Hi Rafael,
> I'll try to publish Commons.GetOptions initial release (it
> already works, basically as Mono.GetOptions did), over the
> weekend and then you can choose if you fork or if you'd like
> to contribute to it, and package with nunit. The license is
> still very permissive, so I hope
Hi,
inline
On 8/9/07, Charlie Poole <[EMAIL PROTECTED]> wrote:
> > Basically the idea, would be to add another of the internal
> > options that would you to extract either a gettext compatible
> > base file, or a strings resource file, and use the
> > appropriate mechanism to translate the descr
Hi Rafael,
> On the Desktop, I've seen both approaches, depending on how
> well packaged/versioned the libraries are, put although the
> space cost, it's better to pack your binary dependencies with
> the program, especially for Windows, until some more
> universal dependency-resolving system
Hi Charlie,
inline
On 8/7/07, Charlie Poole <[EMAIL PROTECTED]> wrote:
> Some follow-up questions, now that I've looked at mono.getOptions.
>
> 1) I like the idea of having the system provide this capablility,
> rather than including it in every app. But what do people generally
> do for cross-pl
Hi Mirco,
> On Tue, 2007-08-07 at 10:21 -0700, Charlie Poole wrote:
> > Some follow-up questions, now that I've looked at mono.getOptions.
> >
> > 1) I like the idea of having the system provide this capablility,
> > rather than including it in every app. But what do people
> generally do
> >
Hi Charlie,
On Tue, 2007-08-07 at 10:21 -0700, Charlie Poole wrote:
> Some follow-up questions, now that I've looked at mono.getOptions.
>
> 1) I like the idea of having the system provide this capablility,
> rather than including it in every app. But what do people generally
> do for cross-platf
rom: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Charlie Poole
> Sent: Monday, August 06, 2007 10:57 AM
> To: 'Miguel de Icaza'
> Cc: 'Rafael Teixeira'; mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] Cross-platform command-lines
>
&g
Hi Miguel,
> > I haven't but I'll take a look. Do you use the double-dash
> convention
> > as well? I wonder if that's something windows users can get
> accustomed
> > to?
>
> It seems that the majority of the flags on Windows take the
> form /word but they tend to accept -word.
That's true
> I haven't but I'll take a look. Do you use the double-dash
> convention as well? I wonder if that's something windows
> users can get accustomed to?
It seems that the majority of the flags on Windows take the form /word
but they tend to accept -word.
In Unix historically options after a single
arlie Poole
> > Cc: mono-devel-list@lists.ximian.com
> > Subject: Re: [Mono-dev] Cross-platform command-lines
> >
> > Did you look at how Mono.GetOptions adapts to each platform,
> > if desired. Just to give you food for thought.
> >
> > Personally I like,
Charlie Poole escribió:
> I haven't but I'll take a look. Do you use the double-dash
> convention as well? I wonder if that's something windows
> users can get accustomed to?
I've used it some time ago and as I remember, you would have three
options for each "commmand-line-option":
1) Long one w
ra
> Sent: Tuesday, July 31, 2007 10:58 AM
> To: Charlie Poole
> Cc: mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] Cross-platform command-lines
>
> Did you look at how Mono.GetOptions adapts to each platform,
> if desired. Just to give you food for thought.
>
&g
Did you look at how Mono.GetOptions adapts to each platform, if
desired. Just to give you food for thought.
Personally I like, what I've implemented on it: the simple usage of
accepting either "/" or "-" as the prefix, generally having
long/descriptive option names, with selected shortcuts for a s
Hi All,
I'm looking for ideas on best practices for command-line parameters intended
to be used on both Windows and Linux. Mostly, I want guidelines for how to
design syntax that makes sense on both platforms, but if anyone has
implemented something I'd be interested in that as well.
Charlie
__
14 matches
Mail list logo
