I'm surprised this doesn't work...
() is not illegal in a path, is it?
Especially under Linux, where you can name a file
foo*?bar.c too, if you think that it's a good idea (it is not, but you can do it). But seriously, no joking... files like
foo-1.4.3-15(2).tar.gz aren't entirely uncommon, so the same thing should really work with Code::Blocks too
Maybe we need to quote filenames more rigorously, not only if they contain spaces. It seems that
gcc calls
sh for some of its work, and the shell believes it has to do something about the unquoted
(). Does that seem about right? So... we should make sure it doesn't.