Interfaces and "package"

[Eric Herz]

Hi all-

I've just recently started using Mirah for a project and it's great. I've noticed that while the documentation on the site notes that package path is derived from the file system path, I've noticed in the current version I'm using (v0.1.4), it not only allows me to declare package but it seems to require it. I've declared the package on most of my files, but I've run into a snag with interfaces. I have an interface defined in its own file, like so:

package my.package.path

interface Foo do

  def bar(x: int): void; end

end

The interface seems to compile file, and even imports fine in another file:

import my.package.path.Foo

However, I get a runtime error:

java/lang/ClassLoader.java:-2:in `defineClass1': java.lang.NoClassDefFoundError:my.package.path.Foo

I suspect that perhaps the package keyword implementation is a newer feature and something has been overlooked with interfaces??

[Nick Howard]

That's certainly possible. Could you file a bug on github? It should be pretty easy to reproduce if that's right.

--
You received this message because you are subscribed to the Google Groups "The Mirah Programming Language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mirah+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

-Nick Howard
http://blog.baroquebobcat.com/

[Eric Herz]

Couldn't reproduce it in a test case at first until I realized it might be the file inclusion order. I was right. Issue here:

https://github.com/mirah/mirah/issues/314