public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Eselect Syntax Bug?
Date: Mon, 3 Aug 2009 12:37:11 -0400	[thread overview]
Message-ID: <20090803123711.621097d8.frank.peters@comcast.net> (raw)
In-Reply-To: <20090803121751.ccc23314.frank.peters@comcast.net>

On Mon, 3 Aug 2009 12:17:51 -0400
Frank Peters <frank.peters@comcast.net> wrote:


>  These lines encapsulate the problem with
> the eselect code.
> 
> 
> #! /bin/bash
> function-one()
> {
> echo "FOOBAR"
> }
> function-one
> 
> 
> This code fails on my system.  In fact, I booted into my old system,
> a non-gentoo system, and the code also failed.  However, after booting
> into a Linux rescue disk, that runs from a CD and ramdisk, the code does
> not fail.  (All bash versions were 4.x.)
> 
>

I am responding to my own message.

The code fails on some systems and succeeds on other systems.  Why?

The answer may not be important.  The code seems to be an example
of poor practice.  Check out the second entry at this link:

http://tldp.org/LDP/abs/html/gotchas.html

If the above code is re-written to remove the hyphens and replace
them with underscores, it will not fail on any system.

Thus, the eselect developers should re-write their variables using
underscores and the problem will disappear for everyone.

Frank Peters



  reply	other threads:[~2009-08-03 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 14:04 [gentoo-amd64] Eselect Syntax Bug? Frank Peters
2009-08-03 14:27 ` Josh Sled
2009-08-03 16:17   ` Frank Peters
2009-08-03 16:37     ` Frank Peters [this message]
2009-08-03 16:46     ` Josh Sled

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=20090803123711.621097d8.frank.peters@comcast.net \
    --to=frank.peters@comcast.net \
    --cc=gentoo-amd64@lists.gentoo.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