xembly
xembly copied to clipboard
get rid of ANTLR
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.
@yegor256 tagged this issue with "bug"
@yegor256 thanks a lot for reporting, 15 mins added to your acc, pmt ID 000-3d107665
@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).
@0crat in
@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)
@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)
@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)
@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)
@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)
@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)
@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)
@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)
@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)
Hello, I am interested in tweaking this to use ANTLR4. If like my proposal, I can start with this.
@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)
@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)
@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)
@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)
@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)
@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)
@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)
@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)
@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)
@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)
@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)
@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)
@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)
@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)
@rultor release, tag is 0.31.0
@maxonfjvipon many thanks!