@ascii1457,
I'm at a point with my rewrite where I'm ready to start getting user feedback and would very much appreciate you being willing to give it a shot. For my part I would be willing to prioritize any features, bug fixes, and assistance you need in exchange for you being my guinea pig. But I also wouldn't be offended if you say 'no'. If you're interested we can take this discussion offline and you can send me a PM.
If you plan to stick with the current version of ScintillaNET, my recommendation would be to use the
Jacob
P.S. Given the topic of discussion I find your username ironic. :)
I'm at a point with my rewrite where I'm ready to start getting user feedback and would very much appreciate you being willing to give it a shot. For my part I would be willing to prioritize any features, bug fixes, and assistance you need in exchange for you being my guinea pig. But I also wouldn't be offended if you say 'no'. If you're interested we can take this discussion offline and you can send me a PM.
If you plan to stick with the current version of ScintillaNET, my recommendation would be to use the
Scintilla.NativeInterface.PositionAfter (or Scintilla.NativeInterface.PositionBefore) method(s). What they allow you to do is specify a BYTE position as input and then the return the BYTE position where the next CHARACTER starts, taking into account the current encoding/codepage. Thus for every CHARACTER you want to consume in your lexer, you can determine the number of BYTES to consume.Jacob
P.S. Given the topic of discussion I find your username ironic. :)