FROM : Soares
DATE : Fri Apr 27 14:28:27 2007
I'd like to know more about this. I'm currently using C-style arrays for
storing 3D model data such as vertices, vertex indices, normals, texture
coordinates etc.
Some of the models are large and naturally C-style arrays are the optimal
kind of array for this sort of thing, but as I'm also using Core Data and
shoving most things at the GPU and so iteration is less problematic than if
one were in immediate mode, and I'd quite like some of the flexibility and
security offered by NSArrays. Is using an NSArray of NSNumbers realistic in
this sense? I mean how big is an NSNumber object for instance, considering
there might be 100,000's of them?
F.
On 26/04/07, Philippe Mougin <<email_removed>> wrote:
>
>
> It depends how the NSArrays you deal with are implemented (remember
> that NSArray is a class cluster -- in other words, a semi-abstract
> class). For instance, in F-Script we make extensive usage of NSArrays
> (in particular arrays of NSNumbers), but we do so using an
> implementation that transparently make them as small and as fast as C-
> style arrays, in most cases.
>
> Philippe Mougin
>
> _______________________________________________
>
> Cocoa-dev mailing list ( <email_removed>)
>
> 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:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
>
DATE : Fri Apr 27 14:28:27 2007
I'd like to know more about this. I'm currently using C-style arrays for
storing 3D model data such as vertices, vertex indices, normals, texture
coordinates etc.
Some of the models are large and naturally C-style arrays are the optimal
kind of array for this sort of thing, but as I'm also using Core Data and
shoving most things at the GPU and so iteration is less problematic than if
one were in immediate mode, and I'd quite like some of the flexibility and
security offered by NSArrays. Is using an NSArray of NSNumbers realistic in
this sense? I mean how big is an NSNumber object for instance, considering
there might be 100,000's of them?
F.
On 26/04/07, Philippe Mougin <<email_removed>> wrote:
>
>
> It depends how the NSArrays you deal with are implemented (remember
> that NSArray is a class cluster -- in other words, a semi-abstract
> class). For instance, in F-Script we make extensive usage of NSArrays
> (in particular arrays of NSNumbers), but we do so using an
> implementation that transparently make them as small and as fast as C-
> style arrays, in most cases.
>
> Philippe Mougin
>
> _______________________________________________
>
> Cocoa-dev mailing list ( <email_removed>)
>
> 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:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
>
| Related mails | Author | Date |
|---|---|---|
| Soares | Apr 27, 14:28 | |
| Erik Buck | Apr 27, 17:02 | |
| Erik Buck | Apr 27, 17:04 |






Cocoa mail archive

