According to Eric Blake on 7/9/2009 3:09 PM: > According to POSIX, the status of . shall be 0 if no command was executed during > the sourced script. Therefore, this is a bug: > > $ dash -c 'false; . /dev/null; echo $?' > 1 > > and should be fixed to output 0. Ping. -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -- To unsubscribe from this list: send the line "unsubscribe dash" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: bug with $? after .
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: bug with $? after .
- From: Eric Blake <ebb9@xxxxxxx>
- Date: Mon, 31 Aug 2009 05:28:39 -0600
- In-reply-to: <loom.20090709T210608-909@xxxxxxxxxxxxxx>
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
- References:
- bug with $? after .
- From: Eric Blake
- bug with $? after .
- Prev by Date: Re: bugs in cd
- Next by Date: Re: avoid compiler warning
- Previous by thread: bug with $? after .
- Next by thread: Re: bug with $? after .
- Index(es):
 |