From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20110508182753.GA18603@polynum.com> References: <129E2E01-3583-4E27-B520-252A956F59FC@corpus-callosum.com> <20110508182753.GA18603@polynum.com> Date: Sun, 8 May 2011 17:34:22 -0400 Message-ID: From: Comeau At9Fans To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=00151757714a77e82e04a2ca7c2c Subject: Re: [9fans] Compiling 9atom kernel WAS: Re: spaces in filenames Topicbox-Message-UUID: e13b1f76-ead6-11e9-9d60-3106f5b1d025 --00151757714a77e82e04a2ca7c2c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Sun, May 8, 2011 at 2:27 PM, wrote: > On Thu, May 05, 2011 at 09:54:28AM +0000, Greg Comeau wrote: > > > > Some more food for thought: > > > > "Debugging is twice as hard as writing the code in the first place. > > Therefore, if you write the code as cleverly as possible, you are, > > definition, not smart enough to debug it." --Brian Kernighan > > > > With a caveat: when one is really clever, one finds "the shortest path > to the truth" i.e. the simplicity; this means that really clever guys > make programs easy to debug because these are the simplest ones doing > the job. > > In Brian Kernighan's sentence, s/cleverly/sophisticatedly/ (this is > probably a barbarism, but in french "sophistiqu=E9" is pejorative: > obfuscation, convoluted etc.). I think one can usually read things into such phrases, sometimes validly sometime invalidly. I also think it is often easy to disprove such phrases= , and so to instead to often just try to find the spirit of the phrase even i= f it is found to be problematic. For instance, easy to debug could mean the program is so riddled with problems just opening to a random part of it wil= l yield a problem with little effort it could also mean to the contrary that it was written so well that any bugs could be easy to find, but equally on the contrary the program could be such a bleeping mess that even though bug riddled getting through the logic etc could be tormenting at best while at the same time a clean program with few bugs can sometimes make finding "the long bug" harder because it is the lone last one. In the end there is often no pure bug cause or pure bug resolution mechanism but something in the middle that is contextual. All IMO. --=20 Greg Comeau / 4.3.10.1 with C++0xisms now in beta! Comeau C/C++ ONLINE =3D=3D> http://www.comeaucomputing.com/tryitout World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90. Comeau C/C++ with Dinkumware's Libraries... Have you tried it? --00151757714a77e82e04a2ca7c2c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Sun, May 8, 2011 at 2:27 PM, <tlaronde@polynum.com> wrote:
On Thu, May 05, 2011 at 09:54:28AM +0000, Greg Comeau wro= te:
>
> Some more food for thought:
>
> "Debugging is twice as hard as writing the code in the first plac= e.
> =A0Therefore, if you write the code as cleverly as possible, you are,<= br> > =A0 definition, not smart enough to debug it." --Brian Kernighan<= br> >

With a caveat: when one is really clever, one finds "the shortes= t path
to the truth" i.e. the simplicity; this means that really clever guys<= br> make programs easy to debug because these are the simplest ones doing
the job.

In Brian Kernighan's sentence, s/cleverly/sophisticatedly/ (this is
probably a barbarism, but in french "sophistiqu=E9" is pejorative= :
obfuscation, convoluted etc.).

I think one = can usually read things into such phrases, sometimes validly sometime inval= idly. =A0I also think it is often easy to disprove such phrases, and so to = instead to often just try to find the spirit of the phrase even if it is fo= und to be problematic. =A0For instance, easy to debug could mean the progra= m is so riddled with problems just opening to a random part of it will yiel= d a problem with little effort it could also mean to the contrary that it w= as written so well that any bugs could be easy to find, but equally on the = contrary the program could be such a bleeping mess that even though bug rid= dled getting through the logic etc could be tormenting at best while at the= same time a clean program with few bugs can sometimes make finding "t= he long bug" harder because it is the lone last one. =A0 In the end th= ere is often no pure bug cause or pure bug resolution mechanism but somethi= ng in the middle that is contextual. =A0All IMO.

--
Greg Comeau / 4.3.10.1 with C++0xisms now in beta!
Comeau C/C++ ONLINE =3D=3D> =A0 =A0 http://www.comeaucomputing.com/tr= yitout
World Class Compilers: =A0Breathtaking C++, Amazing C99, Fabulous C90.=
Comeau C/C++ with Dinkumware's Libraries... Have you tried i= t?
--00151757714a77e82e04a2ca7c2c--