> > AFAICT that would be the only case where this code came > into play, i.e. > > on non-WinXX host for which configure could not locate a scandir > > implementation at build time... > > Yep, I believe this is true. There is an exception for SunOS that > disables the system scandir function explicitly, but I still don't > know what this is good for (today). ISTR that this exception was > more than 10 years old when I checked it. Mike (or anybody), do > you have an idea why that was needed and whether we can remove it > for today's SunOS systems?
I have no idea... If we can ascertain that there is no system for which this now comes into play, we can drop the questionable scandir code and thereby alleviate any license worries? > There may be others that don't have scandir(), though, but I really > can't imagine what (ancient?) systems those might be. Anybody? I know that, a while back, I had 1.1.x running on VxWorks (an old version, maybe 5.2?) and that was embedded *with no filesystem* and hence no scandir function. But since it had no filesystem, I had to inhibit all the fltk filename stuff anyway, so it didn't matter! That said, I think (assume, have not tried) that if I used VxWorks with an embedded filesystem then I would also get a scandir function... _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
