Re: [fpc-pascal] CLI argument parsers

2019-01-17 Thread Martok
> I have archived this mail list via GMANE News so I have *everything* > from about Sept 2003. Very handy for local searches of issues and > content. I do the exact same thing, and I know how much bad threading can ruin the usefulness of a group. You may want to examine whose message was the first

Re: [fpc-pascal] CLI argument parsers

2019-01-16 Thread Bo Berglund
On Tue, 15 Jan 2019 20:02:05 +0100, Martok wrote: >Am 14.01.2019 um 18:05 schrieb Bo Berglund: >> By changing the subject of an existing (very old thread) and post new >> content you have screwed up the message handling of threads so this >> conversation now gets stuffed into the "Resource compil

Re: [fpc-pascal] CLI argument parsers (was: Resource compilation)

2019-01-16 Thread Bart
On Tue, Jan 15, 2019 at 11:02 PM Bart wrote: > I tried the proposed fix (it should go in 5 lines from the bottom i=of > Internal_getopt), and it does not fix the issue. I attached a possible fix to the bugreport. Are there tests for the getopst unit? -- Bart __

Re: [fpc-pascal] CLI argument parsers (was: Resource compilation)

2019-01-15 Thread Bart
On Mon, Jan 14, 2019 at 3:04 PM Michael Van Canneyt wrote: > I think getopts has changed since the bug was reported, but maybe the > proposed fix is still valid. The report is from 2011. Since then there has been a 1 change, adding 1 line, to getopts.pp I tried the proposed fix (it should go i

Re: [fpc-pascal] CLI argument parsers

2019-01-15 Thread wkitty42
On 1/15/19 2:02 PM, Martok wrote: Am 14.01.2019 um 18:05 schrieb Bo Berglund: By changing the subject of an existing (very old thread) and post new content you have screwed up the message handling of threads so this conversation now gets stuffed into the "Resource compilation" thread dating back

Re: [fpc-pascal] CLI argument parsers

2019-01-15 Thread Martok
Am 14.01.2019 um 18:05 schrieb Bo Berglund: > By changing the subject of an existing (very old thread) and post new > content you have screwed up the message handling of threads so this > conversation now gets stuffed into the "Resource compilation" thread > dating back a year and 3 months... > >

Re: [fpc-pascal] CLI argument parsers (was: Resource compilation)

2019-01-14 Thread Bo Berglund
On Mon, 14 Jan 2019 00:56:12 +0100, Martok wrote: >Am 13.01.2019 um 18:43 schrieb Michael Van Canneyt: >> Assuming you mean the command-line arguments: >> >> What's wrong/missing with the functionality in TCustomApplication ? >Other than that nobody in the wild seems to fully use it? ;-) >Even m

Re: [fpc-pascal] CLI argument parsers

2019-01-14 Thread Benito van der Zander
I wrote one, too: http://benibela.de/sources_en.html#rcmdline Supports --linux=style and /windows style, and ' and " quotes On 14.01.2019 10:49, Yann Mérignac wrote: You can also try this: http://yann.merignac.free.fr/unit-cmdline.html It's a command line parser I wrote when I needed it a fe

Re: [fpc-pascal] CLI argument parsers (was: Resource compilation)

2019-01-14 Thread Michael Van Canneyt
On Mon, 14 Jan 2019, Bart wrote: On Mon, Jan 14, 2019 at 12:56 AM Martok wrote: I'm a fan of getopts and use it (with a small wrapper) for almost everything (i. [2]), but it seems that many people are not aware it even exists. It's even POSIX compliant, so the program's users won't be surpr

Re: [fpc-pascal] CLI argument parsers (was: Resource compilation)

2019-01-14 Thread Bart
On Mon, Jan 14, 2019 at 12:56 AM Martok wrote: > I'm a fan of getopts and use it (with a small wrapper) for almost everything > (i. > [2]), but it seems that many people are not aware it even exists. It's even > POSIX compliant, so the program's users won't be surprised by some > implementation

Re: [fpc-pascal] CLI argument parsers

2019-01-14 Thread Yann Mérignac
You can also try this: http://yann.merignac.free.fr/unit-cmdline.html It's a command line parser I wrote when I needed it a few years ago. I was inspired by these 2 articles: - https://www.adacore.com/gems/gem-138-gnatcoll.command-line - https://www.adacore.com/gems/gem-139-master-the-command

Re: [fpc-pascal] CLI argument parsers

2019-01-14 Thread Michael Van Canneyt
On Mon, 14 Jan 2019, Martok wrote: I was 100% expecting that sort of answer. My invitation to suggest improvements, you mean ? I meant it: you're welcome to suggest improvements. If you implement something like argpars and it can be used as backend for TCustomApplication, I'm willing to re

Re: [fpc-pascal] CLI argument parsers

2019-01-14 Thread Martok
I was 100% expecting that sort of answer. Cheers, Martok ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] CLI argument parsers (was: Resource compilation)

2019-01-13 Thread Michael Van Canneyt
On Mon, 14 Jan 2019, Martok wrote: Am 13.01.2019 um 18:43 schrieb Michael Van Canneyt: Assuming you mean the command-line arguments: What's wrong/missing with the functionality in TCustomApplication ? Other than that nobody in the wild seems to fully use it? ;-) Your count is a little bia

[fpc-pascal] CLI argument parsers (was: Resource compilation)

2019-01-13 Thread Martok
Am 13.01.2019 um 18:43 schrieb Michael Van Canneyt: > Assuming you mean the command-line arguments: > > What's wrong/missing with the functionality in TCustomApplication ? Other than that nobody in the wild seems to fully use it? ;-) Even most of the examples in the compiler tree use homegrown par