5 Mar 2009 14:05
[Bug 89167] support for utility classes
Oliver Kellogg <okellogg <at> users.sourceforge.net>
2009-03-05 13:05:16 GMT
2009-03-05 13:05:16 GMT
https://bugs.kde.org/show_bug.cgi?id=89167 --- Comment #2 from Oliver Kellogg <okellogg users sourceforge net> 2009-03-05 14:05:14 --- Import could be done using the following rules: Ada package without any subprograms => UML package Ada package with subprograms which are all primitive operations of tagged types => UML package Ada package with subprogram(s) which are non primitive on a tagged type => UML class with stereotype <<utility>> Using a fixed set of rules implies that code may be generated different from its imported form. For example, according to the above rules, an Ada package containing several tagged types would be imported as a UML package with nested classes. However, on generating Ada code from the UML, the nested classes would be generated as child packages. The best solution would certainly be to allow the user to specify the mapping per Ada package (choose between UML package and utility class on import) but that is difficult to implement. -- -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA(Continue reading)
RSS Feed