Re: [Pharo-dev] GetOpt

Can you be more concrete because I like what Camillo designed. Le 2/12/14 16:06, Sean P. DeNigris a écrit : EstebanLM wrote is cool. I would like to explore the possibility to replace our command line parser with getopt. You know… is more compatible at the end :) I find the implementation of o

Re: [Pharo-dev] GetOpt

FWIW I am writing my product doc with Pillar . Some humps to go through but it is now coming out nicely. I hope to be able to write some things too! Phil Le 6 déc. 2014 04:32, "stepharo" a écrit : > I liked that you propose yourself also to edit the zeroConf chapter. > Thanks. > I must admit

Re: [Pharo-dev] GetOpt

On Wed, Dec 3, 2014 at 5:29 AM, Ben Coman wrote: > Eliot Miranda wrote: > >> One if these, which Ben Coman's recent changes above my 64-bit >> microsecond clock should have fixed is a spin loop of up to a second to >> synchronize the second and millisecond clocks. >> > > Is this in the image or

Re: [Pharo-dev] GetOpt

Can you be more concrete because I like what Camillo designed. Le 2/12/14 16:06, Sean P. DeNigris a écrit : EstebanLM wrote is cool. I would like to explore the possibility to replace our command line parser with getopt. You know… is more compatible at the end :) I find the implementation of o

Re: [Pharo-dev] GetOpt

IMO all that needs to be fine is to take a careful look at start-up and eliminate costly but unnecessary activities. You should easily be able to get startup times down to tens if milliseconds on modem hardware. I always wanted to have a pharoDaemon.

Re: [Pharo-dev] GetOpt

I liked that you propose yourself also to edit the zeroConf chapter. Thanks. I must admit that I'M FED UP to feel the only one with Sven that seems to be able to write a documentation in our wonderful community. So at least changes should be retrofitted in the available doc. Do not worry LaTex i

Re: [Pharo-dev] GetOpt

Eliot Miranda wrote: One if these, which Ben Coman's recent changes above my 64-bit microsecond clock should have fixed is a spin loop of up to a second to synchronize the second and millisecond clocks. Is this in the image or VM ? I didn't notice this. I found these either by profiling (c

Re: [Pharo-dev] GetOpt

On Wed, Dec 3, 2014 at 9:51 AM, Eliot Miranda wrote: > Hi Phil, > > On Dec 2, 2014, at 2:18 AM, "p...@highoctane.be" > wrote: > > Well, after looking at the command line handlers in the image for the way > options are handled, I was of opinion that I wanted something like getopt. > > So, I looke

Re: [Pharo-dev] GetOpt

Hi Phil, On Dec 2, 2014, at 2:18 AM, "p...@highoctane.be" wrote: > Well, after looking at the command line handlers in the image for the way > options are handled, I was of opinion that I wanted something like getopt. > > So, I looked around and found that implementation of Ian that I plugged

Re: [Pharo-dev] GetOpt

On Tue, Dec 2, 2014 at 4:55 PM, Ben Coman wrote: > p...@highoctane.be wrote: > >> On Tue, Dec 2, 2014 at 4:30 PM, Ben Coman > b...@openinworld.com>> wrote: >> >> p...@highoctane.be wrote: >> >> >> >> On Tue, Dec 2, 2014 at 4:06 PM, Sean P. DeNigris >>

Re: [Pharo-dev] GetOpt

On Tue, Dec 2, 2014 at 4:42 PM, Damien Pollet wrote: > Coral is currently broken because I didn't maintain it through the > pharo releases (the current CommandLine stuff is more or less > extracted from it). However, the option-parsers part should still be > OK, it's the hooking at image startup

Re: [Pharo-dev] GetOpt

p...@highoctane.be wrote: On Tue, Dec 2, 2014 at 4:30 PM, Ben Coman > wrote: p...@highoctane.be wrote: On Tue, Dec 2, 2014 at 4:06 PM, Sean P. DeNigris mailto:s...@clipperadams.com>

Re: [Pharo-dev] GetOpt

Coral is currently broken because I didn't maintain it through the pharo releases (the current CommandLine stuff is more or less extracted from it). However, the option-parsers part should still be OK, it's the hooking at image startup that is not up to date. There were/are multiple goals : - mak

Re: [Pharo-dev] GetOpt

On Tue, Dec 2, 2014 at 4:30 PM, Ben Coman wrote: > p...@highoctane.be wrote: > >> >> >> >> On Tue, Dec 2, 2014 at 4:06 PM, Sean P. DeNigris > > wrote: >> >> EstebanLM wrote >> > is cool. >> > I would like to explore the possibility to replace our comman

Re: [Pharo-dev] GetOpt

p...@highoctane.be wrote: On Tue, Dec 2, 2014 at 4:06 PM, Sean P. DeNigris > wrote: EstebanLM wrote > is cool. > I would like to explore the possibility to replace our command line parser > with getopt. You know… is more compatible at t

Re: [Pharo-dev] GetOpt

On Tue, Dec 2, 2014 at 4:06 PM, Sean P. DeNigris wrote: > EstebanLM wrote > > is cool. > > I would like to explore the possibility to replace our command line > parser > > with getopt. You know… is more compatible at the end :) > > I find the implementation of our command line handlers very confu

