Author: peterw Date: 2006-01-15 16:00:21 -0500 (Sun, 15 Jan 2006) New Revision: 55604
Modified: trunk/mbuild/TODO Log: Add some thoughts to the TODO Modified: trunk/mbuild/TODO =================================================================== --- trunk/mbuild/TODO 2006-01-15 20:46:27 UTC (rev 55603) +++ trunk/mbuild/TODO 2006-01-15 21:00:21 UTC (rev 55604) @@ -271,3 +271,30 @@ to build the target and 'allowed' is false, signal an error. Not sure if allowed = true should imply default = true; almost certainly not, actually. + +* I just committed a patch to allow spaces in subdirectory names, but I + don't think I should have. It's easy to specify a subdirectory with + a space in its name as a literal string: + + subdirs [ a b c "hey a space" d ] + + but then you can't refer to a target inside that subdirectory: + + foo.exe = [ a.cs "path with space/b.cs" ] + + because that can't be disambiguated from a literal string, and it is + pretty ugly. The proper solution is probably to implement escaping + of some sort: + + subdirs [ a b c hey%20a%20space d ] + + this is awkward but if you're going to put spaces in your names then + a little extra work is not unreasonable. If we do this, though, it + brings up whether we should allow, say, arbitrary Unicode characters + to be put into identifiers. But we support UTF-8 buildfiles, so you + can already put arbitrary Unicode characters in your buildfiles + except for those that the tokenizer cares about. If we add escaping, + maybe just have buildfiles be ASCII? Less reduntant, but I am 99% + sure that that is just a horribly bad idea. Then do we have a special + syntax for escaping just spaces, or just characters special to the + tokenizer? just backslashes? _______________________________________________ Mono-patches maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-patches
