TheDcoder

Then every code execution vulnerability should get this rating... but they don't.

The 10/10 rating for this is highly inaccurate, that should only be reserved for fully remote arbitrary code execution. I agree with the points made in this video:

@jchd I'm afraid I don't really understand what you said, but it sounds about right... except for the part about copying, I don't see why that's necessary since it is already in the memory and not used by anything else, so just use that directly instead. All "updates" would be gone because the function would clean up all of the local variables.

Same as what gets passed if the parameter weren't a byref

There's no question of reading the value, the function totally disregards byref if the supplied expression is not a value that can be referenced

@jchd I don't think they are trying to actually manipulate the value though. Several years ago I encountered a similar problem with ByRef but it could be solved by simply treating the ByRef parameter like a normal non-ref one. So this is not a bug but could be a useful "feature" that can be added.

Have you considered supporting git repositories as packages directly? That way you don't need to deal with a central database at all (but you can still have one, of course). NPM supports this and even has a shorthand for adding git repos from GitHub directly I think.

I totally forgot about those functions, very handy indeed! But why doesn't TCPSend automatically handle that though? Is it just hardcoded to convert everything to ANSI?

Indeed I have, I couldn't send emoji with my scripts. I suspect that TCPSend is screwing with the encoding. You will have to manually find a way to convert your messages string to properly formatted UTF-8 binary and then send that directly with TCPSend. By the way, don't bother with BOM, it is fairly useless and even undesired, so it won't help you with anything but it can for sure screw up your text potentially if programs are not properly made to handle it. AutoIt's own IniRead function will fail if the file has a BOM.

C++ is just a bastardised version of C, I had to write some a few days ago

Or you can also use an older Beta version if needed.

It's not needed if you don't wish to authenticate, and the server will definitely disconnect you if you provide invalid credentials like "TestScript" So definitely remove the function calls to Auth functions. Not sure about other UDFs but the documentation on mine should be up to date according to the IRCv3.1 standard, which is fairly modern compared to the older RFCs. The IRC standards committee doesn't use version numbers anymore but everything should be backward compatible.

What's the exact error message? I looked at the script and the error messages are very detailed so we can pin-point the error

Oh, that's an interesting issue, never encountered it while I was working with IRC in AutoIt.

I am slightly curious, why did you start working on this with an older version of AutoIt?