Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OAW developer telco 2008-01-07"
(→Minutes) |
(→Minutes) |
||
| Line 33: | Line 33: | ||
#* All Eclipse related stuff will be developed on the Eclipse CVS | #* All Eclipse related stuff will be developed on the Eclipse CVS | ||
#* All non-Eclipse related stuff will be stay on the SF.net CVS. | #* All non-Eclipse related stuff will be stay on the SF.net CVS. | ||
| − | #* Thus, we will have a new module oaw_v5 | + | #* Thus, we will have a new module oaw_v5 in which we will use the HEAD |
#* Added value can be put into the oaw_integration module (e.g. oAW perspective, etc.) | #* Added value can be put into the oaw_integration module (e.g. oAW perspective, etc.) | ||
#* The various modules will be developed and released separately | #* The various modules will be developed and released separately | ||
Revision as of 18:29, 9 January 2008
Contents
oAW developer meeting 2008-01-07 20:00 CEST
Via Skype (host's skype name 'svenefftinge')
Attendees
Arno Haase
Bernd Kolb
Dieter Moroff
Markus Voelter
Peter Friese
Sven Efftinge
Karsten Thoms
Ueli Brawand
Agenda
- oAW 4.2.1 maintenance / oAW 5.0
- New Backend
- different call semantics among Xtend / Xpand
- Additional features
- New committer: Patrick
Minutes
- oAW 4.2.1 maintenance / oAW 5.0
- There will be no oAW 4.2.1 release. However, fixes and minor features can be developed within the 4.2 branch on our SF.net CVS
- All Eclipse related stuff will be developed on the Eclipse CVS
- All non-Eclipse related stuff will be stay on the SF.net CVS.
- Thus, we will have a new module oaw_v5 in which we will use the HEAD
- Added value can be put into the oaw_integration module (e.g. oAW perspective, etc.)
- The various modules will be developed and released separately
- Each module will have a module owener. Sven will start a Wiki page with a list of modules and owners.
- naming conventions: Projects (and thus CVS modules) will be named exactly like the plug-in they contain
- New Backend
- Arno is working on a new backend, which will require some changes to the existing frontends
- Question: when / how to perform those changes?
- Peer review: Bernd and Sven (Arno sends code by email)
- Affected frontends: languages, debugger, profiler (can be implemented afterwards), tracing (not yet available publicly)
- Current status:
- Process can be started using ANT - ready this week
- Mode of operation:
- Arno to finish work
- Bernd and Sven to review work
- detach debugger
- check-in backend
- attach languages
- re-attach debugger
- different call semantics among Xtend / Xpand
- Should be restructured, but how?
- Fulfill the Java model?
- Name Mangling = one flat namespace in backend, while in Xpand (where it is important), inject mangled names
- Frontend: Xtend / Xpand call semantics stay the same
- Backend: functions can be called by their fully qualified names. However, polymorphism will then be limited to functions with the same parameters
- The backend will support several names for the same function (i.e. the same in terms of caching etc.). This will support being able to call the same function both unqualified and fully qualified, and it will provide a basis for renaming functions e.g. in an extended import syntax. That feature is currently not supported by any of the oAW languages, but Scala has it.
- Additional features
- Polish for Xtext:
- Enhanced Outline (Sorting / Labelling / Icons)
- Builder to scan all Xtext files and construct an import index to facilitate importing in the editor
- Polish for Xtext:
- Patrick
- Paid by itemis, available full-time for oAW
- As always, we want to see some work before granting committer rights
- As usual, a voting will take place
Actions
- one
- two
Other Decisions
- one