In my quest to create a syntax highlight mode for the text editor I use, it
occurred to me that there might be a better way of organizing some of the
material the manual.  Specifically "III. Reference - Orchestra Opcodes and
Operators."

As of right now, everything gets bundled into one section.  If it is
reorganized, the content would much more clear, and easier to navigate. 
Here are the sub-sections I propose, in the order I think makes the most
sense: Block Statements, Operators, Functions, Macros, Opcodes.



Blocks Statements.  instr, endin, opcode, endop.

Operators.  Items such as *, +, >, &&, etc.

Functions.  This would include anything that works like cpspch() or a().

Macros.  The preprocessors, such as #define and #include.

Opcodes.  Pretty much everything else.



The reason I see a real need for this is because in terms of syntax and
functionality, all these different classes of keywords and operators work
very differently from one another.  Does it makes sense to group instr, *,
cpspch(), #define and oscil all in one list?  In my humble opinion, the
answer is no.

I realize that maybe I'm making a big deal out of nothing.  However, I think
it's at least worth mentioning.  Any thoughts?


Best, 
Jake 
---- 
The Csound Blog 
http://www.thumbuki.com/csound/blog/




-- 
View this message in context: http://www.nabble.com/Suggestion-for-organizing-the-Csound-Manual-tp14717865p14717865.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net