From: Bruce Korb <bruce.korb@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: [PATCH] do not augment environment
Date: Mon, 01 Oct 2012 07:24:00 -0700 [thread overview]
Message-ID: <5069A780.1040700@gmail.com> (raw)
In-Reply-To: <5069022C.9040600@netris.org>
Hi Mark,
On 09/30/12 19:38, Mark H Weaver wrote:
> Thanks for the patch, but I think it needs more work before it can be
> committed. See below for my comments.
You're welcome! Just FYI, I've got no ego wrapped up in being the
one to type in characters, so fixing things up for preferred style
or oversights would be no concern to me at all.
> * You assume that the directory separator is '/'.
Either that, or a wrapper environment fixes it up.
If there is a conventional way of dealing with Microsoft-did-it-their-way
issues, I don't know what it is. I'm not overly familiar with Guile code.
> * You should not do the extra search if 'fname' is an absolute
> pathname, and I'm not sure whether it should be done for relative
> pathnames containing directory separators. Does anyone else have
> thoughts on that?
It is already an "unusual case" path. The extra check would save a few cpu
cycles when the unusual case was going to fail. This saves one or two cycles
in the marginally more common case of the unusual case succeeding.
> * As a stylistic issue, I don't like your trick of breaking out of the
> do-while. I'd prefer something closer to this (but with the above
> problems addressed):
I consider it a developed style. :) The deeper the logic nesting, the
more complex the code, to my eyes anyway. In this particular case,
we're talking about "break" in the third level instead of two statements.
I definitely think the two statements make for microscopically more
complex code. That is likely much outweighed by familiarity with
the technique.
All that notwithstanding, it's your code and what I provided I considered
mostly a guideline for what needs to happen to eliminate the LD_LIBRARY_PATH
fiddling. Just let me know how to plug in the Microsoft directory
separator when needed and I'll resubmit the patch. NOTE: I'll be out
of town the 10th through 20th.
Thanks - Bruce
next prev parent reply other threads:[~2012-10-01 14:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 23:36 [PATCH] do not augment environment Bruce Korb
2012-10-01 1:13 ` Bruce Korb
2012-10-01 2:38 ` Mark H Weaver
2012-10-01 14:24 ` Bruce Korb [this message]
2012-10-01 14:39 ` Bruce Korb
2012-10-01 16:59 ` Mark H Weaver
2012-10-01 18:27 ` Bruce Korb
2012-10-03 10:31 ` [PATCH] Don't augment LD_LIBRARY_PATH (was Re: [PATCH] do not augment environment) Mark H Weaver
2012-10-04 20:37 ` Ludovic Courtès
2012-10-06 2:30 ` Mark H Weaver
2012-10-06 12:36 ` Mark H Weaver
2012-10-07 21:16 ` Ludovic Courtès
2012-10-06 12:42 ` Ludovic Courtès
2012-10-06 14:31 ` Mark H Weaver
2012-10-05 9:43 ` Sjoerd van Leent Privé
2012-10-05 21:58 ` Mark H Weaver
2012-11-27 22:54 ` [PATCH] Fix library search order and don't change LD_LIBRARY_PATH Mark H Weaver
2012-11-27 22:59 ` Ludovic Courtès
2012-11-27 23:23 ` Mark H Weaver
2012-11-27 23:01 ` Bruce Korb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5069A780.1040700@gmail.com \
--to=bruce.korb@gmail.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).