Derick Rethans <[EMAIL PROTECTED]> wrote: > On Wed, 27 Nov 2002, Sara Pollita Golemon wrote: > > > User complains that maximum length of a line used by fscanf is too short > > (he has lines > 1600 chars). Looking at file.h I agree (it's only 512). > > > > The user requested two options: > > > > 1) Add an optional length field. > > No way to do that without breaking parameter list. :( > > We can't really do that, users will get pissed :) > > > > > 2) Increase to a larger arbitrary number. > > This simply has the problem that it may prove too short eventually as well. > > Yeah, IMO it doesn't solve anything. > > > > > Plus I came up with a third option: > > > > 3) Create an .ini entry to specify the maximum length used. > > I think this has the best overall return on it. > > I don't like us adding a new ini entry for this, I think we should try > another option: > > 4) Make sure we can use fscanf on a dynamically sized buffer. This will > definitely the hardest solution, but also the most beautiful one.
I like this fourth option, because the internal scanf function will anyway need reimplementation since it's not binary safe. Moriyoshi > Derick > > -- > > ------------------------------------------------------------------------- > Derick Rethans http://derickrethans.nl/ > PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ > ------------------------------------------------------------------------- > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
