On Sun, Jun 20, 2004 at 12:45:37PM -0400, Derek Atkins was heard to remark: > [EMAIL PROTECTED] (Linas Vepstas) writes: > > > On Sun, Jun 20, 2004 at 12:16:20PM -0400, Derek Atkins was heard to remark: > >> > void qof_class_foreach (QofClassForeachCB, gpointer user_data); > >> > >> We already had qof_object_foreach_type(); why do we need a > >> qof_class_foreach()? > > > > I am thinking about merging object and class into one thing. > > Maybe. Any remarks pro or con appreciated. > > What's the difference now?
Well, you're the guy who made this distinction when you wrote the code way back when ... :) -- object defines the relationship to the 'backend'. -- class defines parameters. historically, parameters could only be queried, and 'class' was used only by the query subsystem. The objects were used only for the backend interaction. > So what's your conceptual distinction between a QofObject and a > QofClass? I dunno. Something that only knows about parameters vs. something that knows about lots of other things as well. Maybe 'class' should be a base-class for 'object'. Better names for these things might help too ... --linas -- pub 1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <[EMAIL PROTECTED]> PGP Key fingerprint = 8305 2521 6000 0B5E 8984 3F54 64A9 9A82 0104 5933 _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
