misspell VS cJson.ahk

Fun fact: We actually use a code linter via golangci-linter to catch misspellings in code/comments using client9/misspell.

Sorry for disappearing for a day. Meanwhile, I found a few lists (missplell was the big one) and combined them into a single list gofile.io/d/ll1End – 38930 lines. This many hotstrings still work pretty fast.

Using G33KDUDE's cJson wish to store them out to a Json file, so that contents of the .json file looks like this:

Yes, I downloaded this and JSON.ahk. Both are stored in the same folder with the Google script above as AHK files in the same folder.

For that to happen you need to include a JSON parsing library. It can be G33kDude's cJson.ahk or cocobelgica's JSON.ahk.

I wanted to ask if you've taken any looks at my cJson library: https://github.com/G33kDude/cJson.ahk

The best JSON library out there is courtesy of G33kDude cJson.ahk, is the best performing of all and then there's COCO's AutoHotkey-JSON which properly handles empty arrays; also thanks again to G33kDude there's a fork that handles boolean.

If that doesn't cut it for your needs, u/G33kDude has a project named cJson.ahk, as far as I recall it works only on 64bits but has null handling.

In order to keep things as simple as possible I'm gonna use my WinHttpRequest wrapper and a #Warn-compatible version of G33kDude's Socket library. Though cocobelgica's JSON library is not necessary, might be easier working with the AHK native object it provides rather than the COM object I work with as it can't be iterated. Other option is to use the pre-release of cJson.ahk.