U++ forum: Welcome to the forum

Status & Roadmap

Authors & License

Funding Ultimate++

Search on this site

Search in forums

Home » U++ Library support » U++ Core » In some cases CParser can be out of buffer

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Return to the default flat view

Create a new topic

Submit Reply

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

Sun, 22 March 2009 09:06

gridem is currently offline

gridem
Messages: 45
Registered: August 2008

Member

luzr wrote on Sun, 22 March 2009 02:07

I am perhaps missing something. Which cases? Do you have any testcase demostrating the problem?

(Note that you should not call GetChar when IsEof...)

Mirek

Yes, in case of calling GetChar twice without check on IsEof() (it can be treated as error of using CParser yet). But the function SkipTerm already has this check: two subsequent calls of SkipTerm work fine.

There is another issue: when CParser::term == '\n' and the function CParser::SkipTerm() is called than CParser::line will not be increased.

Report message to a moderator

Send a private message to this user

[Message index]

		In some cases CParser can be out of buffer By: gridem on Sat, 21 March 2009 21:38
		Re: In some cases CParser can be out of buffer By: mirek on Sun, 22 March 2009 00:07
		Re: In some cases CParser can be out of buffer By: gridem on Sun, 22 March 2009 09:06
		Re: In some cases CParser can be out of buffer By: mirek on Sun, 22 March 2009 09:27
		Re: In some cases CParser can be out of buffer By: gridem on Tue, 24 March 2009 08:32
		Re: In some cases CParser can be out of buffer By: mirek on Tue, 24 March 2009 11:02

Previous Topic:	bug StaticConditionVariable::Initialize() has no implementation
Next Topic:	The problem with 'Null'

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

PDF

]

Current Time: Thu Jun 13 01:14:57 CEST 2024

Total time taken to generate the page: 0.02403 seconds