Beginner question - the differences between .h and .m
Beginner question - the differences between .h and .m
- Subject: Beginner question - the differences between .h and .m
- From: Alex Handley <email@hidden>
- Date: Sun, 23 Mar 2008 10:45:20 +0000
- Thread-topic: Beginner question - the differences between .h and .m
Hi, I have just started learning Cocoa and I have been reading the apple
tutorials but one thing they don't really explain is what is the purpose of
a .m and .h for each class. This is probably a silly question but coming
from a java im only used to seeing one class file.
Happy Easter
Thanks
Alex
On 22/03/2008 19:02 22 Mar 2008, "email@hidden"
<email@hidden> wrote:
> Send Cocoa-dev mailing list submissions to
> email@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.apple.com/mailman/listinfo/cocoa-dev
> or, via email, send a message with subject or body 'help' to
> email@hidden
>
> You can reach the person managing the list at
> email@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Cocoa-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Best Way To Lookup From a Huge Table (Thomas Engelmeier)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 22 Mar 2008 19:46:36 +0100
> From: Thomas Engelmeier <email@hidden>
> Subject: Re: Best Way To Lookup From a Huge Table
> To: John Stiles <email@hidden>
> Cc: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed;
> delsp=yes
>
>
> On 21.03.2008, at 21:51, John Stiles wrote:
>
>> std::map actually does more than NSDictionaryit sorts its entries
>> instead of keeping them in random order. Also, it copies its keys
>> instead of just keeping a reference to them, which is also more work
>> it would be a much fairer test if you used std::string* pointers for
>> your keys and values instead of std::string objects, but it'd also
>> be a little more work since you'd need a custom comparator and you'd
>> need to consider memory management (which boost smart pointers
>> apparently can manage pretty well).
>
> No need to pull in the whole boost overhead for smart(er) pointers as
> of gcc 4.0.
>
> #include <tr1/memory>
> using std::tr1::shared_ptr;
>
> And for the presorting time - TR1 includes also an unordered_map and
> unordered_set.
>
> Regards,
> Tom_E
>
>
>
> ------------------------------
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins (at) lists.apple.com
>
> http://lists.apple.com/mailman/listinfo/cocoa-dev
>
>
> End of Cocoa-dev Digest, Vol 5, Issue 459
> *****************************************
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden