Re: GCC for PARROT (GCC Compiling itself to PARROT, then compilin g all supported languages to PARROT from PARROT)?!?!

2004-03-23 Thread Gabriel Dos Reis
Matt Fowles [EMAIL PROTECTED] writes: | All~ | | If I recall correctly, GCC supports Haskell, which is an ideal | language for Parrot. That might probably be the case, but we don't have it in the FSF release and I don't recall we have any mention of Haskell in the section of various front-ends

RE: GCC for PARROT (GCC Compiling itself to PARROT, then compilin g all supported languages to PARROT from PARROT)?!?!

2004-03-22 Thread Butler, Gerald
OK, I think I'm starting to get a better picture of what needs to happen. Does this sound more reasonable? Java, C#, Fortran(???), (Managed???)C++, (Other languages with appropriate non-direct memory access) == GCC Parser == Parse Tree == Enhanced RTL (where

Re: GCC for PARROT (GCC Compiling itself to PARROT, then compilin g all supported languages to PARROT from PARROT)?!?!

2004-03-22 Thread Simon Wistow
On Mon, Mar 22, 2004 at 09:54:56AM -0500, Butler, Gerald said: The important point is that the starting language must have semantics which treat variables, object, etc. as abstract entities to be manipulated not *memory locations* to be accessed arbitrarily. Then, the parse stage must spit out

RE: GCC for PARROT (GCC Compiling itself to PARROT, then compilin g all supported languages to PARROT from PARROT)?!?!

2004-03-22 Thread Dan Sugalski
At 9:54 AM -0500 3/22/04, Butler, Gerald wrote: OK, I think I'm starting to get a better picture of what needs to happen. Does this sound more reasonable? With the caveat that I know nothing about gcc's internals, it seems at least reasonable. :) -- Dan

RE: GCC for PARROT (GCC Compiling itself to PARROT, then compilin g all supported languages to PARROT from PARROT)?!?!

2004-03-22 Thread Simon Glover
On Mon, 22 Mar 2004, Butler, Gerald wrote: The important point is that the starting language must have semantics which treat variables, object, etc. as abstract entities to be manipulated not *memory locations* to be accessed arbitrarily. Then, the parse stage must spit This requirement

Re: GCC for PARROT (GCC Compiling itself to PARROT, then compilin g all supported languages to PARROT from PARROT)?!?!

2004-03-22 Thread Matt Fowles
All~ If I recall correctly, GCC supports Haskell, which is an ideal language for Parrot. Matt Simon Glover wrote: On Mon, 22 Mar 2004, Butler, Gerald wrote: The important point is that the starting language must have semantics which treat variables, object, etc. as abstract entities to be

Re: GCC for PARROT (GCC Compiling itself to PARROT, then compilin g all supported languages to PARROT from PARROT)?!?!

2004-03-22 Thread Gerald E Butler
Could you please give a little more insight on Haskell and why it is/would be so good? I've never heard of it. On Mon, 2004-03-22 at 14:23, Matt Fowles wrote: All~ If I recall correctly, GCC supports Haskell, which is an ideal language for Parrot. Matt Simon Glover wrote: On Mon,

Re: GCC for PARROT (GCC Compiling itself to PARROT, then compilin g all supported languages to PARROT from PARROT)?!?!

2004-03-22 Thread ozone
On 23/03/2004, at 6:23 AM, Matt Fowles wrote: If I recall correctly, GCC supports Haskell, which is an ideal language for Parrot. GCC doesn't support Haskell -- perhaps the compiler you're thinking of is GHC? (Glasgow Haskell Compiler). I'm starting to look at implementing a Haskell to Parrot

Re: GCC for PARROT (GCC Compiling itself to PARROT, then compilin g all supported languages to PARROT from PARROT)?!?!

2004-03-22 Thread Matt Fowles
I could be getting things mixed up here, but I thought I read that GHC (Glasgow Haskell Compiler) is part of GCC (GNU Compiler Collection). Although I might be misreading this paper slightly http://home.in.tum.de/~baueran/thesis/ I would greatly support adding a Haskell compiler and would be

Re: GCC for PARROT (GCC Compiling itself to PARROT, then compilin g all supported languages to PARROT from PARROT)?!?!

2004-03-22 Thread ozone
On 23/03/2004, at 12:24 PM, Matt Fowles wrote: I could be getting things mixed up here, but I thought I read that GHC (Glasgow Haskell Compiler) is part of GCC (GNU Compiler Collection). Although I might be misreading this paper slightly http://home.in.tum.de/~baueran/thesis/ GHC can