Hi Manfred,

On Fri, 2004-02-13 at 12:21, Manfred Weiler wrote:
> 
> I am in doubt, whether you are right here. I found some code as you 
> described in the "SceneFileHandler/ImageFileHandler" but not in the
> PathHandler itself - where I rather think it belongs. 

check out PathHandler::findFile, it does a PNOTICE for every path it
tries, and calls PathHandler::analysePath, which tries to determine
whether it's a Win32 or Unix path.

> > We thought about adding that as a default, but then you would have to
> > have specific API calls to remove it in cases where you don't want it,
> > thus we decided to have the users add it explicitly. It just some thing
> > you need to know, as it's not a big deal to do it.
> 
> So we are again at documentation issues here. ;-)

Aren't we always. :)

> > Integrated, thanks for the patch. Is there a specific reason for using
> > the FLOG? FWARNING is generally more appropriate.
> 
> Wouldn't you consider this an error situation which the user need to be
> informed about under any circumstances? Just consider your application
> which you called with a file argument terminates without a remark if
> the file does not exist.

We usually use WARNING as an indicator for a non-fatal errors (for fatal
errors there's FATAL, which should only be used before an exit()), LOG
is only used for explicitly requested output (like ::dump or similar
things). The default warning level is NOTICE, so unless the user
consciously changes something, he will get notices and warnings.

        Dirk




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to