[prev in list] [next in list] [prev in thread] [next in thread] 

List:       twig-devel
Subject:    RE: [twig-devel] php4 probs..(contd. from "Strange problem (bug?)")
From:       "Greg Ross" <greg () darkphoton ! com>
Date:       2000-04-25 18:21:23
[Download RAW message or body]


	Things like bound's checking shouldn't really be reported since they are
valid cases usually.  TWIG doesn't currently have any logging facilities
other than outputing to the user's display.

							Greg

> -----Original Message-----
> From: The Doctor What [mailto:docwhat@gerf.org]
> Sent: Monday, April 24, 2000 4:15 PM
> To: twig-devel@screwdriver.net
> Subject: Re: [twig-devel] php4 probs..(contd. from "Strange problem
> (bug?)")
>
>
> * Greg Ross (greg@darkphoton.com) [000424 00:24]:
> >
> > 	There are many area's of TWIG that need to have bounds
> checking added, it
> > simply a matter of time...
> >
> > 	Thanks for the fix, I've committed it to the cvs tree.
>
> Sorry for grumping:  I was fustrated by the experience.  It wasn't
> fair to the developers of TWIG.
>
> I might go bounds hunting later, what is the approved way of
> throwing a WARNING/ERROR?  Is there a twig.log kept someplace?  It
> isn't too useful to throw a warning if it appears only for one user
> in this one esoteric case and the user doesn't report it to the
> sysadmin to look at.
>
> Ciao!
>
> --
> "I can see the headlines now... and they're wrong!"
>
> The Doctor What: A Holtje Production             http://docwhat.gerf.org/
> docwhat@gerf.org                                                   KF6VNC
>

[prev in list] [next in list] [prev in thread] [next in thread]