Re: ostrstream in lyxsum.C

2000-06-28 Thread Lars Gullik Bjønnes
Lior Silberman <[EMAIL PROTECTED]> writes: | This is a known feature of strstream::str() - it does _not_ null-terminate | the string. You need to explicitely write a '\0' to the stream for this. | (this behavrious is documented in the strstream manpage). I know this. Just look at the other place

Re: ostrstream in lyxsum.C

2000-06-28 Thread Lior Silberman
On 28 Jun 2000, Lars Gullik [iso-8859-1] Bj&resh;nnes wrote: > I'd really like to know what strlen(s) in #0 is... > And I can't really se why it craches... s != NULL, *s != "" n > 0 < npos. > > Ok, had a look... The only think I can thing of would be to add a '\0' > to the read...hmm this can be

Re: ostrstream in lyxsum.C

2000-06-28 Thread Lars Gullik Bjønnes
Andre Poenitz <[EMAIL PROTECTED]> writes: | > This is what I did first...then some tests showed that this was | > _really_ slow, so I changed it. | | There seems to be indeed a factor of 10 between the running times. | Strange thing. agree. | On the other hand - we are talking about less than

Re: ostrstream in lyxsum.C

2000-06-28 Thread Andre Poenitz
> This is what I did first...then some tests showed that this was > _really_ slow, so I changed it. There seems to be indeed a factor of 10 between the running times. Strange thing. On the other hand - we are talking about less than a second for a 1-MB-file. Having documents this large is rather

Re: ostrstream in lyxsum.C

2000-06-28 Thread Lars Gullik Bjønnes
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | Lars> You get a dynamic char* that you have to manually delete. How | Lars> large should the char[] buffer be? | | The size of the file, probably. Dynamic char[] is just as easy to work with. (in this case) | Lars> | I am trying to fix the bug

Re: ostrstream in lyxsum.C

2000-06-28 Thread Jean-Marc Lasgouttes
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> | - why is the ostrstream created without a corresponding char[] Lars> buffer, | whereas a buffer is used in the other cases? What;s Lars> the behaviour of | the constructor in this case (I read the std, Lars> but I am not sure

Re: ostrstream in lyxsum.C

2000-06-28 Thread Lars Gullik Bjønnes
Andre Poenitz <[EMAIL PROTECTED]> writes: | > Lars, could you explain a bit how the code in lyx::lyxsum works? | > | > - why do we need a ostringstream/ostrstream? Is it really imppossible | > to output from an ifstream to a string? That looks like a stupid | > thing, IMO. | | Since do_crc(

Re: ostrstream in lyxsum.C

2000-06-28 Thread Lars Gullik Bjønnes
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | Lars, could you explain a bit how the code in lyx::lyxsum works? | | - why do we need a ostringstream/ostrstream? Is it really imppossible | to output from an ifstream to a string? That looks like a stupid | thing, IMO. And istream_iterator

Re: ostrstream in lyxsum.C

2000-06-28 Thread Andre Poenitz
> Lars, could you explain a bit how the code in lyx::lyxsum works? > > - why do we need a ostringstream/ostrstream? Is it really imppossible > to output from an ifstream to a string? That looks like a stupid > thing, IMO. Since do_crc() seems to accept _any_ input iterator, one should be abl

ostrstream in lyxsum.C

2000-06-28 Thread Jean-Marc Lasgouttes
Lars, could you explain a bit how the code in lyx::lyxsum works? - why do we need a ostringstream/ostrstream? Is it really imppossible to output from an ifstream to a string? That looks like a stupid thing, IMO. - why is the ostrstream created without a corresponding char[] buffer, wherea