If you use double parentheses, you won’t get the warning:
if ((self = [super init])) {
}
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at
On 10/11/2011, at 12:04 PM, Ian Joyner wrote:
It's the old I have a hammer so everything looks like a nail, but in C++'s
case it's I have a programming language, so everything gets put in that. We
really need to get away from that kind of thinking about programming
languages and get back
for multiple bundle
products, so when the host loads our products this issue surfaces.
And yes, this thread does belong on the objC list and will be moving it there
(I didn't realize there was a objC list when I originally posted).
On Nov 9, 2011, at 12:08 AM, Karl Goiser wrote:
I
Your first option looks better to me!
:-)
All I’m saying is that Objective C is a very mature language now and if it has
been able to get by without adding this extra layer of complexity, why
introduce it for an edge case to address a situation where people are expecting
it to act like C++?
I think there is another solution that doesn’t involve making the language more
complicated:
I would complain to the suppliers of the bundles with conflicting class names.
They know they are delivering into an environment with a flat namespace. It is
up to them to defend against this sort of
pattern is a fix for inadequately designed languages.
Karl
On 02/08/2011, at 2:02 PM, Kyle Sluder wrote:
On Mon, Aug 1, 2011 at 7:14 PM, Karl Goiser li...@goiser.com wrote:
Wow, class methods finally get the tick of approval! Only 30+ years after
being specified in the Smalltalk standard
Hi Greg,
Is that wishful thinking or a hint about the future?
:-)
All I have to say is: yes please!!
Regards,
Karl
On 03/08/2011, at 5:43 AM, Greg Parker wrote:
On Aug 1, 2011, at 9:02 PM, Kyle Sluder wrote:
if we had class storage (which in practice would be no different from
static
Wow, class methods finally get the tick of approval! Only 30+ years after
being specified in the Smalltalk standard..
Forget about singletons: they are just a workaround for not having class
methods/variables.
Each class is a single object that exists for the life of the application
How many debugger windows/panes do you want open at a time?
I can tell you how many I want and need: 1. I can only debug one app, why
should I have 7? All interfering with my editing?
I have tabs containing the current set of files that I am editing. Every one
of them has an open debugger
Hi David,
On 25/07/2011, at 8:44 AM, David Duncan wrote:
On Jul 24, 2011, at 3:34 PM, Karl Goiser wrote:
So, I tried the trick with behaviours, assigning debugging to a special tab.
Sure it seems to work, but it doesn’t. I still get debugger panes crowding
out my editing windows
I think that we need to differentiate between the new features that could
easily have been put into Xcode 3, and the changes that have been made (to my
mind) to wreck a great UI.
Schemes and Git and the like do not justify the damage…
Why would I want to see Interface Builder objects when I am
The issue is that a boolean value is not numeric, but the denotation
of truth or falsehood. If you take boolVar to represent the
proposition that Socrates is a man, then saying:
if (boolVar == YES)
is equivalent to:
if (Socrates is a man == YES)
This is obviously a correct expression -
Dear Markus and others,
This is a problem that I have had with an application of mine,
iCalViewer, which displays a window on the desktop.
What happens is that you can find a window level which draws the
window under the desktop icons and over the desktop itself. However,
at that level,
Hello,
I'm creating a borderless window whose content view uses Core
Animation...
When I do this, the window is drawn without any shadow no matter the
alpha of the content.
- a borderless window with a normal view draws the window's shadow.
- a normal window with a content view which
14 matches
Mail list logo
