Am Samstag, 1. April 2006 21:17 schrieb Enrico Forestieri: > On Sat, Apr 01, 2006 at 05:55:07PM +0200, Georg Baum wrote: > > Almost. No boolean please (that would circumvent the whole idea of > > internal/external path). Simply hardcode the decision in internal_path > > and external_path. Later we can then think about paths visible to the > > user and replace some calls of external_path() by a new function > > display_path(). > > Georg, cygwin runs on windows and it understands both posix and > win-style paths. So, what is external and what is internal? > In the win32 version C:/xxx is the internal representation, in > the *nix version /c/xxx is the internal representation. > Why one of the two cannot be chosen as internal representation > in cygwin (which bridges both worlds) ?
I already wrote that either could be used as internal representation. My point is that this decision should be made at compile time, and it should not be configurable at runtime which representation is chosen. > Sincerely I cannot understand your point. If you fear that this > fact can bring a major burden to a programmer, well, now I have > spent quite some time on the subject and can tell you that it is > exactly the contrary, i.e., a major burden can occur if you adopt > a different representation for external and internal ;-) We are forced to do that on non-cygwin windows. So we have no choice but use external_path() and internal_path() carefully. With this prerequisite I see no additional burden to programmers if external_path() uses something different than internal_path() on cygwin. Georg
