Article View: comp.lang.misc
Article #6033Re: What makes a language successful
From: Liber
Date: Wed, 21 Dec 1988 01:57
Date: Wed, 21 Dec 1988 01:57
14 lines
1188 bytes
1188 bytes
In article <874@quintus.UUCP> ok@quintus.UUCP (Richard A. O'Keefe) writes: >if you regard it as a problem: GO AHEAD AND WRITE SEMICOLONS BEFORE ENDS. >Ever heard of empty statements? Although it is syntactically legal, it is considered by some to be bad style (usually the people grading your programs in school). I've even used a few compilers that would give you lots of warning messages about null statements resulting from this case. Personally, I put the semicolons in; it's much less of a hassle when I have to change the code. Unfortunately, the problem does not go away when you talk about ELSE instead of END. -- NEVIN ":-)" LIBER AT&T Bell Laboratories nevin1@ihlpb.ATT.COM (312) 979-4751
Technical Details
Message-ID:
<9236@ihlpb.ATT.COM>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-lcc!ames!ucsd!rutgers!att!ihlpb!nevin1References:
<208100002@s.cs.uiuc.edu> <2832@uhccux.uhcc.hawaii.edu> <874@quintus.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-lcc!ames!ucsd!rutgers!att!ihlpb!nevin1 From: nevin1@ihlpb.ATT.COM (Liber) Newsgroups: comp.lang.misc Subject: Re: What makes a language successful Message-ID: <9236@ihlpb.ATT.COM> Date: 21 Dec 88 01:57:50 GMT References: <208100002@s.cs.uiuc.edu> <2832@uhccux.uhcc.hawaii.edu> <874@quintus.UUCP> Reply-To: nevin1@ihlpb.UUCP (55528-Liber,N.J.) Organization: AT&T Bell Laboratories - Naperville, Illinois Lines: 13