Brandon J. Van Every scripsit: > The various INSTALL_* variables denote pathnames. Windows pathnames can > have spaces in them, [...] there is nothing more hideous than double > secret quoting escape problems. [...] For all I know, there might > be nothing wrong with my quoting, and the real issue may be lack of > pathname-with-spaces support. Yes, Windows does take pathnames in > double quotes. Now try quoting and escaping the quotes to get 'em > through the C preprocessor, or through Chicken.
The only thing that prevents this from being a problem in Unix as well is sheer convention; Unix pathnames can and do have spaces in them too. So this work is very valuable in any case. -- John Cowan [EMAIL PROTECTED] http://ccil.org/~cowan Rather than making ill-conceived suggestions for improvement based on uninformed guesses about established conventions in a field of study with which familiarity is limited, it is sometimes better to stick to merely observing the usage and listening to the explanations offered, inserting only questions as needed to fill in gaps in understanding. --Peter Constable _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
