Conference turris::languages

    I knew that I should have extracted it when I first read it this
    morning!  Can someone state why .0 is set hidden?
    
    Thanks,
    Jim
    

I did not set the note hidden but .0 is a memo from Dick Sites that gives
advice on compiling code for Scorpio.  When this memo was written there were
several complaints that the advice was very inappropriate for other VAX models.
As a result, the VAX Architecture Group formed a committee that included
representatives from all major VAX implementation teams and the various
compiler groups. This committee developed a set of approved VAX coding style
guidelines. In several cases these approved coding style guidelines conflict
with the advice given in .0.  Anyone who is writing a VAX compiler should not
use the memo in .0 but should instead get a copy of the approved guidelines.
Unfortunately, the memo that gives these approved guidelines does not have
general distribution.  If you need to see this document, you should ask your
VAXB representative to show you MORE_VAX note 51. 

You might also ask your VAXB representative why these guidelines do not have a
larger distribution. I understand why we don't publish them for reading by
customers but it seems that more than just hardware implementors and compiler
implementors would benefit by seeing them. 

    We're looking into getting the guidelines mentioned in .2 posted
    here.  I don't know yet whether we'll be able to, but in any event,
    Steve's analysis is correct: .0 was set hidden because it conflicts
    with the Architecture Group's guidelines, and it seems like a mistake
    to allow .0 to be distributed.
    
       Gary (co-moderator)

    The current VAX coding styles memo may be found in the VAX
    Architecture conference, EAGLE1::VAX (press KP7...), topic 132.
    
    	-Neil