FROM : Ole Voß
DATE : Sun Oct 31 23:10:27 2004
>On Sun, 31 Oct 2004 16:18:17 +0100, Ole Voss <<email_removed>> wrote:
>
>
>>This also means, that I have to include the header file wherever I need it?
>>That could mean that the same class has to be recompiled tens of times -
>>right?
>>
>>
>
>The class implementation won't be recompiled, since that will reside
>in the .m file. If you're putting the implementation in your header,
>you're very, very confused.
>
>
You really shouldn't make it sound as if it was the most natural thing
in the world. Afterall, I don't include my '.m' files anywhere either
and they still get compiled - right?
So what's telling the compiler NOT to do it again? Is it the same
program that tells the compiler to forget that I already compiled that
class and forget that it exists unless I re-include it in the next
implementation that I need it in?
Somehow this sounds awefully messy. Why would I want to tell the
compiler again and again and again that a certain class exists? Why
doesn't it just remember, that I have created this class and that I'd
like to use it - afterall if I didn't want to use it, why did I include
it in my project?
>>So what possibilities do I have to create global variables?
>>
>>
>
>Declare them extern in a header, like you would in C.
>
>
Ok, that's worth a try.
Thanks,
Ole.
DATE : Sun Oct 31 23:10:27 2004
>On Sun, 31 Oct 2004 16:18:17 +0100, Ole Voss <<email_removed>> wrote:
>
>
>>This also means, that I have to include the header file wherever I need it?
>>That could mean that the same class has to be recompiled tens of times -
>>right?
>>
>>
>
>The class implementation won't be recompiled, since that will reside
>in the .m file. If you're putting the implementation in your header,
>you're very, very confused.
>
>
You really shouldn't make it sound as if it was the most natural thing
in the world. Afterall, I don't include my '.m' files anywhere either
and they still get compiled - right?
So what's telling the compiler NOT to do it again? Is it the same
program that tells the compiler to forget that I already compiled that
class and forget that it exists unless I re-include it in the next
implementation that I need it in?
Somehow this sounds awefully messy. Why would I want to tell the
compiler again and again and again that a certain class exists? Why
doesn't it just remember, that I have created this class and that I'd
like to use it - afterall if I didn't want to use it, why did I include
it in my project?
>>So what possibilities do I have to create global variables?
>>
>>
>
>Declare them extern in a header, like you would in C.
>
>
Ok, that's worth a try.
Thanks,
Ole.
| Related mails | Author | Date |
|---|---|---|
| Ole Voss | Oct 31, 16:18 | |
| Finlay Dobbie | Oct 31, 16:40 | |
| Ole Voß | Oct 31, 23:10 | |
| Finlay Dobbie | Oct 31, 23:47 | |
| Ole Voß | Nov 1, 09:07 | |
| Kevin Ballard | Nov 1, 09:37 | |
| Ole Voß | Nov 1, 13:09 | |
| Kevin Ballard | Nov 1, 13:11 | |
| M. Uli Kusterer | Nov 5, 00:15 |






Cocoa mail archive

