> If we wrote a GUI library in parrot, a sort of Tkinter, and our > widgets compiled down to parrot then we would have a consistent GUI > library where widgets could be shared across languages and across > platforms. Unlike the present situation where Tk widgets from Perl > have to be rewritten for Ruby, verty painful.
it is still better to write everything in the library in one of the HLLs (that will compile to Parrot) and then compile to Parrot, than to write it in Parrot directly. choosing that "bootstrap" language... ah! will be amusing to watch the pie fight. this makes me think that we need to preserve names from the HLL when compiling to Parrot, so the next language knows how to use by name and not by some obscure, automatically-generated goto label. this has to be for libraries, classes, functions, variables, etc. we need to define a "standard" way of addressing these symbols and call arguments. scary, isn't it? > (I am not volunteering though, don't have the skills) me neither. flaviu
