Perl6 #47
Open
Perl6 #47
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Avoid some deprecated API items - Java approach changes, also related to API - Plenty of compliant's about unused variables / methods / functions Some solutions are suspect and perhaps a matter for discussion I found it helpful to Install both the PDE and the "Eclipse Platform SDK", It quickly identifies many deprecated API usage.
Attempt to reuse "run" functionality in Perl-5 Debug to "run" Perl-6 Scripts. I run into a bump in org.eclipse.team.core.IFileTypeInfo where the magic handling on the Perl-5 interpreter may be a bit messy. It was not clear to me how to un-tangle the highly cross-wired method calls. I suspect this is not a good solution. It may be better to start fresh with an entirely new Debug OR perhaps an independent Debug for Perl-5. Being new to this its all just conjecture.
Contributor
|
Hi Victor, what about starting a general discussion about perl6 support, which is - if you ask me - too different from perl5 to squeeze into EPIC. So, instead, why not take a clean-slate approach based on state-of-the-art toolsets like LSP[1] and come up with a proof-of-concept implementation? I'd be happy to join the experiment. [1] https://microsoft.github.io/language-server-protocol/implementors/servers/ |
Author
|
Sure I'd love to talk; contact me directly as ancient dot wizard at verizon dot net |
Author
|
Let me know if this gets to you. I’ve been attempting to respond; but I have no idea if this is working.
…-victor
From: Oliver Trosien [mailto:notifications@github.com]
Sent: Sunday, January 06, 2019 09:52
To: jploski/epic-ide
Cc: Victor; Author
Subject: Re: [jploski/epic-ide] Perl6 (#47)
Hi Victor, what about starting a general discussion about perl6 support, which is - if you ask me - too different from perl5 to squeeze into EPIC. So, instead, why not take a clean-slate approach based on state-of-the-art toolsets like LSP[1] and come up with a proof-of-concept implementation? I'd be happy to join the experiment.
[1] https://microsoft.github.io/language-server-protocol/implementors/servers/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#47 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AG01dLia92DskzwctyAV4fSf7b-fPzrLks5vAhuhgaJpZM4SBcIO> . <https://github.com/notifications/beacon/AG01dAN6m7ZQ-lKBAwT52ACQvQdnabtcks5vAhuhgaJpZM4SBcIO.gif>
|
- Learn about adding plug-ins to Eclipse
- Use the EPIC Plug in as a template for the learning process
and hopefully gaining a good deal of code-reuse and collaboration
- Answer the question; Is it viable to add Perl6 support to the
existing EPIC solution? YES it is
CONS:
- Existing code has a large technical debt
- The maintainer is unwilling to move forward to a modern Java
and Version of Eclipse. I proposed fixes and they were rejected.
- Some of debt comes in the form of using NON-Approved/NON-API code
That I believe are properly solved using end-points. And
plenty of deprecated code usage which I found solutions for.
PROS:
- I experimented with EPIC and Eclipse 2019-12 and would be pretty
easy to port. Then re-factor the other issues over time to clear
much of the technical debt and improve those areas that both P5
and P6 can share
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No expectations here. There are several API changes for moving away from deprecated items to the newer API. Many are very small and simple. It includes an item or two we've already spoken about, so ignore them. Ignore that I'm using Java 8.
I commented out many items that were not being used. Its your call, I like clearing noise warnings so I can find the important stuff.
I'm not even sure you'll want the perl6 branch, unless it makes it easier for you to merge useful changes you like into testing.
-Cheers!