🚀 go-pugleaf

In article <Bwznzx.Dr1@mentor.cc.purdue.edu> hrubin@mentor.cc.purdue.edu (Herman Rubin) writes:
>In article <1css0nINNc51@agate.berkeley.edu> jhauser@pine.CS.Berkeley.EDU (me) writes:
>>And if your compiler won't let you do basic formatting, Herman, I suggest
>>you toss it and get another.  I'm sure there are some that will.
>
>Where does a faculty member get such a compiler?  I have not run this through
>a compiler; about all I can think of doing to get this coded intelligently is
>to get a compiler not to do too much damage, and tweak the assembler output.

Uh, clearly I wasn't clear.  What I meant was that---as much as you complain
about shortcomings in languages and compilers---most modern languages (and
their compilers) don't prevent you from writing your code in a readable,
well-formatted style.  Why not use indentation to show nesting, for example,
like most folks do?  (Or does that hurt performance, too?)  You know;
something like:

extern B;
n = 0;
m = 0;
b = B;
{
    goto start;
    case 1: {
        n += 1;
    }
    case 3:
    case 5:
    case 6:
    case 9:
    case 10:
    case 11:
    case 12:
  start:
    g = ....;
    switch( g ){
        case 2: goto label1;
        case 4: goto label2;
        case 7: {
            g4 = 1;
            goto label3;
        }

	.... etc.


--------------------------------------------------------------------------n
Boycott redwood.  Boycott Louisiana-Pacific.  Keep the forests.  YYYYYYYYYYY
John Hauser---jhauser@cs.berkeley.edu  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY