> 1) No - the action tag is useful! Yea, Pat gave a good creative example of why it's good. I find your argument very enlightening though.
> 2) Why? The property tag is flexible - not confusing! Unix has two commands: cd and cat. cd changes directory. cat prints the contents of a file. Two different commands to do two different things. In webwork however we have a single command to do both these things and it's called "property", which btw doesn't really say much. Had an operating system had a command like that you would not be pleased: c:\> property foo c:\foo>property bar.txt contents of bar.txt c:\foo> How logical is that really? Besides the obvious readability aspects of having a tag for printing a property and another for modifying the stack, the code for PropertyTag (or rather BasicPropertyTag in the CVS version) is rather ugly due to the fact that it's really two tags. If nothing else, the code should reflect this with one PrintPropertyTag and another PushPropertyTag. Changing BasicPropertyTag to do exactly what it does not but doing it by extending PrintPropertyTag would be trivial and open up possibilities for the users. It would also make the code more orthogonal and readable. // Anders Hovmöller ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
