Re: Table View Blues

FROM : <rixstep000
DATE : Mon Nov 18 14:10:09 2002

> > Even if I could associate data - without creating a class, something
> > I would prefer, as this is just cold data to me and it's going to
> > have to be formatted as CSV or TSV - with each record in a table
> > view, I would still be stuck - or so I think - with individual calls
> > to free() whenever my user wanted to start a new file.

> I don't understand. If you would like to allocate one big chunck of
> memory and manage it on your own - go ahead. Nothing is going to stop
> you. Objective-C is a superset of C after all.

No, I don't think you do. Sorry if I was unclear.

It's got nothing to do with languages. It has a bit to do with the API. But mostly it has to do with the underlying memory management in the operating system - or any layer thereof the API wants to put on top.

In Unix, AFAIK, calloc and malloc are true primitives, whereas in Cutler's Win32 they are not - they resolve to his own memory management schemes - which in this case are essential to survival.

You can never get away from the task of loading data into a program. What you must get away from here is the bottleneck of having to deal with potentially 100's of 1000's of recursive dealloc calls when a view is to be vacated and repopulated.

Cheers, R.
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.