jpff@maths.bath.ac.uk wrote:
> 
> That is because there is no poscil opcode in Csound!  There was a
> suggestion at one time, but it was not released.

Aha. It was actually announced/documented in 3.47 notes.
Shall we just remove it from the docs then?
(I wouldn't mind having it though, I'd like a pulse generator.)

Also:

Backslash line continuation doesn't work right under DOS/Winsound yet.
The reconstructed line misses the first character, and csound doesn't skip 
the second half of the broken line, so I get a "no legal opcode" error.
Eg:
    kcps, kbw xyin .02, \
	0, 1000, 0, 10
is parsed as
    kcps, kbw xyin .02, , 1000, 0, 10
	 , 1000, 0, 10

By the way, this breaks path name parsing under dos/win too,
since they use backslash for path separator. Currently only
forward slash works for full path names. So, either insert a 
check on double quote status in the backslash management, or 
specify that file names in Csound must use front slash only.


Regards,

	re