Re^2: What should I name my module?

Replies are listed 'Best First'.
Re^3: What should I name my module? by itub (Priest) on Sep 08, 2005 at 00:38 UTC
Games::AutomobileFights ? ;-)	[reply]
Re^4: Rather WeirdDataModeller by BerntB (Deacon) on Sep 08, 2005 at 01:01 UTC
He,he. But no, the whole point is that this will be usable for other stuff. It is a modelling application for things that can be described as hierarchical parts. Say, think of a backend to an XML editor with an API so you can implement a data model which is semantically correct. What it is usable for, would be to give messages like "Error! There are too few vacation days left" or "Err! That material for table legs would need too large a diameter to look good". update: If I do a version 2, I'll integrate it with XML. There is an easy mapping between these object hierarchies and the XML tags.) (Also, fixed spelling.)	[reply]
Re^5: Rather WeirdDataModeller by xdg (Monsignor) on Sep 08, 2005 at 01:17 UTC
If it's a generic tool for dealing with hierarchies of things, maybe `Tree::` would be a good place? I think `Model::` would too generic -- better to try to describe what it is or does. (The "noun::adjective" style). As a last resort, maybe something under `Data::`. (c.f. Data::Grove or Data::Hierarchy.) -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply] [d/l] [select]
Re^6: Rather WeirdDataModeller by BerntB (Deacon) on Sep 08, 2005 at 03:12 UTC
Re^7: Rather WeirdDataModeller by xdg (Monsignor) on Sep 08, 2005 at 09:42 UTC
Some notes below your chosen depth have not been shown here


Come for the quick hacks, stay for the epiphanies.
	PerlMonks