May 13, 2014 Re: Recommendation on option parsing | ||||
---|---|---|---|---|
| ||||
Posted in reply to Vladimir Panteleev | On Tuesday, 13 May 2014 at 12:08:51 UTC, Vladimir Panteleev wrote:
> On Tuesday, 13 May 2014 at 03:40:57 UTC, Chris Piker wrote:
>> I like your enthusiasm. If you have any modules that don't
>> require me to rebuild libphobos, I'll be happy to give them a
>> whirl. Thank's for responding to my inquiry.
>
> Try Digger!
>
> https://github.com/CyberShadow/Digger
>
> Run: digger build "master + phobos#2072"
>
> Or run the web interface (digger-web), and select the pull from the list.
Thanks for the suggestion! I'll be happy to try it out next
time I have an opportunity to use D. Unfortunately the window
has closed on my current project. I just can't afford any more
schedule slip.
--
Chris
|
May 14, 2014 Re: Recommendation on option parsing | ||||
---|---|---|---|---|
| ||||
Posted in reply to Chris Piker | On Tuesday, 13 May 2014 at 17:05:15 UTC, Chris Piker wrote:
> I tried that, but you're using private members of std.getopt
> (which of course is okay for the way you intended the code
> to be used) so I stopped pursuing this solution.
Not sure why he had you break up the file. It should be as simple as changing the line "module std.getopt;" to something simple like "module getopt" then importing "import getopt;" and include the new file within the build.
Anyway, D's libraries are not as extensive as Python/Ruby/Perl.
|
May 14, 2014 Re: Recommendation on option parsing | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jesse Phillips | On Wednesday, 14 May 2014 at 04:15:04 UTC, Jesse Phillips wrote:
> Anyway, D's libraries are not as extensive as Python/Ruby/Perl.
True, but they wouldn't need to have much more to pass the
good-enough threshold for me. In my current position I
mostly write relatively simple server side programs. So a
good logger + command line handling + cgi interface support
is really enough for what I commonly do. An sftp library
would be hand too, but I can find plenty of work for D to do
without it.
In the future I hope to investigate vibe.d, since a threaded,
cross-platform, standalone server for our data would be nice
to have.
Cheers;
|
May 14, 2014 Re: Recommendation on option parsing | ||||
---|---|---|---|---|
| ||||
Posted in reply to Chris Piker | Too late I see, but maybe next time it will provide you a way to search available projects faster. On DUB http://code.dlang.org/ there is one project that looks like address the issues you had with std.getopt, "post-rock". Have not used it so I cannot give any further recommendations. Maybe you will find there others. On Friday, 9 May 2014 at 23:09:34 UTC, Chris Piker wrote: > Phobos' std.getopt is a bit spare for my taste, as there is > no builtin general help facility with word-wrapping. > > Does anyone have a recommendation on which of the existing > command line option parsing libraries floating around in the > wild to use? If it doesn't compile against the current > version of phobos I'm willing to put in a little work, but > since I'm very new to D I probably would not make the best > design decisions. > > -- > Chris |
May 14, 2014 Re: Recommendation on option parsing | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jesse Phillips | On 05/14/2014 06:15 AM, Jesse Phillips via Digitalmars-d-learn wrote: > On Tuesday, 13 May 2014 at 17:05:15 UTC, Chris Piker wrote: >> I tried that, but you're using private members of std.getopt (which of course is okay for the way you intended the code to be used) so I stopped pursuing this solution. > > Not sure why he had you break up the file. It should be as simple as changing the line "module std.getopt;" to something simple like "module getopt" then importing "import getopt;" and include the new file within the build. he is right, my bad > > Anyway, D's libraries are not as extensive as Python/Ruby/Perl. |
Copyright © 1999-2021 by the D Language Foundation