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

How to use other libraries? #22

Closed
snayaksnayak opened this issue Feb 25, 2016 · 3 comments
Closed

How to use other libraries? #22

snayaksnayak opened this issue Feb 25, 2016 · 3 comments

Comments

@snayaksnayak
Copy link

Voc has many libraries inbuilt, V4, S3, Ulm's, ooc etc.
How to use a specific library? Any compile time option?
Or everything available at the same time? No name space clash?

@norayr
Copy link
Member

norayr commented Feb 25, 2016

On my system, voc is prefixed in /opt, therefore list of available by default (in libVishapOberon) library interfaces can be get by

ls /opt/voc/lib/voc/sym/

Then, interface of the specific module can be get by running

 /opt/voc/bin/showdef /opt/voc/lib/voc/sym/Strings.sym

This is default Strings module ported from Oberon V4 system.

There are different implementations of that module.

/opt/voc/bin/showdef /opt/voc/lib/voc/sym/oocStrings.sym

comes from ooc compiler version 1.

 /opt/voc/bin/showdef /opt/voc/lib/voc/sym/ooc2Strings.sym

comes from ooc compiler version 2.

 /opt/voc/bin/showdef /opt/voc/lib/voc/sym/powStrings.sym

comes from POW compiler.

 /opt/voc/bin/showdef /opt/voc/lib/voc/sym/ethStrings.sym

comes from Oberon System 3(ETH version)

 /opt/voc/bin/showdef /opt/voc/lib/voc/sym/ulmStrings.sym

comes from Ulm Oberon System.

You can just import necessary module with IMPORT ethStrings or IMPORT oocStrings, or you can IMPORT Strings := oocStrings and then just use Strings alias in your code.

@snayaksnayak
Copy link
Author

Good. Now we have too many things to chose from. :-)

@norayr
Copy link
Member

norayr commented Feb 26, 2016

btw when module gets compiled, symbol and object files are created with the name which is in the source code after MODULE keyword, not the file name.

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

2 participants