On Jan 9, 2008 3:45 PM, Jean-Sébastien Guay
<[EMAIL PROTECTED]> wrote:
> OK, I'll probably be able to help there in the coming weeks.
Great, much appreciated.
> I didn't mean warnings, there are some errors that should show up on
> any compiler, such as a method declared as bool someMethod() not
> returning a value... For example, in include/vpb/FileCache :
>
> bool sync() { if (_requiresWrite) write(_filename); }
>
> should be
>
> bool sync() { if (_requiresWrite) return write(_filename); return false;
> }
>
> or something to that effect. I would have thought gcc would give an
> error there... MSVC certainly does.
I've just done a clean build and g++ isn't reporting any warnings whatsoever.
The above is an error of course, I'll fix this.
> BTW, to correct the methods, I would like to know what is your
> standard for methods returning error? 0/false = no error and 1/true =
> error? Or 0/false = failed and 1/true = succeeded?
Typically true for succeeded/did operation.
Robert.
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
