Re: Xcode 2 Question
Re: Xcode 2 Question
- Subject: Re: Xcode 2 Question
- From: Markian Hlynka <email@hidden>
- Date: Thu, 5 May 2005 16:19:14 -0600
Removing the typedef doesn't help.
But I'd recommend doing it anyway, it's completely redundant in C++.
I realize this. There was, originally, a Good Reason(tm) for which I
used the typedef. Darned if I remember what it was now. I think it had
to do with some of my c-style function or something not allowing me to
use my type names as I wanted to. I'll think about removing them and
seeing what happens.
Additionally, I'd recommend using the class keyword instead, as a
workaround, and because I can't think of any reason not to:
There is no technical reason that I shouldn't. Ideologically, I did it
because a struct means that all members are public by default. Thus, I
use struct when I have a data type that I want to use to group
something together, but expect its data members to be accessed
directly. If I used a class, I would go for hiding the data members.
Or, that's what I tell myself. I just found a class where for ease of
use, I made everything public. Well, at least the class means I
explicitly state what's public. If it's a struct, I presume that it's
all intended to be public.
Anyway, if this isn't fixed, I'll file a bug; I can't recall if I ever
did, or was told that it was a known issue, or what....
It's not fixed, file away.
Turns out I did file it, quite some time ago. Radar: 3855755,
27-Oct-2004 03:10
So it really ought to be fixed by now.
Markian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden