On 28 Dec 2012, at 06:47, w. szukalski wrote:
> The filename_ANY.cxx files do know a dirsep:
>
> #if defined(WIN32) || defined(__EMX__) && !defined(__CYGWIN__)
> inline int isdirsep(char c) {return c=='/' || c=='\\';}
> #else
> #define isdirsep(c) ((c)=='/')
> #endif
>
>
> But some utf8.cxx functions do not:
>
> char fltk3::make_path( const char *path )
> {
> if (fltk3::access(path, 0)) {
> const char *s = strrchr( path, '/' );
> }
>
> // strip the filename and create a path
> void fltk3::make_path_for_file( const char *path )
> {
> const char *s = strrchr( path, '/' );
> }
>
> Is this a bug in fltk-3.0.x and in fltk-1.3.x ?
Not sure: are you seeing aberrant behaviours manifested due to this behaviour?
It may be that the way we are using these paths in WIN32 is such that the path
sep does not matter - many WIN32 API's (but not all, unfortunately) are now
more or less posix accepting (if not posix compliant) and so do not care which
way the dir sep slopes any more...
So... maybe it is OK then. Though it looks like it is probably an oversight...
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
