that's a *great* feature.
There is an option in Eclipse to force the use of 'this.' for
members. I have that option set and don't use the prefix.
--
jason.vp.engineering.particle
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To
I don't buy that argument since since all of the core classes in Java
are written without prefixes of any kind, and many of the classes were
implemented before IDEs became popular. I do also think that the
convention would have been added to the Code Conventions for the Java
Programming Language
That was a choice made at Sun when they wrote the Java core classes,
our choice was to use a prefix. That's all. It's NOT going to change.
On Tue, Feb 23, 2010 at 12:07 AM, Kaj Bjurman kaj.bjur...@gmail.com wrote:
I don't buy that argument since since all of the core classes in Java
are written
Perhaps you should consider that the people who came up with Android's
convention had a lot more Java experience under their belt than the
people who came up with Java's convention had, way back when.
I'm not saying that makes the case, just that your argument-from-
authority here falls flat.
There is an option in Eclipse to force the use of 'this.' for
members. I have that option set and don't use the prefix.
On Feb 23, 12:39 am, Bob Kerns r...@acm.org wrote:
I'm not fond of 'this.member'. It seems to combine the worst of both
worlds -- an optional prefix that may or may not be
I like that document, but I'd add a caveat: don't go all gung-ho style
police. (I think that fits well with the overall tenor of the
document, but is worth being made explicit).
The point of style conventions is to make things easier, not provoke
arguments.
There is, in fact, some benefit from a
I'm not fond of 'this.member'. It seems to combine the worst of both
worlds -- an optional prefix that may or may not be used in different
places.
Though I understand why people use it in setters and constructors to
avoid manging their argument names -- real prefixes avoid that need.
On Feb 22,
On Feb 22, 8:05 am, Romain Guy romain...@android.com wrote:
I myself am not fond of prefixes, especially since languages like Java
already have this. when you need to distinguish local vars vs
members. Also, modern IDEs highlight fields differently from local
variables.
++
I don't use the m
On Feb 22, 12:39 am, Bob Kerns r...@acm.org wrote:
The point of style conventions is to make things easier, not provoke
arguments.
It succeeds at both.
There is, however, NEGATIVE benefit -- actual harm, from the Hungarian
Notation you find in Microsoft's code, which redundantly encodes the
prefixes are from another time.. now there are good IDEs.
More to write, More to explain and NO benefit.
Please use your favorite IDE, that is enough.
NM
On Mon, Feb 22, 2010 at 4:00 PM, fadden fad...@android.com wrote:
On Feb 22, 12:39 am, Bob Kerns r...@acm.org wrote:
The point of style
I love these threads where people throw in their opinions as if they're
fact. THIS IS A COMPLETELY SUBJECTIVE MATTER. If you like the prefixes, use
them. If you don't, don't. It's that simple. There's really nothing to argue
about here. There's is no good, bad, right, or wrong way about this.
Do
TreKing wrote:
I love these threads where people throw in their opinions as if they're
fact. THIS IS A COMPLETELY SUBJECTIVE MATTER.
But wait! Isn't that an opinion?
:: ducks the rotten tomatoes tossed my way ::
:-)
--
Mark Murphy (a Commons Guy)
http://commonsware.com |
with all due respect, it's not quite just a subjective matter :-)
i *really* like visual clues to denote the scope of variables etc, so
i used to use the m prefix. however, i stopped, and now i use an
explicit this to denote a reference to a data member.
why? well, if you use a prefix, then
On Mon, Feb 22, 2010 at 4:45 PM, TreKing treking...@gmail.com wrote:
THIS IS A COMPLETELY SUBJECTIVE MATTER.
Computer science teaches us to 'always do the simplest thing that will work'.
--
Greg Donald
destiney.com | gregdonald.com
--
You received this message because you are subscribed to
On Mon, Feb 22, 2010 at 4:50 PM, Mark Murphy mmur...@commonsware.comwrote:
But wait! Isn't that an opinion?
Nope, that's fact =P
On Mon, Feb 22, 2010 at 4:56 PM, Jason Proctor
jason.android.li...@gmail.com wrote:
why? well, if you use a prefix, then bean-centric code can't derive the
The Android Code Style Guide explains the conventions used for field
names: http://source.android.com/submit-patches/code-style-guide#field_names.
Sam Dutton
On Feb 22, 5:52 am, Christ wutie...@gmail.com wrote:
Hi guys,
I saw many sample codes that each variable contains the 'm' prefix. I
16 matches
Mail list logo