Re: [Pharo-dev] GetOpt

EstebanLM wrote > is cool. > I would like to explore the possibility to replace our command line parser > with getopt. You know… is more compatible at the end :) I find the implementation of our command line handlers very confusing. It seems like it grew organically from a smaller idea and the de

Re: [Pharo-dev] GetOpt

> On 02 Dec 2014, at 11:24, Torsten Bergmann wrote: > >> Combined with a small image, it would be a terrific tool. > > That was/is the goal of Coral. http://rmod.lille.inria.fr/coral/ > afaik the goal of coral was/is what “scale” is trying also to do… the g

Re: [Pharo-dev] GetOpt

>Combined with a small image, it would be a terrific tool. That was/is the goal of Coral. http://rmod.lille.inria.fr/coral/ Dont know about its current state. Thx T.

Re: [Pharo-dev] GetOpt

Well, after looking at the command line handlers in the image for the way options are handled, I was of opinion that I wanted something like getopt. So, I looked around and found that implementation of Ian that I plugged into the CommandLineArguments in my activate methods. I like the dictionary

Re: [Pharo-dev] GetOpt

See https://en.wikipedia.org/wiki/Getopt Le 2 déc. 2014 à 10:17, stepharo a écrit : > Can you just tell me a bit more :) > > Le 2/12/14 08:45, p...@highoctane.be a écrit : >> I have made Ian Piumarta's GST GetOpt work in Pharo 3.0 >> >> See: >> >> http://www.smalltalkhub.com/#!/~philippeback/G

Re: [Pharo-dev] GetOpt

Can you just tell me a bit more :) Le 2/12/14 08:45, p...@highoctane.be a écrit : I have made Ian Piumarta's GST GetOpt work in Pharo 3.0 See: http://www.smalltalkhub.com/#!/~philippeback/GetOpt Nice tool even if we have some other s

Re: [Pharo-dev] GetOpt

2014-12-02 9:37 GMT+01:00 Esteban Lorenzano : > is cool. > I would like to explore the possibility to replace our command line parser > with getopt. You know… is more compatible at the end :) > +1 ! Thx Phil, Luc > > thanks phil. > > Esteban > > On 02 Dec 2014, at 08:45, p...@highoctane.be wr

Re: [Pharo-dev] GetOpt

is cool. I would like to explore the possibility to replace our command line parser with getopt. You know… is more compatible at the end :) thanks phil. Esteban > On 02 Dec 2014, at 08:45, p...@highoctane.be wrote: > > I have made Ian Piumarta's GST GetOpt work in Pharo 3.0 > > See: > > ht

[Pharo-dev] GetOpt

I have made Ian Piumarta's GST GetOpt work in Pharo 3.0 See: http://www.smalltalkhub.com/#!/~philippeback/GetOpt Nice tool even if we have some other support in CommandLineHandlers. But for a quick parameters setting in your own CommandLineHandler, it is fast to use and easy to debug. Phil