My suggestion is this: Unless you are willing to switch to the full OOP paradigm, it is not worth the thought process.
inherited objects make sense but to code all the actions upon the object is almost mind boggling. At work we have a saying "If its new, you can consider anything you want, if not.. stay with what is working" Also.. there are several C++ mud codebases out there. Take a look at how they do it. Chris "Winston" Litchfield ----- Original Message ----- From: "Dale Kingston" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Sunday, September 28, 2003 3:42 PM Subject: Loading objects, as objects... > I know odd title, but I've been working on something lately and I'm a little > confused at how to go about this, (bare with me, most of my c++ knowledge is > self taught.) > > I'm trying to make my objects, objects. And have them much more object > oriented then they are currently. The problem I ran into tho is fread_obj, > now I had altered it to return an int for the nest value, for those > functions that need to know how it's nested. But I have other things that > need to read objects as well. And rather then making a new function for > every type of object loading. I wanted to make fread_obj work solely as a > object reading function. > > Now it didn't work well as a macro in the object_data cause it didn't like > the this = create_obj() stuff. And when I tried to be a smart ass and send > it a pointer to the object basically obj->fread_obj(fp, obj) ya well I > should have seen that coming. > > My question is this, how could I go about loading the objects. In a nice > clean non hackish way? Is their a way to have an object read itself in from > a file? > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom > >
