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

Add eo-runtime dependency for all eo programs #1361

Closed
volodya-lombrozo opened this issue Oct 21, 2022 · 3 comments · Fixed by #1357
Closed

Add eo-runtime dependency for all eo programs #1361

volodya-lombrozo opened this issue Oct 21, 2022 · 3 comments · Fixed by #1357
Assignees

Comments

@volodya-lombrozo
Copy link
Member

volodya-lombrozo commented Oct 21, 2022

Issue comes from objectionary/eoc#35

I’ve tried to run the same code in sandbox and using eoc directly:

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

In both cases we have the same compilation exception.
The problem remains with all EO programs where we don’t use foreign objects. For example, the next code samples will compile fine:

[a b] > sum
  plus. > @
    a
    b
  QQ.io.stdout > neo
    "Wake up, Neo..."

Or

[a b] > sum
  memory 0 > x
  plus. > @
    a
    b

As I mentioned above, in the first code sample we don’t use foreign objects, by that reason our eo-foreign.json will contain only one entry:

[
    {
        "id": "sum",
        "discovered": "0",
        "xmir": "/Users/lombrozo/Workspace/EOlang/Projects/sum/.eoc/01-parse/sum.xmir",
        "scope": "compile",
        "eo": "/Users/lombrozo/Workspace/EOlang/Projects/sum/sum.eo",
        "xmir2": "/Users/lombrozo/Workspace/EOlang/Projects/sum/.eoc/03-optimize/sum.xmir",
        "version": "0.0.0"
    }
]

Therefore the next phases Discover, Pull, Resolve, Place will do nothing. The key point there is that classpath after all phases will be empty. eo-runtime classes will absent and we will see compilation error (since all transpiled classes depend on runtime library).

@0pdd
Copy link

0pdd commented Nov 1, 2022

@volodya-lombrozo 2 puzzles #1385, #1386 are still not solved.

@0pdd
Copy link

0pdd commented Nov 8, 2022

@volodya-lombrozo the puzzle #1385 is still not solved; solved: #1386.

@0pdd
Copy link

0pdd commented Dec 9, 2022

@volodya-lombrozo all 2 puzzles are solved here: #1385, #1386.

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

Successfully merging a pull request may close this issue.

2 participants