Scheme naming conventions

Norman Gray <[email protected]>
Newsgroups gmane.comp.java.sisc.user
Message-ID <[email protected]>
Greetings,

[This is really a Scheme question, rather than a specifically SISC one]

In a recent feature request, Matthias said

> There is a naming convention in Scheme that denotes
> "with" with "/" in procedure names, e.g. |call/cc| for
> |call-with-current-continuation|

This made me think: is there a list anywhere, canonical or otherwise,  
of Scheme naming conventions?  At various times, I've googled for the  
obvious things without turning up any that I don't already know.

I know of:

predicate?
mutator!
*global-parameter*
type-method (eg STRING-LENGTH)
convert-type->type
...and now '/' -> 'with'.

I think I've also seen %implementation-private%, but don't know how  
common that is.

Scsh uses '/' as a sort of sub-name notation, so that OPEN/APPEND is  
the append flag for the OPEN-FILE procedure, and BUFPOL/LINE (for  
example) indicates line buffering in port.  I suppose these _can_ be  
pronounced 'with', but it's a bit of a stretch.

The SISC manual mentions `By convention field accessors should be  
named with a leading colon (:) followed by the field name'.  That's  
specific to record types, yes?

I have the vaguely paranoid impression that there's some set of  
conventions known to Everyone Else, passed on by some sort of  
apostolic succession.  Can anyone put me out of my misery?

All the best,

Norman


-- 
------------------------------------------------------------------------ 
----
Norman Gray  /  http://nxg.me.uk
eurovotech.org  /  University of Leicester, UK





-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.