U++ forum: Welcome to the forum

Re: In some cases CParser can be out of buffer [message #20573 is a reply to message #20525]

Tue, 24 March 2009 08:32

gridem
Messages: 45
Registered: August 2008

Member

luzr wrote on Sun, 22 March 2009 11:27

Especially, CParser normally never stops at "space" (e.g. term == '\n'). Look at the code, after each "term eating" operation, there is a call to DoSpaces. This is to make e.g. Char operation fast.

Of course, in "other" special cases, you might want to deal with spaces yourself, then you activate NoSkipSpaces and you have to call Spaces after each accepted term yourself.

Is there a hole in this logic? Smile

Mirek

P.S.: While a very unlikely case, I think you are right about SkipTerm and line number. I have added a fix there.

So, I used the CParser in mixed mode. And I found that in some cases CParser shows wrong line number. Applied patch will solve such kind of issue.

I used the NoSkipSpaces because I need not to skip spaces after the last bracket but inside brackets I used SkipSpaces.

I notices that CParser works very fast and it's really useful and easy to use. It's amazing!

Report message to a moderator