Talents Presentation at ESUG 2011
•Descargar como KEY, PDF•
0 recomendaciones•1,036 vistas
Recomendados
Más contenido relacionado
Último
Último (20)
Destacado
Destacado (20)
Talents Presentation at ESUG 2011
- 1. Talents: Dynamically Composable Units of Reuse Jorge Ressia, Tudor Gîrba, Oscar Nierstrasz, Fabrizio Perin and Lukas Renggli www.scg.unibe.ch
- 2. Reuse
- 3. Mixins
- 9. Traits
- 10. Class = Superclass + State + Traits + Glue methods
- 13. Problem
- 15. MooseEntity FAMIXEntity ... FAMIXType aFAMIXClass isTestClass 2 FAMIXClass Key instance-of isTestClass 1 message send lookup aFAMIXClass self inheritsFrom: 'TestCase' 3
- 17. Talents
- 18. MooseEntity FAMIXEntity ... 3 aJeeClassTalent FAMIXType talent isTestClass aJeeClassTalent FAMIXClass aFAMIXClass 2 inheritsFrom: 'TestCase' 4 aFAMIXClass Key instance-of 1 message send lookup aFAMIXClass acquire isTestClass
- 19. Operations
- 20. Define a method
- 21. jeeClassTalent defineMethodNamed: #isTestClass performing: '^ self inheritsFrom: #TestCase'.
- 22. Exclude a method
- 23. jeeClassTalent excludeMethodNamed: #isTestClass
- 24. Replace a method
- 25. jeeClassTalent replaceMethodNamed: #isTestClass performing: '^ self inheritsFrom: #TestCase'.
- 27. Composition
- 28. aClass := FAMIXClass new. aClass acquire: ( javaClassTalent , jeeClassTalent ).
- 29. Alias
- 30. aClass := FAMIXClass new. aClass acquire: javaClassTalent , ( jeeClassTalent @ {#isTestClass -> #isJEETestClass})
- 31. Exclusion
- 32. aClass := FAMIXClass new. aClass acquire: javaClassTalent , (jeeClassTalent - #isTestClass).
- 33. Implementation
- 34. Reflection
- 35. scg.unibe.ch/research/ bifrost
- 38. Class Talent Object
- 39. Class Talent Object
- 40. Class Talent Talented Object
- 41. Flattening
- 42. Scoping
Notas del editor
- \n
- \n
- \n
- Since My Rectangle is a composition, I cannot access the behavior in MColor or MBorder exclusively.\nMixins have to be applied one at a time.\n
- \n\n
- Since My Rectangle is a composition, I cannot access the behavior in MColor or MBorder exclusively.\nMixins have to be applied one at a time.\n
- \n
- Since My Rectangle is a composition, I cannot access the behavior in MColor or MBorder exclusively.\nMixins have to be applied one at a time.\n
- Originally in self\nthen developed by nathanel scharli in smalltalk.\nWith operations\n\n
- Self traits do not provide composition operators.\n
- Originally in self\nthen developed by nathanel scharli in smalltalk.\nWith operations\n\n
- Originally in self\nthen developed by nathanel scharli in smalltalk.\nWith operations\n\n
- \n
- that it is a cool, large and open source platform for data and software analysis that is being increasingly used in industrial projects\n
- Class oriented. Fixed on classes.\nClass explosion. \nGet the example from simon.\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- Another example will be the Simon one.\nTypically for a graph algorithm you have a graph structure which is built from Famix entities, yet nodes and edges require specific behavior and state to preserve algorithmic complexity.\nRight now we do some model transformations, that is we create the graph structure from the Famix model to run the algorithm with, then we can reflect on the graph or inject the result back into the Famix entities if necessary. But we need to create this disposable graph structure anyway.\nI always thought it would be much cooler to add behavior and state for graph computation directly into the Famix entities, run the algorithm, get the results, then remove such state and behavior from entities to preserve space. Especially this last point was not apparent in the Moose JEE example.\n
- \n
- \n
- \n
- We see that there are many different ways of doing reflection, adaptation, instrumentation, many are low level.\nAnd the ones that are highly flexible cannot break free from the limitations of the language.\n
- Adaptation semantic abstraction for composing meta-level structure and behavior.\n
- \n
- \n
- \n
- \n
- \n
- \n