From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org, psmith@netezza.com
Subject: Re: crosstool-ng libncurses check in configure
Date: Tue, 12 May 2009 16:33:00 -0000 [thread overview]
Message-ID: <200905121833.03293.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <1242141974.30571.269.camel@psmith-ubeta.netezza.com>
Paul,
All,
On Tuesday 12 May 2009 17:26:14 Paul Smith wrote:
> On Sun, 2009-05-10 at 10:30 -0400, Joachim Nilsson wrote:
> > lib="$( echo lib{ncursesw,ncurses,curses}.{so,a,dylib} )"
> Personally I think that changing the script to work properly with a
> POSIX shell is the best in the _long_ run, as it's the most portable.
Yes, ./configure *shall* be a POSIX-compliant shell script.
This is the course I took when fixing that non-portable line.
> The above seems like a lot of processing (non-portable, invokes an extra
> shell, etc.) to avoid writing 9 words:
Programers are lazy, and if they can write smaller code, all the
better. Note also that programers also prefer writing bigger code
to generate a list of constants, rather than writing said list.
Given this, please note that you can call me a programmer! ;-P
Using loops to generate said list has one positive side effect, by
the way: if we have to add a new library name and/or extension, it
is easier to update the loop that handles that part, rather than
updating the full list, which would become unmanageable in the
loooong term.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ___ |
| --==< ^_^ >==-- `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
`------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2009-05-12 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 14:31 Joachim Nilsson
2009-05-11 17:03 ` Yann E. MORIN
2009-05-11 17:27 ` Michael Abbott
2009-05-11 18:13 ` Yann E. MORIN
2009-05-11 20:48 ` Yann E. MORIN
2009-05-12 15:26 ` Paul Smith
2009-05-12 16:33 ` Yann E. MORIN [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905121833.03293.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=psmith@netezza.com \
/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).