in reply to Re: Re: Programming Laws
in thread Programming Laws

My group now has to spell "deprecated" as "depricated" because when I did the database design, I spelled it wrong, wrote a bunch of code around it, and now it has too much inertia to fix


Replies are listed 'Best First'.
Re: Re: Re: Re: Programming Laws
by George_Sherston (Vicar) on Jan 25, 2002 at 02:35 UTC
    A relatively harmless infraction compared to the guy who misspelt "referrer" as "referer" (as in $ENV{'HTTP_REFERER'})

    George Sherston
Re: Re: Re: Re: Programming Laws
by Juerd (Abbot) on Jan 25, 2002 at 03:09 UTC
    .oO( find | xargs perl -i -pe's/depricated/deprecated/g' )
    (update: stefp correctly said /g was a good idea)

    2;0 juerd@ouranos:~$ perl -e'undef christmas' Segmentation fault 2;139 juerd@ouranos:~$

      There is a loophole (sic). you probably meant:

      <ctt>find | xargs perl -i -pe's/depricated/deprecated/g'

      -- stefp -- check out TeXmacs wiki

      Yes, yes, I know I could do that, but I don't really want to break something that is currently working. That misspelling is spread across MSSQL Server as column headings in various tables, VB script ASPs, C++ applications, and Perl scripts. If I were to try to change it now, it would certainly break something.
Re: Re: Re: Re: Programming Laws
by Jenda (Abbot) on Mar 23, 2003 at 16:24 UTC

    The project I inherited and now spend most of my time with is full of these. And they could not even misspell consistently :-(

    Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
       -- Rick Osborne

    Edit by castaway: Closed small tag in signature