Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
perl.perl6.internals
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Q: about Parrot assembly code
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Steve Coleman  
View profile  
 More options Feb 25 2005, 4:41 pm
Newsgroups: perl.perl6.internals
From: Steve.Cole...@jhuapl.edu (Steve Coleman)
Date: Fri, 25 Feb 2005 16:41:30 -0500
Local: Fri, Feb 25 2005 4:41 pm
Subject: Re: Q: about Parrot assembly code
Reply to author | Forward | Print | View thread | Show original | Report this message | Find messages by this author

MrJoltCola wrote:
> I doubt there is much that could not be mapped to Parrot, but Parrot
> does things that would be impossible to map directly back to a CPU.

Currently I am only thinking of just a CPU X to Parrot asm translation,
not the reverse, and this is just an attempt to get to a consolidated
Virtual CPU (VPU?) model, and a single language syntax or state machine
to deal with. All tools from that point on would work on a common model
of the same virtual cpu. I could pick any virtual CPU and that would be
Ok because it would not have to be run anywhere to be able to analyse
structure and purpose, but Parrot would then have the potential benifit
of having additional tools developed for understanding program
structure. After all, why build something nobody else could use? Well it
seemed like a good idea at the time, but as I feared the Parrot virtual
CPU is highly slanted towards a very different goal.

>  I'm not sure why you'd want to do this, though. We don't
> have any application base to speak of. :)

I'm not looking for any Parrot apps to run, but the extension of that
same capability could eventually lead to extra debugging and bitecode
runtime support, but thats not my primary aim. The more near-term
benifit might have been a set of "anything to Parrot" translators, which
in theory could then be used to convert all your favorite binary
applications to your favorite new runtime VM. Then you could have lots
of  applications! (lol) This part of course was meant as a joke, but
then Parrot itself started as a joke did it not?

In any case I will be interested to see your project move forward and
become a reality. Perl has been a wonderful language, for so many
purposes, and I believe with this project in the works there will be a
lot more of that to come in the future as well.

--
Steve Coleman
Johns Hopkins University / Applied Physics Laboratory


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google