Mon, 18 Jun 2001 16:03:08 +0400
>> The lack of extra_command_line_opts is not important,
>> but I wonder, why make things worse?
>> I thought the idea of -package was to collect in one place all
>> the project-specific settings. For example, for my project docon,
>> I need
>> doconOpts = -fglasgow-exts -fallow-this-and-this ...
Simon Marlow <firstname.lastname@example.org> writes
> I'm in two minds about this. At the moment, using a -package option
> does two well defined things:
> - it brings a set of modules into scope
> - it links in the object code for those modules
> According to the Principle of Least Astonishment, we should force the
> user to add any extra options himself, because if '-package wibble'
> automatically adds a number of language-feature options then it's just
> too magical and non-obvious.
> On the other hand, I presume you *need* these options in order to be
> able to use Docon, so adding them automatically would seem reasonable.
> Opinions, anyone?
To add or not to add automatically the language-feature options,
or many other options, this is up to the designer of the package.
The designer is always free to set  in the package.
And you were going to desable this choice (concerning package).