It's a matter of readability. A function call is used like a noun, so (from the natural language point of view), the name should appear to be a noun (or noun phrase). Now I'll admit that a programming language is not a natural language, so maybe this shouldn't apply. I know that I feel more comfortable reading " NewValue = ValueOf (Object);" than "NewValue = GetValue (Object);" The latter name makes me want to use "GetValue ( Object, NewValue );" On the gripping hand, it's all a matter of what one's custom might be, isn't it? Phil Phil Brashear EDS Conformance Testing Center 4646 Needmore Road, Bin 46 P.O. Box 24593 Dayton, OH 45424-0593 (937) 237-4510 [log in to unmask] www.eds-conform.com > -----Original Message----- > From: Matthew Heaney [SMTP:[log in to unmask]] > Sent: Tuesday, April 20, 1999 7:35 AM > To: [log in to unmask] > Subject: Re: Environment Variables > > "David C. Hoos, Sr." <[log in to unmask]> writes: > > > The use of verbs as the names of functions is not considered > > good style by many authorities. > > Well, I'm considered an authority by some, and I say verbs are AOK for > functions. I routinely use Get_<noun> as the names of functions (as you > may have noticed if you've been following my patterns articles). > > I call arguments like this the "argument by appeal to higher authority."