in reply to Re^2: What should I name my module?
in thread What should I name my module?

Personally, I'm still lost as to the point of your module. (Which is likely more a reflection on me than on your module.)

You've provided some sample input. (Thanks.) How about some sample output? What does this module give you or do for you? I don't know what modeling a class hierarchy means or is meant to acomplish. Point out dependency loops? List properties of leaf classes?

- tye        

Replies are listed 'Best First'.
Re^4: What should I name my module?
by BerntB (Deacon) on Sep 08, 2005 at 07:52 UTC
    Oh, I am a terrible pedagogue.

    The idea is, basically, to build something that follows a specification/rule system. It builds models using parts mapped onto objects.

    It has support for changing an object tree using the rule system.

    The output is in XML. A simple cgi user interface, first.

    This specification for data can be defined as: Superset of XML Schema, with code that do tests.

    After designing and writing an app that will solve my problem, I find that the data model is easily mapped onto the XML hierarchical tag structure. (-: A long and hard way to rediscover XML. :-) A version 2 of my program would probably use XML Schemas as part, for the familiarity to users.

[reply]

In Section Seekers of Perl Wisdom