From
http://www.eros-os.org/pipermail/e-lang/2004-July/009917.html
? <awt>
# problem: Failed: Need awt Runner, not headless
? <import:java.awt.Color>
# value: <import:java.awt.Color>
I believe <import> allowing the loading AWT/Swing
classes from a
headless vat is a bug.
Consequence: while evaluating the second expression,
the Java process
starts up the AWT UI (visible for me as the creation of
a Mac OS X dock
icon and menu bar). Any E code code can do this, since
<import> is
safeScoped. This seems both undesirable UI-wise and a
potential
security problem.
Consequence: I can't run untrusted code without relying
on the safety
of the AWT/Swing taming. (I have a current project in
mind that would
involve running a lot of untrusted code.)
Consequence: I'm not sure whether this breaks near
reference
discipline; aren't AWT objects expected to be only NEAR
in vats in the
AWT Runner?
Followups 2004-Jul-28 04:34 markm
SWT has similar problems
