I'm aware that certain prefixes like set are bad news to use to start method
names for obvious reasons, but with the caffeine levels in my brain cell
running low, I'm at a loss to recall some of the others (is return verboten?).
Is there a list of reserved method prefix strings that you simply
On May 29, 2013, at 10:37 AM, Alex Zavatone z...@mac.com wrote:
I'm aware that certain prefixes like set are bad news to use to start
method names for obvious reasons, but with the caffeine levels in my brain
cell running low, I'm at a loss to recall some of the others (is return
On Wed, May 29, 2013, at 11:28 AM, Jens Alfke wrote:
There aren’t any forbidden prefixes that I know of, but there are ones
that should be used only for particular purposes, because the compiler
and/or runtime will make assumptions about them when they see that
prefix.
Apple selfishly
Now that my brain cell's caffeine levels are normalizing, I seem to recall
somewhere in the Cocoa docs stating that starting a method name with a string
like return is somewhat frowned upon.
Yeah, it must have been in the ARC docs. I remember that using init or new are
not good ideas.
That
On May 29, 2013, at 11:46 AM, Kyle Sluder k...@ksluder.com wrote:
Because clearly we don't need namespaces in a modern object oriented
programming language.
Oh boy. First off, to pre-empt any lengthy threads about this, people should go
and read last year’s discussion over on the
On May 29, 2013, at 2:46 PM, Kyle Sluder wrote:
On Wed, May 29, 2013, at 11:28 AM, Jens Alfke wrote:
There aren’t any forbidden prefixes that I know of, but there are ones
that should be used only for particular purposes, because the compiler
and/or runtime will make assumptions about them
Clang objected to a variable that started with new when we turned it into a
property, because then there was a method named new that wasn't doing what it
expected. I don't remember the details; I renamed it a long time ago.
On May 29, 2013, at 10:37 AM, Alex Zavatone wrote:
I'm aware that
