Re: [cc65] Forced imports by linker config

On 2010-11-12, at 15:52, Ullrich von Bassewitz wrote:
>
> [...]
> The changes had some effects on order of command line arguments, so  
> it may be
> necessary to change make- or batch processing files. For examples,  
> the output
> file (-o switch) must now be defined before using -t or -C, because  
> the config
> file is read when -t or -C is found on the command line. Changing  
> the output
> file name using -o when the config is already read will cause the  
> name be
> ignored in most cases. The same is true for -t/-C and libraries: If  
> your
> config has forced imports, it must be read before any libraries,  
> because
> otherwise the import may not be resolved.
>
> Please let me know if there are any problems with the new code.

While the whole idea sounds cool and promising, this above seems to me  
like a place to put a bit more effort to neutralise the side effects.  
I have to admit that I am allergic to forced order of options/ 
parameters :-)

A quick question - wouldn't it be relatively easy to parse all the  
options before processing/executing them in a required order,  
regardless of how were they given on the command line?

-- 
SD!
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.