Posted
almost 12 years
ago
by
[email protected]
(Andrew Forward)
Minor point about the reusable syntax, I would consider either using Json like notation { a: y, b: x } Or PHP, ruby style hashes (note that ruby supports the Json notation too, just showing the "old" format a => y -- aforward
|
Posted
almost 12 years
ago
by
[email protected]
(Timothy Lethbridge)
Yes, you are right. We will have to do some more analysis. In the case you have given, for syntactic clarity, I thin it would be necessary to place all the 'substitution rules in braces as a block. Timothy C. Lethbridge, PhD, P.Eng., I.S.P., CSDP Professor of Software Engineering and Computer Science
|
Posted
almost 12 years
ago
by
[email protected]
(Geoffrey Guest)
Seems very dangerous or unpredictable to use regex here. We should make the user have to be more specific about what they are renaming for example use ReusableModel.ump alias class x => a class x { alias previousMethodName => myNewMethodName; alias previousAttributeName => myNewAttributeName;
|
Posted
almost 12 years
ago
by
[email protected]
(Timothy Lethbridge)
I like this option. We do need to analyse a little what Umple would be capable of doing as opposed to the something like AspectJ. One thing about AJ is you can specify separate pattern expressions that get merged together to make the match using various boolean operators. Another thing i was thinking of doing was
|
Posted
almost 12 years
ago
by
[email protected]
(Geoffrey Guest)
I don't know if this is either feasible, or what we would want, but it seems more in line with our current syntax to do it sort of mixin - like because right now, the way that you would do the above code injection would be: --------------aspect.ump------ --------- class A { before setName { "AOP in Umple" }
|
Posted
almost 12 years
ago
by
[email protected]
(Andrew Forward)
Sounds good. I would look at the syntax of other AOP frameworks to see Umple could adopt a similar syntax for consistency (i..e We support AspectJ style method aspects....) andrew f -- aforward
|
Posted
almost 12 years
ago
by
[email protected]
(Miguel Garzon)
Hi, We have recently created an Umple poster concerning the separation of concerns principle and how we can achieve this with Umple. Now, we are planning to write a paper to discuss about how we can *unify aspect orientation and object oriented programming *in one single modular unit (an umple class).
|
Posted
almost 12 years
ago
by
[email protected]
(Geoffrey Guest)
Excellent, this works
|
Posted
almost 12 years
ago
by
[email protected]
(Geoffrey Guest)
Hello folks, I been fine up until sort of recently when editing jet files, what has happened is that when i build templates it get put into the cruise/compiler/java/ instead of src/cruise/compiler/java/ any fixes? much thanks Geoff
|
Posted
almost 12 years
ago
by
[email protected]
(Timothy Lethbridge)
Bravo! Timothy C. Lethbridge, PhD, P.Eng., I.S.P., CSDP Professor of Software Engineering and Computer Science / Professeur Titulaire de g�nie logiciel et d'informatique Facult� de genie / Faculty of Engineering University of Ottawa / Universit� d'Ottawa Tel: 613-562-5800x6685 Fax: 613-562-5664 Mobile: 613-252-1850
|