Command-line toolkit for parsing, compiling, transpiling, optimizing, linking, dataizing, and running EOLANG programs

Why I can't compile program like this:

eoc link

Code

[a b] > sum
  plus. > @
    a
    b

It fails. I don't want to dataize program. I need only XMIR file. Here is log.txt

When I try to run eoc test in terminal, it fails. Maybe I do smth wrong, but there is a log.txt with output. Nevertheless, some programs I can run like hello.eo etc. What should I do?

Error at "EOorg.EOeolang.EObool#plus" attribute
Can't get(), attribute "plus" is absent among other 11 attrs (ρ, not, σ, or, Δ, and, as-bytes, eq, while, if, as-hash) and φ is absent

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | eslint (source) | 8.24.0 -> 8.26.0 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

How can I get GMI for an example from README? I tried:

eoc clean
eoc gmi

eoc clean
eoc dataize hello
eoc gmi

eoc clean
eoc assemble
eoc gmi

But everytime GMI's is not generated and in logs I have this line: [INFO] No .xmir converted to GMIs

I've added some information about compilation process, now it looks like:

EO version is 0.28.11
[eo:register] 1808 ms. Total number of compiled files 0
EO objects registered in /Users/lombrozo/Workspace/EOlang/Projects/sum/.eoc/eo-foreign.json
EO version is 0.28.11
[eo:assemble] 33516 ms. Total number of compiled files 446
EO program assembled in /Users/lombrozo/Workspace/EOlang/Projects/sum/.eoc
EO version is 0.28.11
[eo:transpile] 11081 ms. Total number of compiled files 928
Java sources generated in /Users/lombrozo/Workspace/EOlang/Projects/sum/.eoc/generated-sources

It's important to notice that since spawn function is asynchronous and by that reason I have to wrap it and all calls using async-style chains (and Promise), it looks like:

register(program.opts())
.then((r) => assemble(program.opts()))
.then((r) => transpile(program.opts()))
.then((r) => compile(program.opts()))
.then((r) => link(program.opts()))
.then((r) => test(program.opts()));

Closes: #93

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | mocha (source) | 10.0.0 -> 10.1.0 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

I have the next programm:

+alias org.eolang.txt.sprintf

[] > app
  QQ.io.stdout > @
    sprintf
      "Hello, %s"
      "Jeffrey"

When I run eoc dataize app everything works fine and in the console I can see the next output:

Hello, Jeffrey%

(however, it isn't clear, why the program prints % at the end)

Then, I cange the program to the next:

+alias org.eolang.txt.sprintf

[] > app
  QQ.io.stdout > @
    sprintf
      "Hello, %s, %d"
      "Jeffrey"
      1

and run the same command eoc dataize app. Now, in the console I see the next exception:

[ERROR] COMPILATION ERROR :
[ERROR] /Workspace/EOlang/.eoc/generated-sources/EOapp.java:[47,43] cannot find symbol
  symbol:   class EOstring
  location: package EOorg.EOeolang
[ERROR] /Workspace/EOlang/.eoc/generated-sources/EOapp.java:[50,43] cannot find symbol
  symbol:   class EOstring
  location: package EOorg.EOeolang
[ERROR] /Workspace/EOlang/.eoc/generated-sources/EOapp.java:[53,43] cannot find symbol
  symbol:   class EOint
  location: package EOorg.EOeolang
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-cli) on project eoc: Compilation failure: Compilation failure:
[ERROR] /Workspace/EOlang/.eoc/generated-sources/EOapp.java:[47,43] cannot find symbol
[ERROR]   symbol:   class EOstring
[ERROR]   location: package EOorg.EOeolang
[ERROR] /Workspace/EOlang/.eoc/generated-sources/EOapp.java:[50,43] cannot find symbol
[ERROR]   symbol:   class EOstring
[ERROR]   location: package EOorg.EOeolang
[ERROR] /Workspace/EOlang/.eoc/generated-sources/EOapp.java:[53,43] cannot find symbol
[ERROR]   symbol:   class EOint
[ERROR]   location: package EOorg.EOeolang
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-cli) on project eoc: Compilation failure
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.apache.maven.wrapper.BootstrapMainStarter.start (BootstrapMainStarter.java:53)
    at org.apache.maven.wrapper.WrapperExecutor.execute (WrapperExecutor.java:152)
    at org.apache.maven.wrapper.MavenWrapperMain.main (MavenWrapperMain.java:76)
Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1220)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:187)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.apache.maven.wrapper.BootstrapMainStarter.start (BootstrapMainStarter.java:53)
    at org.apache.maven.wrapper.WrapperExecutor.execute (WrapperExecutor.java:152)
    at org.apache.maven.wrapper.MavenWrapperMain.main (MavenWrapperMain.java:76)
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
The command "/Users/lombrozo/.nvm/versions/node/v16.17.1/lib/node_modules/eolang/mvnw/mvnw compiler:compile --quiet -Dmaven.compiler.source=1.8 -Dmaven.compiler.target=1.8 -Deo.targetDir=/Workspace/EOlang/.eoc -Deo.generatedDir=/Workspace/EOlang/.eoc/generated-sources -Deo.version=0.28.10 --errors --batch-mode --update-snapshots --fail-fast" exited with #1 code

