> I don't think we should even think about putting Parrot into AOLserver as
> the primary multi-language support mechanism until it's actually stable
> and being used (beta-level at the minimum). I'm reminded of the colleague
> who suggested (in early 2001) that I use C# or Mozilla/XUL for my
> bi
On Wednesday, November 13, 2002, at 01:08 PM, Titus Brown wrote:
Now that would be nice... ;) Smalltalk and Objective C both seem to be
interesting languages that are much neglected these days.
The Squeak project (http://www.squeak.org/) seems fairly active, and ObjC
got new focus because it'
On 2002.11.13, Peter M. Jansson <[EMAIL PROTECTED]> wrote:
> On Wednesday, November 13, 2002, at 09:36 AM, Dossy wrote:
>
> >I'm glad the open source community's getting to reinvent the Sun/Java
> >wheel, but ...
>
> Which is a reinvention of the Smalltalk wheel.
I might agree with you if a whole
On Wednesday, November 13, 2002, at 09:36 AM, Dossy wrote:
I'm glad the open source community's getting to reinvent the Sun/Java
wheel, but ...
Which is a reinvention of the Smalltalk wheel.
On 2002.11.12, Talli Somekh <[EMAIL PROTECTED]> wrote:
> "Parrot is in the early phases of its implementation. The primary way
> to use Parrot is to write Parrot assembly code, described in PDD6.
I could easily see implementing a Tcl interpreter written in Parrot
assembly ... Tcl's language spec.
On Tue, 12 Nov 2002, Talli Somekh wrote:
> Anyway, I hope this helps. Perhaps a potentially new way for thinking
> about the problem?
This idea is currently being discussed on comp.lang.tcl (& cross-posted to
other comp.lang groups).
http://groups.google.com/groups?th=a0c66514e743b9c6
Micha
Hey everyone,
This suggestion is quite blue sky, but I thought that one potential
future solution for providing multiple language support would be by
implementing a "nsparrot". (warning, many quotations from various sites
ahead, with links)
Parrot is (from http://www.parrotcode.org):
"Parrot is
