LexMake Revisited..

Sometimes.. when i look through older Code i somedays wrote before.. im smilin while shakein my head simulanously.
That Lexer was initially intended to be just a small addition - enough to learn some basics. ... Often enough i wonder what finally came out. Yes. that surreal std-c stuff has its benefits in speed and portability.. but doin a complete rewrite , oo,class based , would have been much easier.
But thats me.. in the End. Once i have my Teeth somwhere deep within stuff.. its hard for me to let go. Because i really hate givin up.:) Time teached me to at least - calm down a bit, "regenerate" and ome back later with some new ideas. .. or at least.. some fixes.
Happend to be that morning around one oCLock. (while wachtchin TimmyTrumpet on Youtube) Oh-- i was really happy i took the tome to write some inline hints.. woooh.. So.. the lexer recieved some Code simplification, does now understand bash style var notation, can (finally, but with a common refcount) happily correctly handle combinations of (unclosed) strings and brackets within multiline continuations plus some sanity checks here and there. Test on an 2011 built Notebook proved 5MB/Sec which, at least, gives more then most other lexers. So -> Now i do think its "presentable" ... but also.. that i dont feel quite "born" for c/cpp coding...
Another area that recieved work was to cleanup the luaLib repository. Implemented all needed stuff for a succesful lua5.3 built and "hacked" further through the Installer, which i talked about in the previous post... Ok...then. Reallife, Summe, Sun-- -- your next :)
Happy Spring -- Thorsten.
Add: LearnedFromLife: either string.resize is intolerant or my expectations to error reporting with usable stacktraces were too high:
"Check your file for any empty lines. If your edge filling loop finds an empty line it gives you exactly that error, as you try to erase characters at nonexisting positions."
Add2: Seems that was at least partly my Fault by (mis)using a string as an array because of handling strings in "other" Languages i used before. so seems std:vector had been a better approach.