But, I’m not sure C++ is worth it on that platform.

class CSpreadsheet
{
CList m_Tasks;
};

This is what I expect to have now:

class CSpreadsheetViewer
{
void FindByRecID( RecID recID );
UInt16 GetColumnCount();
RecID GetColumnN( UInt16 n );
};

class CTaskViewer
{
void FindByRecID( RecID recID );
};

Obviously, the first is more pure C++. But the second is probably going to be more useful on the Palm.

Yes, what I’m talking about is heap (and stack, to be fair) vs. storage. Serializing is a fix for the problem, and it’s something I considered for a while, but by serializing the objects we introduce the cost I mentioned in switching applications: Namely, objects need to be saved when the application is switched out, and restored when switched back. I’m not talking about a dozen objects here, but thousands. That is, of course, if I intend to treat all of my data as C++ objects instead of datatable record IDs.

C++ objects could be a way to handle this. Some way to create C++ objects in storage and reference C++ objects by record ID woud solve these problems, but there seems to be some compiler work needed there. Codewarrior is closed source and dead, and PRC is nowhere near usable as yet (and may never be, since everyone seems to be distracted by the pretty lights of Copland… err, I mean, Cobalt).

Thanks for the comment, though. Sorry something cut it off.

class Foo
{
public:
Foo() : member(new Bar(initData))
{
}

Bar* member;
};

class Foo
{
public:
Foo() : member(initData)
{
}

Bar member;
};

In the first example, if you create a Foo object on the stack, then yes, you are correct, the member variable will be created on the heap. However, if you use the second definition of Foo, everything will be pushed onto the stack.
Now, I’m rereading your post, and this still doesn’t address your issue. If I understand what you’re saying, you want to have a class and be able to store its state externally. Basically, you need to serialize your classes. This is a fairly well explored topic, and what most people use to address this is the >> and