Version: Alpha 1.2 (using KDE KDE 3.1) Installed from: Mandrake RPMs Compiler: gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk) I followed the instructions OS: Linux 1stly umbrello rocks, I use it for my Software eng subjects all the time at uni. Here is the perl module I generated (only some of it). note that there are some tags or comments like "=head1 EMAIL" I figure they should not be there as I did not specify that they should be. Have I missed an option, or is this a bug. what are they and what are they used for if they are not a bug. package email; =head1 EMAIL =cut =head1 PUBLIC METHODS =over 4 =item email_from_id Parameters: =over 8 =item theId : The Id supplied from the user =back Description: =cut sub email_from_id { } =item email_from_name Parameters: =over 8 =item theName : The name supplied by the user or test data =back Description: =cut sub email_from_name { } =item has_email
Subject: Re: [Uml-devel] New: perl code generation unknown tags in module Could it be, that the perl generator is completely broken? I never used perl, but the generated code doesn't make much sense for me. Maybe we should remove the perl generator.
I believe that this is a case of the perl generator not being completely implemented. The simpleCodeGenerator interface, upon which it is currently based, wont allow for the user to specify options for code generation that are specific to the language (such as C++ and Java currently have). This is not a bug, but a wishlist item then. As far as the Perl generator not generating usable code, that IS a bug, and if that is the case, I would suggest that the Perl generator be removed temporarily from the distribution until it can be improved sufficiently. As I am planning anyways to update the Perl generator in the future, so I volunteer to do this.
Having looked a little bit more, I believe this is a wishlist item. The code, such as is generated, is somewhat usefull, even if the user doesnt get "full" control of the generation as desired.
Recently, work has been on the perl generator. Can we close this?
*** Bug has been marked as fixed ***.