[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Is this an IFS bug in getopts?

From: Steven W. Orr
Subject: Is this an IFS bug in getopts?
Date: Tue, 26 Apr 2011 11:42:49 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20110303 Thunderbird/3.1.9

GNU bash, version 4.0.35(1)-release (x86_64-redhat-linux-gnu)

I ran a program that was supposed to die with an error message that said:

Invalid format: example:

Instead, it died with:

i -- Invalid format: example:

I traced the problem back to a call to getopts. It turns out that when I called getopts, I had set IFS='-'. It never occurred to me that I could impact the function of getopts by setting IFS.

The old code was this:
set -- $DRVREV
(( $# == 3 )) || die -i -- 'Invalid format: example:'

I can fix the problem easily by saying

set -- $DRVREV
(( $# == 3 )) || die -i -- 'Invalid format: example:'

So here we are.
1. Should getopts be documented to say that it uses IFS?
2. Should getopts be hardcoded to use the dash as the option delimiter?
3. Is the current functionality correct the way it is and I'm just looking at it wrong?

TIA :-)

Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

reply via email to

[Prev in Thread] Current Thread [Next in Thread]