From: Greg Russell on
On Wed, 14 Apr 2010 16:47:27 +0000, Chris F.A. Johnson wrote:

>> BTW, I hate this stupid "my ..." naming scheme. It make the UI
>> look like it is for an idiot. Do you label your luggage case "my
>> lugguage" when traveling?
>
> I agree. It's one of the factors that gave me an instant dislike of
> perl!

The "dumbing down" of society to a 5th-grade level seemed to be rather
ubiquitous in the last decade of the last century, but "it's MY
computer ... MY McDonald's ... MY variable, MYSQL, etc. etc." seems to be
more of an angry 2-year-old level.
From: J G Miller on
On Wed, 14 Apr 2010 16:47:27 +0000, Chris F.A. Johnson wrote:

> It's one of the factors that gave me an instant dislike of perl!

Emacs lisp also leans towards using "my" as a prefix for user defined
variables and functions to distinguish them from similarly named
entities in the official released code.

From: Chris F.A. Johnson on
On 2010-04-14, J G Miller wrote:
> On Wed, 14 Apr 2010 16:47:27 +0000, Chris F.A. Johnson wrote:
>
>> It's one of the factors that gave me an instant dislike of perl!
>
> Emacs lisp also leans towards using "my" as a prefix for user defined
> variables and functions to distinguish them from similarly named
> entities in the official released code.

Only two or three that I can see.


--
Chris F.A. Johnson, <http://cfajohnson.com>
Author:
Pro Bash Programming: Scripting the GNU/Linux Shell (2009, Apress)
Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)
From: LEE Sau Dan on
>>>>> "unruh" == unruh <unruh(a)wormhole.physics.ubc.ca> writes:

unruh> Some people like whitespace. "My Recipie File"

>> Why use such a long name, when "Recipie" suffices, and is much
>> easier to type?

unruh> You do know that your likes and dislikes are not universal?

unruh> IF all you ever use is a gui to select files, then making the
unruh> title of the file into a descriptive sentence can be
unruh> useful.

Of course, descriptive names are useful. But not "My Recipe File".

1) The "My" is basically contentless. It conveys no more information
than "someone's" in this context.

2) The word "File" is superfluous. If that isn't a (computer) file,
what is? A paperclip? A pin? A lipstick?

So, I don't find "My Recipe File" any more descriptive than "Recipe".
The latter is simply more concise and no less precise.


IOW, I find your example a bad one. I'm not against giving files more
descriptive names. But adding contentless words in the file name is
simply a waste of storage space, screen space and the time you spend on
parsing and reading it.


--
Lee Sau Dan §õ¦u´° ~{@nJX6X~}

E-mail: danlee(a)informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee

--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
From: LEE Sau Dan on
>>>>> "J" == J G Miller <miller(a)yoyo.ORG> writes:

J> On Wed, 14 Apr 2010 16:47:27 +0000, Chris F.A. Johnson wrote:

>> It's one of the factors that gave me an instant dislike of perl!

J> Emacs lisp also leans towards using "my" as a prefix for user
J> defined variables and functions to distinguish them from
J> similarly named entities in the official released code.

I don't think so. I've read a lot of Elisp code during the past 17
years of using Emacs, and I've also written non-negligible amount of
Elisp code myself, too. I don't see my-.* symbols much. At least not
enough for me to develop the tendency to name my own symbols under such
a scheme. None of the coding examples I've seen (e.g. in the Elisp
manual) contain such symbol names.

(BTW, I like Perl, and I use the "my" keyword a lot! But that's not a
part of a name. So, it's a different thing.)


--
Lee Sau Dan §õ¦u´° ~{@nJX6X~}

E-mail: danlee(a)informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee

--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---