Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!newsfeed.kamp.net!newsfeed.kamp.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.unix.shell,comp.unix.programmer,comp.programming.contests Subject: Re: The First Pure Shell Contest (PUSH): relativepath Date: Fri, 19 Aug 2011 19:58:55 +0100 Lines: 20 Message-ID: <87pqk18byo.fsf@sapphire.mobileactivedefense.com> References: <9b7kg7F3njU1@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net 0UNHYqq4MVZGfon0sDufEgKawCJgTabhZTSo3EAkOxWSzxqZA= Cancel-Lock: sha1:0wYJXLQJt/bXCQAtzUOCKaYpGsk= sha1:du120LeowIA2Cq+Dav+oKgivtPs= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Xref: x330-a1.tempe.blueboxinc.net comp.unix.shell:1718 comp.unix.programmer:1158 comp.programming.contests:9 Jens Schweikhardt writes: > The First Pure Shell Contest (PUSH) > > == Motivation == > > The shell is not known for powerful string processing. Seasoned > programmers use various combinations of sed, awk, cut and others to > perform the more sophisticated transformations, or sacrifice portability > by using their shell's extensions, like arrays. But calls to external > utilities and use of shell extensions are often not needed. Knowing what > the POSIX shell can do may turn a slow non-portable script into a > blazingly fast and portable hacker's delight. The goal is to show the > absurdity of forking and nonportable constructs when a nice and small > pure shell solution solves the problem just as well. I spent some thoughts on this because I was interested in at least having a general idea how a solution could look like. OTOH, the reason why I work in miserably paid programming jobs is essentially because I enjoy solving software problems a lot more than dicksizing contests.