Path: utzoo!utgpu!watserv1!watmath!att!att!emory!wuarchive!usc!elroy.jpl.nasa.gov!jpl-devvax!lwall From: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) Newsgroups: comp.lang.perl Subject: Re: Cute hack around tiny bug (Re: Help a perl apprentice) Message-ID: <10162@jpl-devvax.JPL.NASA.GOV> Date: 30 Oct 90 00:19:26 GMT References: <18840001@hp-lsd.COS.HP.COM> <21380@orstcs.CS.ORST.EDU> <21417@orstcs.CS.ORST.EDU> Reply-To: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) Organization: Jet Propulsion Laboratory, Pasadena, CA Lines: 55 In article <21417@orstcs.CS.ORST.EDU> pvo@sapphire.OCE.ORST.EDU (Paul O'Neill) writes: : In article mdb@ESD.3Com.COM (Mark D. Baushke) writes: : > : >I sent Larry private e-mail about this and suggested a one character : >change to the script change : > : > $line{$avail} = sprintf("%30.30s%10.1f%6s\n", ...); : >to : > $line{$avail} .= sprintf("%30.30s%10.1f%6s\n", ...); : > : : Yikes!! First it was one-liners. Now it's one-byters! : : What's next? One-bitters? Well, actually, one bit patches aren't all that uncommon. Typically they involve changing something from 0 to 1 or 1 to 0, or (un)capitalizing something. Here are a couple of one-bitters I sent out myself, recently: *************** *** 733,739 **** A(0,0,0), /* NEXT */ A(0,0,0), /* REDO */ A(0,0,0), /* GOTO */ ! A(1,1,0), /* INDEX */ A(0,0,0), /* TIME */ A(0,0,0), /* TIMES */ A(1,0,0), /* LOCALTIME */ --- 785,791 ---- A(0,0,0), /* NEXT */ A(0,0,0), /* REDO */ A(0,0,0), /* GOTO */ ! A(1,1,1), /* INDEX */ A(0,0,0), /* TIME */ A(0,0,0), /* TIMES */ A(1,0,0), /* LOCALTIME */ *************** *** 843,849 **** A(1,1,0), /* LISTEN */ A(1,1,0), /* ACCEPT */ A(1,1,3), /* SEND */ ! A(1,1,1), /* RECV */ A(1,1,1), /* SSELECT */ A(1,1,1), /* SOCKPAIR */ A(0,3,0), /* DBSUBR */ --- 895,901 ---- A(1,1,0), /* LISTEN */ A(1,1,0), /* ACCEPT */ A(1,1,3), /* SEND */ ! A(1,1,3), /* RECV */ A(1,1,1), /* SSELECT */ A(1,1,1), /* SOCKPAIR */ A(0,3,0), /* DBSUBR */ Larry