Path: utzoo!mnetor!uunet!steinmetz!ge-dab!codas!pdn!ard
From: ard@pdn.UUCP (Akash Deshpande)
Newsgroups: comp.lang.smalltalk
Subject: Re: embeddedCapitals
Message-ID: <2610@pdn.UUCP>
Date: 23 Mar 88 15:21:42 GMT
References: <2472@pdn.UUCP>
Organization: Paradyne Corporation, Largo, Florida
Lines: 27
Keywords: conventions capitals uppercase

In article <2472@pdn.UUCP>, colin@pdn.UUCP (Colin Kendall) writes:
> In our shop, we have adopted the Smalltalk "standard" of using embedded
> capitals in class names, variable names, etc., as in StandardSystemView.


	Smalltalk parser smartly omits space in such symbol declarations
	as # fred (= #fred). But spaces are permitted in symbols. Thus,
	' fred' asSymbol is the symbol # fred. (Try ' fred' asSymbol asString
	printIt).

	Thus, StandardSystemView could be represented in the system as a 
	symbol 'Standard System View' asSymbol. Of course, it will be 
	most counter productive to put all these ''s and asSymbols in text.
	But maybe a special key/mode could be designated to enter symbols in.
	There is the problem then of reading correctly Standard System View
	as one symbol as opposed to two or three. This can be solved by having
	the system put all non-message name symbols in one font and all message
	name symbols in another font.

	I am sure the system has enough basis to develop this tool.

						Akash
-- 
Akash Deshpande					Paradyne Corporation
{gatech,rutgers,attmail}!codas!pdn!ard		Mail stop LF-207
(813) 530-8307 o				P.O. Box 2826
(813) 535-3987 h				Largo, Florida 34649-2826