When I clean .eoc folder by rm -rf .eoc and run eoc dataize app again, in the console I can see:

Hello, Jeffrey, 1% 

I am not sure how it should work, but in eoc documentation I haven't found anything about cleaning. Should eoc clean .eoc folder themself? Correct me please, if I understand the process wrongly and it's a normal behaviour.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | fast-xml-parser | 4.0.10 -> 4.0.11 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | commander | 9.4.0 -> 9.4.1 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | eslint (source) | 8.23.1 -> 8.24.0 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | org.apache.maven.plugins:maven-compiler-plugin | 3.8.1 -> 3.10.1 | | | | |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | mocha (source) | 10.1.0 -> 10.2.0 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

eslint doesn't catch indents. In some places we can put 4, somewhere 2 and it's allowed which is wrong of course. It's important to adjust eslint to catch such mistakes. The issue comes from that PR comment.

When I run the next command it only cleans the directory:

eoc clean dataize app

Dataization doesn't happen. And I have to call eoc dataize app again. It would be useful to be able to state several eoc commands like clean and dataize in one line, as for me.

I was struggling with the task of adding timestamps for build logs, because applied changes for log4j logger didn’t applied on a build process. In other words, if you use eoc with the new version of eo-maven-plugin (where we already added timestamps for log4j logs), you still will see the next output:

[INFO] There are 33 EO sources registered already
[INFO] Registered 1 EO sources from ./Users/lombrozo/Workspace/EOlang/Projects/learning to ./Users/lombrozo/Workspace/EOlang/Projects/learning/.eoc/eo-foreign.json, included [**.eo], excluded [.eoc/**]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.536 s
[INFO] Finished at: 2022-11-10T21:46:32+03:00
[INFO] ------------------------------------------------------------------------

Why? Because we use logs frameworks like this (I can be wrong in details):



As you can see, we expect to use log4j implementation for slf4j, but here is a trick: Since 3.1.x version of maven, the default maven distributive uses its own slf4j implementation - slf4j-simple, in other words, our picture changes to the next:



You can check maven that installed on your laptop and in the maven lib directory you probably will find the next jars:

maven-slf4j-provider-3.8.3.jar (==“slf4j-simple”)
slf4j-api-1.7.32.jar

Since slf4j chooses only one logging implementation, we have only 2 options here to add timestamps for build logs:

1. Use native slf4j-simple logger directly. To do so we can just add the next arguments for all maven commands

-Dorg.slf4j.simpleLogger.showDateTime=true
-Dorg.slf4j.simpleLogger.dateTimeFormat=yyyy-dd-MM HH:mm:ss

Then all maven build logs will look like:

2022-10-11 21:49:00 [INFO] Assemble cycle #1 (eo:33/xmir:33/xmir2:33/discovered:33 -> eo:33/xmir:33/xmir2:33/discovered:33), took 3s
2022-10-11 21:49:00 [INFO] 1 assemble cycle(s) produced some new object(s): eo:33/xmir:33/xmir2:33/discovered:33
2022-10-11 21:49:00 [INFO] ------------------------------------------------------------------------
2022-10-11 21:49:00 [INFO] BUILD SUCCESS
2022-10-11 21:49:00 [INFO] ------------------------------------------------------------------------
2022-10-11 21:49:00 [INFO] Total time:  3.203 s
2022-10-11 21:49:00 [INFO] Finished at: 2022-11-10T21:49:00+03:00
2022-10-11 21:49:00 [INFO] ------------------------------------------------------------------------

2. Remove slf3j-simple from mvnw distributive (I don’t know if it’s even possible). But at least, you can try to remove slf4j-simple from your maven/lib folder and log4j will work fine.

Useful links:

1. More detailed about maven logging you can read here.
2. Maven slf4j provider library in GitHub.
3. The list of properties that we can use in order to adjust maven slf4j-simple logger.