Hello.
Suppose, I have an app that, for example, works with a database. It
can write to the db, it can select things. There is a class that works
with the database, a class that controls that class and a class that
interacts with the gui. And, of course, there is some testing code in
all the three "layers".
Is it a good idea to split all those classes into categories for
writing, reading and testing? For example, Database (Writing),
Database(Reading), Database(Testing) and so on? Or is it a silly thing
to do for some reason?
Thank you in advance for your replies.
Timofey.
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
