Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] sh bug
- Date: Wed, 19 Feb 2003 21:52:03 -0500
- From: Viktor Pavlenko <vvp@example.com>
- Subject: Re: [tlug] sh bug
- References: <20030219182145.RLM4278.fep04-mail.bloor.is.net.cable.rogers.com@[127.0.0.1]><Pine.LNX.4.44.0302201027450.1463-100000@example.com>
>>>>> "JDB" == J David Beutel <jdb@example.com> writes: >> $ sh -c 'while read a; do if [ $a = "b" ]; then exit 1; fi; echo $a; done < a; echo done' >> a >> done >> $ ksh -c 'while read a; do if [ $a = "b" ]; then exit 1; fi; echo $a; done < a; echo done' >> a JDB> What is the bug? The exit only ends the while loop? Or the JDB> parser is susceptible to obfuscation? I was afraid I would have to explain :( But I though it'd be JC :) sh interprets exit inside the while loop (only if it's fed from stdin) as break. This contradicts the man page. Re. obfuscation, I always do such things on command line, so that I don't have to save a file and make it executable. No intentional obfuscation was intended. Come on, it's just one line of code. Viktor
- Follow-Ups:
- Re: [tlug] sh bug
- From: Matt Doughty
- Re: [tlug] sh bug
- From: Jean-Christian Imbeault
- Re: [tlug] sh bug
- From: Tim Hurman
- References:
- [tlug] sh bug
- From: Viktor Pavlenko
- Re: [tlug] sh bug
- From: J. David Beutel
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] sh bug
- Next by Date: Fonts (Was: Re: [tlug] Linux and USB Flash Mem.)
- Previous by thread: Re: [tlug] sh bug
- Next by thread: Re: [tlug] sh bug
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links