On 03/05/2014 04:13 PM, Ingo W. wrote:
This is a technical problem, but when you run into it, something is
probably wrongly designed.
Maybe. There are probably few cases where you need tightly-coupled
classes written in two languages. Especially with Kawa-Scheme and Java:
There is little to no performance *or* expressiveness advantage to
writing something in Java rather than Kawa-Scheme. It may be different
for languages that make it harder to write close-to-the-JVM code.
Which I guess is why it hasn't been a big priority.
Still, it would be easier if you didn't have to carefully partition
and order your sources files to avoid inter-language cycles. Using
a single command to compile multiple languages is more convenient.
--
--Per Bothner
[email protected] http://per.bothner.com/
--
You received this message because you are subscribed to the Google Groups "JVM
Languages" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jvm-languages.
For more options, visit https://groups.google.com/groups/opt_out.
