in reply to What should I name my module?

If you can't come up with even part of a name for it after you wrote most of it, then I can't come up with a name for it based on a vague or at least imprecise description.

Be much more specific and include at least some sample usage to help us understand what you mean by "model".

- tye        

  • Comment on Re: What should I name my module? (no idea)

Replies are listed 'Best First'.
Re^2: What should I name my module?
by BerntB (Deacon) on Sep 08, 2005 at 03:30 UTC
    If you can't come up with even part of a name for it after you wrote most of it, then I can't come up with a name for it based on a vague or at least imprecise description.
    Valid criticism. :-)

    I wrote it for another purpose then I think people might use it for. It's a solution looking for a problem.

    I added a part of a definition of a object at the top.

    Is that enough to understand?

    Update:

    If I put it like this:

    I wrote above "think of a backend to an XML editor with an API so you can implement a data model" A backend to a smart XML editor, might be a good definition.

    And it is hard to describe! I played the game 15+ years ago and it took a while to understand how it could be modeled without all the exceptions in the the rules making it really ugly code.

    I am proud, it was a hard problem that imho resulted in quite a neat package of functionality.

    There must be similar things, but I've never seen them. I am trying to describe something new. (-: And my verbal talents suck. :-)

[reply]

      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        

[reply]
        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