GHCJS

[Simon Peyton-Jones]

| > So then parseDynamicFlags should be split into two layers, the lower
| > layer returning unused flags, and the upper layer generating errors.
| 
| It's not that simple. In
|     ghcjs -O -someflag something -Wall
| is "something" an argument to someflag, or a file to be compiled?

It think it would be quite acceptable for GHC's parseDynamicFlags to consume any arguments that don't start with "-", and treat them as filenames.  The new behaviour is that it might return any unrecognised flags starting with "-".   So flags for the JavaScript thing would have to look like
	-foogle
or	-blag=33

This is not as flexible as the flag-spec Ian suggests, but it's *simple* and that is a real virtue.

Simon