Re: save options handling

[David Bateman]

John W. Eaton wrote:

> On 29-Apr-2005, Bill Denney wrote:
>
> | As someone who is more of a user, I'd think that if I give any options 
> | they would override the defaults, and it would be hard for me to debug if 
> | there were other default options that took effect when I gave options.  If 
> | you keep the default options when specific options are used, it would be 
> | helpful to at least give a warning that the other options were used.
>
> I agree, I think that if options are supplied, the default options
> should not be used.  Otherwise, I think we will have a lot of confused
> users wondering why their files are compressed when they just
> specified "-ascii".
>
> jwe
>
>  
I see a kludge that might be used to get a compromise of both 
behaviors... This would mean that the default_save_options would give 
the default file format always..... Something like this

1) Parse default_save_format and set default formats
2) Parse user args
3) if user specified no options parse the default_save_options....

I suppose this would give pretty much the behavior you want, but is less 
clean....

D.

--
David Bateman                                address@hidden
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax) 
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary