-
Notifications
You must be signed in to change notification settings - Fork 122
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
File name too long #1077
Comments
@mximp can we do something about this? |
@dours Can you please provide example of Java name the parser is trying to produce? |
@mximp , yes:
|
@mximp Do you have an estimate on how long will it take to fix this one? Is it complicated? It currently blocks around 5 tests in the py2eo translator, I would like to know if I need to think about a workaround. |
@dours should be finished by tomorrow |
@dours fixed. please check & close |
@rultor release, tag is |
@dours @yegor256 Oops, I failed. You can see the full log here (spent 3min)
|
@rultor release, tag is |
@mximp I tried 0.28.2, but still get
the file is for_break_continue_nested.eo.txt |
(and the pom is) |
@dours can you confirm initial case from the description works fine on your machine? Could you please also try to save the file manually: |
@dours please check |
@mximp sorry for the delay. I've made a workaround for this bug, so it currently prevents me from executing only 1 test (for_break_continue_nested ) . I can create the file manually. The initial case also passes. BUT! If add
Checked everything with the release 0.28.2 |
When you add |
@mximp definitely, we need to fix such XSLs |
@dours reminder |
Translation of python code with several (say, 4) levels of structural control flow hierarchy (i.e, an
if
clause inside a doublefor
loop inside a function) leads to EO code with an hierarchy of about 40 objects in my case. Java files for this EO code have too long file names (for Ubuntu 20!), so the compilation process fails.The easiest way to reproduce this problem is to use this EO generator:
The text was updated successfully, but these errors were encountered: