trinity/src
1
0
Fork 0
Code

tear down embarrassingly flawed article until i get it right

Browse Source
This commit is contained in:
dtb 2022-05-31 01:05:46 -04:00
parent c3e34b885e
commit d59fd50600
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
homepage/knowledge/c78.html
View File

@ -48,7 +48,7 @@ This page documents those incompatibilities and relative oddities.
I have never done (and probably never will do) extensive programming in pre-ANSI C. I have never done (and probably never will do) extensive programming in pre-ANSI C.
These incompatibilities were discovered out of Appendix C in <I>The C Programming Language, 2nd ed.</I> but are described further. These incompatibilities were discovered out of Appendix C in <I>The C Programming Language, 2nd ed.</I> but are described further.
</P> </P>
<H2 ID="octal89"><CODE>8</CODE> and <CODE>9</CODE> as valid octal digits</H2> <!--<H2 ID="octal89"><CODE>8</CODE> and <CODE>9</CODE> as valid octal digits</H2>
<PRE> <PRE>
main() main()
{ {
@ -80,5 +80,6 @@ This file provides <CODE>getnum</CODE>, a function used in <CODE>/usr/source/c/c
My theory is that this behavior is a side-effect of a very efficient but imperfect method of parsing integer constants from a file stream, My theory is that this behavior is a side-effect of a very efficient but imperfect method of parsing integer constants from a file stream,
and that this implementation was "good enough" and informally the behavior of a C compiler supplied invalid octal constants was just undefined. and that this implementation was "good enough" and informally the behavior of a C compiler supplied invalid octal constants was just undefined.
</P> </P>
-->
</BODY> </BODY>
</HTML> </HTML>