I have tried to add a feature to my AEC-to-WebAssembly compiler that it suggests corrections for misspelled function or variable names, using the Longest Common Subsequence algorithm. However, now that compiler crashes if compiled with CLANG on Windows or Visual Studio on Windows, and it is set to compile the Analog Clock example. It runs into Stack Overflow then, if I am interpreting the error messages from the debugger correctly, when compiling the line 358 ( https://github.com/FlatAssembler/AECforW...k.aec#L358 ). The error does not occur on Emscripten, on any version of GCC that I have tried or if optimization is enabled in CLANG (using -O3, it only occurs in CLANG on Windows under default optimization). Can somebody help me figure out what is going on?
I have opened a GitHub issue about it, on which you can see what the Visual Studio Debugger outputs when that Stack Overflow occurs: https://github.com/FlatAssembler/AECforW...y/issues/5
By the way, which algorithm would you be using for suggesting corrections for misspelled variable, function and structure names? I am using LCS ( https://github.com/FlatAssembler/AECforW...de.cpp#L99 ), but I am quite sure it is not the most appropriate (sometimes suggesting a very long variable name which has that misstyped variable name as substring, rather than the much-shorter variable name the programmer more likely intended).
I have opened a GitHub issue about it, on which you can see what the Visual Studio Debugger outputs when that Stack Overflow occurs: https://github.com/FlatAssembler/AECforW...y/issues/5
By the way, which algorithm would you be using for suggesting corrections for misspelled variable, function and structure names? I am using LCS ( https://github.com/FlatAssembler/AECforW...de.cpp#L99 ), but I am quite sure it is not the most appropriate (sometimes suggesting a very long variable name which has that misstyped variable name as substring, rather than the much-shorter variable name the programmer more likely intended).
