option quoting in csc is a complete mess

[felix winkelmann]

Using things like csc -cflags in shell scripts is mostly unusable, as the quoted include path (-I" ... ") is taken verbatim and not recognized by gcc due to the quotes.

Even though this is fundamentally based on the completely useless and insane shell quoting rules of sh and it's bastards, the code in csc doesn't make it any better, by using various ways of quoting ("qs", "quotewrap", "quote-option") and a tangled labyrinth of variables and thoughtlessly written crap code.

csc needs a complete rewrite. Ideally with lots of stuff removed to makes it less complex (like deployment) and a single point where options are prepared shell and shell-quoted as necessary.

This will necessarily break lots of stuff. It doesn't matter. It has to be.

[sjamaan]

Does the qs patch (58684f69572453acc6fed7326fa9df39be98760e) fix any of this?

[sjamaan]

It doesn't, see #1334

[sjamaan]

You know, this would be a great one to tackle for CHICKEN 5, since the breakage won't matter.

[felix winkelmann]

I don't know what to do here. To avoid quoting hell, one should probably use execve and friends in this case, but the appropriate device for Windows does not exist. The quoting rules with cmd.exe are even more insane than under UNIX and make up a large part of the messy code that is used in csc to somehow pass the correct arguments to subprocesses.

A rewrite is certainly desirable, but not required for C5. We should identify specific functionality that is either broken or *must* be changed in an incompatible manner.