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

Change package and namespace to Java rather than IdrisJava. #5

Closed
jfdm opened this issue Sep 25, 2015 · 3 comments
Closed

Change package and namespace to Java rather than IdrisJava. #5

jfdm opened this issue Sep 25, 2015 · 3 comments

Comments

@jfdm
Copy link

jfdm commented Sep 25, 2015

Question: Would it not be better to call the package java? As we are already in Idris, the Idris in the IdrisJava namespace seems a little redundant.

If I have time I shall make the alterations myself and issue a PR, but thought it worth a mention in case anybody agrees and wishes to contribute a PR. Also I have no idea how this would affect upstream dev..

@bgaster
Copy link
Contributor

bgaster commented Sep 26, 2015

I would prefer not to change the package name to Java, for two reasons:

  1. I followed the naming convention of IdrisScript, the Javascript backend:
    https://github.com/idris-hackers/IdrisScript
  2. In a application I've written for automatically generating FFI interface for Java method prototypes, there is a library for Java syntax and parsing, packaged under the name Java.

@jfdm
Copy link
Author

jfdm commented Sep 26, 2015

Ah okay. Thought it was worth a mention. Personally, I liked the approach taken in the python backend (ziman/idris-py) where the namespace is Python a little bit cleaner.

@jfdm jfdm closed this as completed Sep 26, 2015
@Melvar
Copy link

Melvar commented Sep 28, 2015

There should definitely be a convention for the names of backend-FFI libraries. The question is how to come up with one.

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