external (Was: myWishList)
Rohan Hart <[email protected]> Mon, 20 Jun 2005 12:01:03 +1200
| Newsgroups | gmane.comp.lang.nice.general |
|---|---|
| Message-ID | <[email protected]> |
On Sat, 18 Jun 2005, Imam Tashdid ul Alam said:
> I will go for Rohan's choice of keywords, 'public' to mean visible
> to other packages (in the same jar?),
I don't believe it's possible to strict the scope of public in the
JVM.
> 'external' to mean visible to Java (and thus any other jars). to
> Rohan: what do you mean 'external public'? that's superfluous!
Because of mixed Nice/Java packages where Nice methods could be
package visible but still external.
Daniel's point about being nice to all possible languages using the
library is a good one but I'd still like to provide the full power of
Nice to other Nice packages. Thus for integration I'd probably be
writing method pairs like:
public int foo (int->int f) ...
public external int fooJ(Callable c)
= foo( int i => c.call(i) )
If some idiomatic mapping could be determined for the Java-hard parts
of the method protocol then these could potentially be generated by
the compiler. On the other hand that mapping might be JDK version
limited/linked.
cheers
Rohan
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click