[Prev][Next][Index][Thread]
Re: Long names are doom ?
-
To: info-dylan@ai.mit.edu
-
Subject: Re: Long names are doom ?
-
From: "Mark Wilden" <mark@mwilden.com>
-
Date: Tue, 12 Jun 2001 18:30:01 -0400 (EDT)
-
Organization: Posted via Supernews, http://www.supernews.com
-
References: <Cy5S6.15$0%3.147909@news.uswest.net> <memo.20010602174435.21899C@brangdon.madasafish.com> <9fguhf$1h4_002@newsreader.cais.net> <T4NT6.151983$eK2.36690315@news4.rdc1.on.home.com> <thvavjjdeodq08@news.supernews.com> <3B1FBC28.6FCD7029@Desk.org> <thvgoto9bgur7b@news.supernews.com> <9g62od$2ja$1@iac5.navix.net>
-
Xref: traf.lcs.mit.edu comp.lang.c++:566137 comp.lang.dylan:13344 comp.lang.clos:5197 comp.lang.smalltalk:114742 comp.lang.tcl:169139
"Eric Moss" <ericmoss@alltel.net> wrote in message
9g62od$2ja$1@iac5.navix.net">news:9g62od$2ja$1@iac5.navix.net...
>
> > Would it help to
> > expand it to nextMatherizingPropersipper if the programmer doesn't know
> what
> > matherizing is or what the proper sipper does?
>
> Not much (you knew that), unless there's a place to find the long name
> explained. Even google can't help much with NMP. :)
Actually, search engines are very good at finding weird abbreviations and
acronyms.
> Type declarations in the
> top-level code can help here, I think:
>
> NextMatherizingPropersipper* nmp = nil;
>
> if (nmp==nil) {...}
Again, if you don't know what those terms mean, they might as well stay as
(unique) abbreviations. Especially if everyone you talk to in the business
actually uses a term like NMP all the time.
> I hope this adds to the conversation...
I usually only reply to parts I disagree with or feel I can elaborate on. I
don't reply to parts I agree with, which is why I didn't reply to most of
your post. :)
References: