[ImageJ-bugs] [Bug 776] jruby integration is broken
bugzilla at fiji.sc
bugzilla at fiji.sc
Thu Aug 28 05:08:20 CDT 2014
http://fiji.sc/bugzilla/show_bug.cgi?id=776
--- Comment #15 from brotkastennation at dukun.de ---
Sorry, I don't really understand the reason behind this:
»The rationale is that the auto-import feature is not safe. What if two classes
of the same name live in two different packages? Or if a new class is
introduced that makes formerly unique names ambiguous? All of a sudden, all of
the scripts that reference the original class no longer work. In short:
auto-imports are dangerously imprecise.«
By using the old ij.thispackage.thisclass syntax, where is an ambiguity with
these auto-imports? (so why not put this into imagej.rb?: def ij; Java:ij; end)
Besides this, I think it's not a good idea to default to include the current
imagej.rb as it is polluting global namespace heavily (e.g. overwriting open).
So I suggest putting all the macro-convenience-functions into a separate module
or putting them into another file.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-bugs/attachments/20140828/abb626cc/attachment.html>
More information about the Imagej-bugs
mailing list