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

Where is the updated sdk source? #83

Open
donlzx opened this issue Mar 12, 2017 · 5 comments
Open

Where is the updated sdk source? #83

donlzx opened this issue Mar 12, 2017 · 5 comments

Comments

@donlzx
Copy link

donlzx commented Mar 12, 2017

I can compile rock using the latest release (1.0.22) source code or using git master branch, but I can not compile any program with it: the system.use file is not found.

Also, the sdk folder seems to be not up-to-date. Many changes noted on the release log are not found in the sdk source folder. Am I missing something?

@marcusnaslund
Copy link

AFAIK, the sdk/ folder is (with minor modifications?) the same as the sdk folder in upstream https://github.com/ooc-lang/rock and used only to build rock itself.

Compiled programs are meant to use the (very much updated) sdk found in https://github.com/magic-lang/ooc-kean - there you find a system/ folder, among other things.

@marcusnaslund
Copy link

@thomasfanell can perhaps confirm and/or fill in if I missed something.

@thomasfanell
Copy link

This is correct.

@donlzx
Copy link
Author

donlzx commented Mar 13, 2017

@marcusnaslund @thomasfanell Thanks for the quick reply.

When I first discover ooc-lang.org, the language design seems very interesting and indeed of some practical use cases. Sadly its development seems to be stalled. Then, I found this fork and glad it is still being updated.

However, the documentation is very lacking and the changes/differences from upstream are confusing to a new comer. Hopefully a simple summary document or one-page website can be setup. In this way, we may get more people interested.

@marcusnaslund
Copy link

marcusnaslund commented Mar 13, 2017

You are absolutely right, and there have been plans for more extensive documentation, but I'm afraid less and less time from our part is being spent maintaining our ooc fork as well.

If you need any help getting started though, just ask. :) The main differences from "upstream ooc" are the lack of GC and the much more extensive standard library.

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

No branches or pull requests

3 participants