[Openmcl-devel] foreign type name escaping

Pascal J.Bourguignon pjb at informatimago.com
Thu Nov 18 05:24:34 PST 2004

Gary Byers writes:
> Cocoa has (and mostly seems to follow)
> rulesForUsingStudlyCaseInMethodsAndClassNames.  Core Foundation's rules
> for type names seem to follow conventions that're similar to (if not
> identical to) Cocoa's class name conventions, with CF replacing NS
> on standard system types/classes.
> After that ... I think that it starts to get a lot less regular quickly
> (and the differences -usually- seem to revolve around whether the first
> "word" in a multi-word token is capitalized and/or whether there's a
> standard prefix on built-in things.  The lisp symbol :MULTI-WORD-TOKEN
> could map to either "multiWordToken" or "MultiWordToken"; I'm sure that
> you could pick one of these and make it the default, but it's not clear
> that there are simple, easily remembered and intuitive rules that work
> with (e.g.) arbitrary legacy things in Carbon or arbitrary 3rd-party
> things.

There's a rule too: what's global is capitalized, what's local starts
with a lower case.

class names, types, global variables are capitalized,
method names, local variables, parameters, attributes have a lower case initial.

__Pascal Bourguignon__                     http://www.informatimago.com/
The world will now reboot; don't bother saving your artefacts.

More information about the Openmcl-devel mailing list