ftp.nice.ch/peanuts/GeneralData/Documents/dsp/DSPDoc.tar.gz#/DSPDoc/Fodder/NameConventions.txt

This is NameConventions.txt in view mode; [Download] [Up]

NAME CONVENTIONS

In general, macros and variables provided by NeXT contain an underbar
('_') character.  Exceptions to this rule occur for the addresses
RESET and START.  Symbols or 'define's which are treated as system
constants or flags are in upper case.


REGISTER USE

Macros do not save any state. The calling routine must save any 
registers whose contents are needed after the call.  The purpose
of this conention is to minimize the amount of save/restore work
necessary --- only the caller knows what has to be saved.

The caller also normally loads all registers containing arguments
for the called macro. This convention allows maximum use of any
serendipitous register usage prior to the macro call. For example,
successive envelope sections (e.g. DSPORCHSRC/expenv)
can be called sequentially, with the current amplitude state variable
being passed effortlessly in the A register.


MEMORY SPACE NUMBERING

Dsp memory spaces are numbered as follows (cf. @MSP directive of the
DSP56000 Macro Assembler Reference Manual):

          0 - none
          1 - 'x'
          2 - 'y'
          3 - 'l'
          4 - 'p'


These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.