> Users will have to learn POE notations. Why not use the same > vocabulary and concepts from something that is know to work and > that a lot of people already know?
I totally agree with this. the POE efforts should concentrate on more important issues than designing notation. if we can reuse language that has been carefully desgined elsewhere then let's leverage the POE efforts and move on to other parts of the desgin. to POE developers it won't make any difference whether they have to learn the UML or some other notation (just reiterating Torvald's point). and as was pointed out before, selecting the UML as the notation of choice will make Perl and POE more eligible amongst crowds that currently only work in C++/Java. Additionally, since design tools already exist for UML the POE team's efforts to create tools will reduce to modifying existing code. I do agree that UML is more than we need, but we don't have to use all of it. - e
