I fixed the highlighting.
See: https://github.com/PrismJS/prism/pull/1 ... 37c02a3b7c

Ist repariert - danke für den Hinweis

AHK does not use .NET at all. AHK uses the WinAPI directly it seems to open the stream with:
https://docs.microsoft.com/en-us/window ... reatefilew

Just use normal ifs. Using short circuit evaluation is considered unreadeable and bad practice.
If the goal is keeping the value below a specific value and then overflowing to the beginning again you could also consider using:

I will see if I can fix the yellow highlighting.

Did you add #NoEnv during this time perhaps? A_ComSpec is always available but ComSpec could be unavailable if #NoEnv was in effect.

Now let's imagine, the default retval size is changed from int (int32) to int64, scripts that run with AHK64 and expect int (int32) will either fail instantly in most cases (easy to pinpoint) if the callee doesn't clean up the upper DWORD or will work w/o issues if the callee does clean up full rax...

Als alternative zum steuern von Webbrowsern gibt es auch noch Selenium und Chrome.ahk

I made the pull request - joedf or tank could probably already update the definitions we have.
See: https://github.com/PrismJS/prism/pull/1703

Edit: if you see any other things our Highlighting misses out on, please share it here.

On the DLLCall page, in the ptr type description, there is a note that:
In order to pass NULL to a function pass the Integer 0.

This note is more confusing than helpful. We need to remove it, or rephrase it in a way that people know that an Integer value is meant and not the int type.

Yeah that needs rephrasing.

AHK's int32 data type should not use bits 32..63 and lower bits 0..31 contain a valid 32 bit result. :D I'm not quite sure what you mean here. You said that using Ptr instead of Int would be fine on 64 bit, since the 32 bit values will be fine. But no they won't be fine. So I don't understand this ...

When a script expects 32bit int as default and gets 64bit int64, it gets the same value. But when we truncate full x64 pointer, we might corrupt it and it would lead to an exception. No it doesn't. When values are returned from C functions the returning function just assigns the value to a specific...

It locks other programs from editing the file and keeps you from deleting it I think.

I have identified the issue and prepared a fix - will try to merge it into the PrismJS AutoHotkey highlighter later today.
See: https://github.com/PrismJS/prism/issues/1700

Ever since Minecraft got taken over by Microsoft the game got 100% better - and its only been 2 updates so far.

It looks nice Well done - might use this in the future.

Bei mir ist die < Taste kein Modifikator da ich sie zum programmieren brauche. Ich weiß ich wieso deine anderen Anwendungen das so sehen, aber du musst das wahrscheinlich über Hotkeys/Plugins lösen. Die Farben links repräsentieren wo du Änderungen gemacht hast. Zudem scheinen die Markierungen um ein...

Well there are several types of Singletons in that topic.
I mostly use the super global automatically initiated one

Well I would go over this in a later tutorial. What you discovered here is essentially a design pattern. Many people seem to find this particular pattern first. What you have in B would be called a Singleton. Design Patterns are reoccurring small patterns in our code that we use to tackle specific p...