On 17 Nov 2011, at 19:19, Greg Ercolano wrote: > LOL, yes, the curse of backslashes.. sorry. > > Was doing a bit of windows stuff just before sending > that msg, and my muscle memory remained in 'backslash mode'. > > One day, Microsoft will understand their kernel understands both > fronts and backs, and adjust their front end tools accordingly. > > I would have thought the new 'powershell' would be their big > opportunity to rid us of the curse.. at least you can type > fronts in commands now, but last I looked their tab completion > turns fronts into backs.. so apparently not.
Yes, it's weird... They've done a lot of work internally - I guess it's maybe it's part of the work they did so they can get the US govt to accept it as "posix compatible" or whatever - then they fail to leverage it in any of their tools, and even seem to be actively preventing it from working in places. Strange. Still, from a developer perspective, many of the API's seem to accept either path separator style now, so that makes my code simpler. Right up 'til I hit an API that still needs backslashes... _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
