Sorry,
Forgot to include dev-list.
Adolfo Sánchez-Barbudo Herrera escribió:
Hi Bob, Philippe,
I'm not particularly in a hurry with this, I'm quite busy this month so
I think that I won't be able to tackle the LPGv2 migration until
November. However it's important for OCL to migrate the grammars and
parser infrastructure to LPG2 as soon as possible, since the migration
has already started in a branch and several patches are concurrently
being committed to HEAD, so we won't want to deal with a big effort
when merging the migration to the HEAD.
I'm CCing ocl-dev list so the remaing OCL tean members can expose their
considerations/concerns about this.
We would also appreciate that you could provide a more precise
estimation of the 2.0.19 release date.
Cheers,
Adolfo.
Robert M. Fuhrer escribió:
Hi Adolfo,
Thought you might be interested in an update: it looks as
though
we might get 2.0.18 out the door this week. Then we can start the CQ
for that version.
That said, 2.0.18 won't include all the necessary changes to
the
runtime to support the generation of "prosthetic" AST nodes (used when
the parser does error recovery), which will come in the following
release. I don't know yet when that work will get done, but it's likely
that it will happen in the next few months. It's partly due to that
delay that we decided to push 2.0.18 out with just the current set of
fixes, rather than waiting for the rest of the prosthetic work to be
completed.
As far as the Orbit contribution is concerned, obviously
2.0.19
will have a fairly important new feature in it which solves a problem
plaguing many IDE developers (What to do about an AST when the parser
is forced to do error recovery?), so in some sense it might be best to
wait for that before putting LPG into Orbit. On the other hand, the
delay in getting LPG into Orbit might be too much for some clients. I
don't know which path is best for the community, all things considered.
On Sep 4, 2009, at 1:07 PM, Adolfo Sánchez-Barbudo Herrera
wrote:
Hi Robert,
We will wait until 2.0.18 comes up, so it's not necessary to raise any
CQ about 2.0.17 :)
Let's keep in touch.
Cheers !!!
Adolfo.
Adolfo Sánchez-Barbudo Herrera escribió:
Hi Robert,
Nice to hear from you. I think we could wait some weeks. I'll forward
your email to OCL dev-list so we can discuss it. Hopefully, nobody will
be reluctant to wait until 2.0.18 ;)
Cheers !!
Adolfo.
Robert M. Fuhrer escribió:
Hi Adolfo,
[Apologies for not having responded to your newsgroup post; it's been a
particularly intense work period for me the last couple of weeks.]
Although v2.0.17 is the latest LPG version at the moment, v2.0.18 is
due out fairly soon (so says Philippe Charles, the primary author), and
has some potentially very useful improvements in the area of error
recovery.
As a result, I've been delaying the initiation of another CQ for LPG in
hopes of avoiding doing two in rapid succession.
I've also been intending to get LPG into Orbit, since as you say it's
useful to a wider audience than just IMP users.
Also, although v2.0.17 is mostly a bug-fix release over 2.0.16, it
includes one fairly significant fix to the runtime (as I recall, it
resolves a bug causing the parser driver to hang on certain erroneous
inputs). As a result, I believe 2.0.17+ is a better candidate for Orbit
than 2.0.16.
As of his latest communication, Philippe believes 2.0.18 will be
released within the next few weeks. If that's too long a delay given
your project's constraints, let me know, and I'll start a 2.0.17 CQ,
and perhaps you can initiate the Orbit process once that's in place.
On Sep 3, 2009, at 1:52 PM, Adolfo Sánchez-Barbudo Herrera wrote:
Hi Robert,
I'm not sure if I have made any presentation before, so let me do it...
I'm Adolfo Sanchez-Barbudo Herrera, an employee of a company in the
Canary Islands (Spain), called Open Canarias. I'm currently working as
committer in a couple of projects in Eclipse: MDT-OCL (An Eclipse
Modeling subproject) which has been using LPG since some years ago, and
Orbit, the official project in which all third party plugins reside.
I'm privately mailing to you, because as the IMP project leader I guess
we may stablish some collaborations. I have tried to contact you or any
mate of the IMP team via the newsgroup with no luck, so I have decided
to directly mail you.
One of the goals of the MDT-OCL project for Helios release, is adopting
and aligning with the last version of LPG, which, AFAIU, is 2.0.17. In
order to achieve this, an official Eclipse project must have their
third party plugins as bundles in the Eclipse's Orbit project. To do
this several IP legal process must be solved, and the third party
library must be converted in a suitable bundle in the Orbit project.
I have already checked that you have raised a CQ against LPG v 2.0.16,
which has already been accepted. This is pretty good, however, the
bundle is not in the Orbit repository yet. Fortunately, I could help in
this task since I have been granted with privileges to create and
commit Orbit's bundles. On the other hand, I have been working on the
last LPG v 2.0.17 version, which I don't really know how it differs
with the previous one. So, we could decide which is the proper LPG
version which would be included in the Orbit, LPG v2.0.16 or LPG
c2.0.17 ?
I could work on v2.0.16 to include it Orbit right know since it has
already been approved in CQ. If you would be happy to have LPGv2.0.17
in Orbit, we should previously solve the IP process.
Please, let me know about your interests on having 2.0.16 or 2.0.17 in
Orbit.
--
Cheers,
- Bob
-------------------------------------------------
Robert M. Fuhrer
Research Staff Member
Programming Technologies Dept.
IBM T.J. Watson Research Center
--
|
Adolfo
Sánchez-Barbudo Herrera
adolfosbh(at)opencanarias(dot)com
C/Elías Ramos González, 4, ofc. 304
38001 SANTA CRUZ DE TENERIFE
Tel.: +34 922 240231 / +34 617 718268 |
--
|
Adolfo
Sánchez-Barbudo Herrera
adolfosbh(at)opencanarias(dot)com
C/Elías Ramos González, 4, ofc. 304
38001 SANTA CRUZ DE TENERIFE
Tel.: +34 922 240231 / +34 617 718268 |
|
