Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

get rid of ANTLR #75

Closed
yegor256 opened this issue Jan 14, 2016 · 14 comments · Fixed by #173
Closed

get rid of ANTLR #75

yegor256 opened this issue Jan 14, 2016 · 14 comments · Fixed by #173

Comments

@yegor256
Copy link
Owner

Let's get rid of ANTLR library and parse Xembly syntax using a more primitive approach. Just by string manipulations. It's not that complex.

@davvd
Copy link

davvd commented Jan 18, 2016

@yegor256 tagged this issue with "bug"

@davvd davvd added the bug label Jan 18, 2016
@davvd
Copy link

davvd commented Jan 18, 2016

@yegor256 thanks a lot for reporting, 15 mins added to your acc, pmt ID 000-3d107665

@krzyk
Copy link

krzyk commented Jul 6, 2018

@yegor256 this will help with outdated ANTLR library (some newer libraries, like groovy with invokedynamic, or new checkstyle need ANTLR4 and can't be used together with xembly).

@carlosmiranda
Copy link
Collaborator

@0crat in

@0crat 0crat added the scope label Aug 10, 2018
@0crat
Copy link
Collaborator

0crat commented Aug 10, 2018

@0crat in (here)

@carlosmiranda Job #75 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Aug 10, 2018

Bug was reported, see §29: +15 point(s) just awarded to @yegor256/z

@Marti2203
Copy link

Marti2203 commented Aug 17, 2020

Hello, I am interested in tweaking this to use ANTLR4. If like my proposal, I can start with this.

@yegor256 yegor256 self-assigned this Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
Repository owner deleted a comment from 0crat Jan 24, 2023
@0crat
Copy link
Collaborator

0crat commented Jan 28, 2023

@carlosmiranda/z everybody who has role DEV is banned at #75; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Feb 2, 2023

@carlosmiranda/z everybody who has role DEV is banned at #75; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Feb 7, 2023

@carlosmiranda/z everybody who has role DEV is banned at #75; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

maxonfjvipon added a commit to maxonfjvipon/xembly that referenced this issue Jan 10, 2024
@yegor256
Copy link
Owner Author

@rultor release, tag is 0.31.0

@rultor
Copy link
Collaborator

rultor commented Jan 11, 2024

@rultor release, tag is 0.31.0

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Collaborator

rultor commented Jan 11, 2024

@rultor release, tag is 0.31.0

@yegor256 Done! FYI, the full log is here (took me 16min)

@yegor256
Copy link
Owner Author

@maxonfjvipon many thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants