Just like we cleaned up the Field_* classes, I would like to begin
cleaning up the Item_* classes. Currently, like was the case with the
field stuff, a myriad Item_* classes are housed in a few files in the
drizzled/ directory:
item.cc
item_buff.cc
item_cmpfunc. cc
item_func.cc
item_create.cc
item_row.cc
item_strfunc.cc
item_subselect.cc
item_sum.cc
item_timefunc.cc
As Brian has stated in the codestyle guidelines, we prefer to have a
header and codefile per class to aid in maintenance and readability --
anyone *really* enjoy dealing with .cc files that are 6549 lines long?
So, I would like to lead off the task of dividing and conquering the
Item classes. I propose we place all Item classes in their own
codefiles under an item/ directory within drizzled/. This would make
the file organization something like this:
/
/drizzled
/item
item_basic_constant.h/cc
item_ident.h/cc
item_num.h/cc
and so on...
Any objections?
If not, please mark the following blueprint as Approved and I will begin
work on this...
https://blueprints.launchpad.net/drizzle/+spec/item-class-file-reorg
Cheers,
Jay
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
