Tokenizer- user-keys, but how ???

[ErosOlmi]

Will see what I can do, but pretty sure I can do almost all with cTokenizer module class
Using a module class let me encapsulate all options under a single instance of the class without interference with the rest of the module.


I think I will change .PosStart and .PosEnd to a more esplicative .ByteStart and .ByteEnd

[ReneMiner]

...err, the Byte(-Start and also Line) - idea i had too but in another sense:

Long lStart ' should be in range 1 to Strptrlen(Strptr(sText)) 
Long lLine  ' should be in range 1 to ParseCount(sText, $CRLF)

myParser.Scan(sText, Byte lStart) ' Byte option to tell the parser to start scanning at Byte lStart
myParser.Scan(sText, Line lLine ) ' Line option to scan desired line only

Have time for a very small idea?
check this:
http://www.thinbasic.com/community/s...2320#post92320

[Petr Schreiber]

Eros,

thanks a lot for the explanations, now I understand, very practical!
I like the new functions, thanks a lot for them!

One wish - could ToString be added for SubType as well? There is a string specified during the NewSubType, so could be returned this way.


Petr

[ErosOlmi]

Petr,

actually there is not string we can specify on SubType information in Tokenizer class.
A possible string is the Token itself.

But maybe there is something I do not get from your request.
If you can give me a real life example maybe I can better understand the request.

Ciao
Eros

[Petr Schreiber]

Buonasera,

my apologies for confusion. Take this line:

Dim MyKeys    As Long Value MyParser.NewMainType("MyKeys")

...the generation of new main type takes "MyKeys" as parameter, and produces some integer.

If there would be some kind of internal dictionary, it could match back the integer to "MyKeys".

Just idea, low priority.


Petr