Robert, Sorry. I tested with the fixed version of ArgumentParser. I reverted to the non-fixed ArgumentParser version and yes! the problem does occur from a standard console when I run the debug version of an application e.g osgconvd.exe !
John Ivar On Mon, Oct 4, 2010 at 7:12 PM, John r Haugland <[email protected]>wrote: > Hi Robert, > No, the problem doesn't occur from a standard console, only when I run the > code from Visual Studio 2010 (for debug purpose). > John Ivar > > > > On Mon, Oct 4, 2010 at 6:32 PM, Robert Osfield > <[email protected]>wrote: > >> Hi John, >> >> On Mon, Oct 4, 2010 at 5:23 PM, John Ivar Haugland >> <[email protected]> wrote: >> > The linefeed '\n' is present as the last character of the last argument >> of >> > argv when I run an application (from Visual Studio 2010). I did the >> change >> > to the ArgumentParser in order to be able to debug code in Visual >> Studio. A >> > bug in Visual Studio 2010? >> > >> > Perhaps we could have "#ifdef WIN32 .. #endif" around the code change, >> or >> > should we wait for Microsoft to fix it ? >> > John Ivar Haugland >> >> Does this problem occur if you run from a standard console? >> >> Personally I'd rather have a single solution that happens on all >> platforms and avoid #ifdef's where possible, as it's all too easy for >> platform specific compile problems or bugs to creep in without be >> spotted. >> >> Robert. >> _______________________________________________ >> osg-submissions mailing list >> [email protected] >> >> http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org >> > >
_______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
