On Sat, Dec 25, 2021 at 4:31 PM Maneesh Sud via perl6-users
wrote:
>
> Merry Christmas and a Happy New Year.
Hi. Happy holidays to you too.
> Does perl6 or moarvm run on risc-v 32-bit processors.
I think a key piece is dyncall/libffi support. Googling suggests
dyncall doesn't support risc-v but
Merry Christmas and a Happy New Year.
Does perl6 or moarvm run on risc-v 32-bit processors. how much RAM do I need.
Do I need RTOS and Java or is there another way to boot strap.
uClinux is now part of the main kernel any ports to risc5 microcontrollers.
Reference designs including PCB for a micro
On Sun, Jan 31, 2016 at 5:20 PM, Will Coleda wrote:
> Nope. Most people just show up on #perl6 and chat, or make a pull
> request or open an RT.
Gotcha, thanks.
-Tom
Nope. Most people just show up on #perl6 and chat, or make a pull
request or open an RT.
On Sun, Jan 31, 2016 at 6:10 PM, Tom Browder wrote:
> On Sun, Jan 31, 2016 at 5:01 PM, Will Coleda wrote:
>> The language is intended to evolve; the specification will change as we go.
>>
>> If you have a pr
On Sun, Jan 31, 2016 at 5:01 PM, Will Coleda wrote:
> The language is intended to evolve; the specification will change as we go.
>
> If you have a proposal, go ahead and make it, see what traction it
> gets on the list.
Is there any specific format for a proposal? If not, is there a
successful
The language is intended to evolve; the specification will change as we go.
If you have a proposal, go ahead and make it, see what traction it
gets on the list.
On Sun, Jan 31, 2016 at 8:27 AM, Tom Browder wrote:
> I would like to propose some new Str and IO::Path methods if such
> would be cons
I would like to propose some new Str and IO::Path methods if such
would be considered.
Best regards,
-Tom
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #37021]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37021 >
Recently a couple of new language implementations have arrived in
Cory Spencer <[EMAIL PROTECTED]> wrote:
>-> (* 2 3.2)
>9.6
>-> (+ 1.2 3)
> I'm not sure what kind of magic you worked last time with Integers,
> Leo, but would you mind working it again? (Or pointing me in the right
> direction so that I can fix it myself. :)
Short answer: will be f
On Fri, 22 Apr 2005, Matt Diephouse wrote:
-> (defun (square x) (* x x))
T
-> (square 2)
*** ERROR: SQUARE is not a function name
A quick follow-up - I've just checked in code implementing some primitive
macros, so if you wanted to give (defun ...) a go again, you should find
that it works now. (
From: Cory Spencer <[EMAIL PROTECTED]>
Date: Fri, 22 Apr 2005 10:45:17 -0600 (MDT)
> -> (defun (square x) (* x x))
> [...]
> *** ERROR: SQUARE is not a function name
>
> Is that because (a) that's not implemented yet or (b) I'm doing
> something wrong? I haven't found the t
-> (defun (square x) (* x x))
[...]
*** ERROR: SQUARE is not a function name
Is that because (a) that's not implemented yet or (b) I'm doing
something wrong? I haven't found the time to delve into the source
yet.
Oops, that wasn't supposed to have made it in there - I haven't finished
up macros y
Cory Spencer <[EMAIL PROTECTED]> wrote:
> http://www.sprocket.org/pcl/pcl-0.1.0.tar.gz
Below is a patch against 0.1.0
- handle a command line file argument:
$ cat t.lisp
(print (+ 2 3))
$ ../parrot lisp.imc t.lisp
5
- use a FixedPMCArray for cons
- much faster _LIST_LENGTH (not that I
On Fri, Apr 22, 2005 at 07:59:57AM +0200, Uwe Voelker wrote:
> >I'd like to announce the creation of the Parrot Common Lisp project,
>
> Let's port emacs to it :-)
Erik Naggum, is that you?
--
Lars Balker RasmussenConsult::Perl
I'd like to announce the creation of the Parrot Common Lisp project,
Let's port emacs to it :-)
Bye,
Uwe
Matt Diephouse <[EMAIL PROTECTED]> wrote:
> -> (* 2 3)
> 9
See my reply to Cory's mail.
leo
Cory Spencer <[EMAIL PROTECTED]> wrote:
> For examples of what it can currently do, look in the lisp/ subdirectory
> in the files loaded at run time (bootstrap.l system.l and primitives.l).
>
> Anyone who would like to have a peek at what I've got so far is invited to
> download the 0.1.0 release
Cory Spencer <[EMAIL PROTECTED]> wrote:
>* There are some outstanding issues with the Dead Object
> Detection/Garbage collection systems that I've yet to track down.
I've fixed a bug that happened in combination with Hash iterators.
Exactly the symptoms that I saw, when running:
(prin
(If anyone is able to track down aforementioned DOD/GC problems,
you'll earn my eternal gratitude.)
Can you please provide a code snippet that exhibits the error.
Just running the program gives me errors on both Linux/x86 and OS X.
Running with GC disabled works fine.
On OS X with GC e
According to Cory Spencer:
> I'd like to announce the creation of the Parrot Common Lisp project
Excellent!
> * It's not a compiler yet, although I've got plans for that down the
> road.
(declare (type PerlString s)) ? :-)
--
Chip Salzenberg- a.k.a. -<[EMAIL PROTE
Cory Spencer <[EMAIL PROTECTED]> wrote:
> I'd like to announce the creation of the Parrot Common Lisp project, which
> aims to implement a significant subset of the Common Lisp language.
Wow. I can even do something with it:
$ ../parrot lisp.imc
-> (+ 2 5)
7
-> (list 1 2 3)
(1 . (2 . (3 . NIL)))
I'd like to announce the creation of the Parrot Common Lisp project, which
aims to implement a significant subset of the Common Lisp language. At
present it's nowhere near achieving that goal, but it's progressing slowly
as I figure out the intricacies of writing a Lisp implementation.
A brief
At 8:41 PM +0200 8/19/04, Leopold Toetsch wrote:
Dan Sugalski wrote:
If span can generate PIR that'll run on a base parrot interpreter, ...
Currently custom opcodes and an all-in-one PMC, the object - IIRC. But ...
... I'd love to get some to check in as part of the test suite.
... that would be re
Dan Sugalski wrote:
If span can generate PIR that'll run on a base parrot interpreter, ...
Currently custom opcodes and an all-in-one PMC, the object - IIRC. But ...
... I'd
love to get some to check in as part of the test suite.
... that would be really great.
I'm currently testing the increment
At 1:16 AM -0400 8/1/04, Matt Kennedy wrote:
Hey, all. I'd like to announce the initial release of a new language
which uses Parrot as its VM. Span is a dynamic, object oriented
programming language.
As I dig through old mail...
This is really cool. I know some folks have noted some problems
Matt Kennedy <[EMAIL PROTECTED]> wrote:
> Hey, all. I'd like to announce the initial release of a new language
> which uses Parrot as its VM. Span is a dynamic, object oriented
> programming language.
... and the most evolved language running on top of Parrot it seems,
wo
This is definitely cool. I'm impressed :)
Your PBC output code seems a little buggy, tho ;)
error:imcc:main: Couldn't open /tmpo.pbc/Hpbco.spa
But keep up the good work. A compiler writer myself,
I'd like to know more about how others go about
implementing these things. I'm eagerly awaiting th
Hey, all. I'd like to announce the initial release of a new language
which uses Parrot as its VM. Span is a dynamic, object oriented
programming language. Span can be most concisely described as
Smalltalk for C++, C#, and Java programmers. It features an object
system modeled on the Smal
Bernhard Schmalhofer (via RT) wrote:
besides skiing in the Austrian alps, I have worked some on my port of GNU m4
during the holidays.
Lot of snow now :)
config/gen/makefiles/m4.in:
I missed that one in the first place, added now.
So (hopefully) all is in (I dropped empty dirs and vims swap f
In perl.perl6.internals, you wrote:
> Leopold Toetsch wrote:
>> $ ../imcc/imcc -r ook.pasm hello.ook
>> Hello World!
> You don't seem to have checked in the compile thing...
No, its not ready yet.
> About the eval: you said that compile does eval here. In the future, how
> should I eval after co
Leopold Toetsch wrote:
> Jerome Quelin (via RT) wrote:
> > - currently I'm just printing on stdout the resulting parrot code,
> > I lack an eval instruction in Parrot. Dan, Leo? :-)
> $ diff -ub ~/src/parrot/languages/ook/ook.pasm ook.pasm
> --- /home/lt/src/parrot/languages/ook/ook.pasm Wed Jan
Jerome Quelin (via RT) wrote:
- currently I'm just printing on stdout the resulting parrot code, I
lack an eval instruction in Parrot. Dan, Leo? :-)
$ diff -ub ~/src/parrot/languages/ook/ook.pasm ook.pasm
--- /home/lt/src/parrot/languages/ook/ook.pasm Wed Jan 1 01:34:16 2003
+++ ook.pasm
t;
>
> Thanks to our dear summarizer, I'm now known (from a googlism point of
> view) as 'one of the "let's implement a bunch of languages on parrot"
> crew'. So, in order to prove him right definitely (and also because
> orang-utans should also bene
On Tue, Dec 31, 2002 at 06:18:36PM +0100, Jerome Quelin wrote:
> Nice to see how dummy languages make the whole stuff advance... :o)
Then there's the zcode interpreter...
(dynamic opcode library loading, foreign bytecode translation)
Nicholas Clark
At 12:49 PM -0500 12/31/02, Dan Sugalski wrote:
At 6:18 PM +0100 12/31/02, Jerome Quelin wrote:
Leopold Toetsch wrote:
> - currently I'm just printing on stdout the resulting parrot code,
> I lack an eval instruction in Parrot. Dan, Leo? :-)
Here is the solution of our perl6 bootstrapping pr
> orang-utans should also benefit from Parrot's speed), here's a new
> language supported by Parrot: the Ook! language.
Shouldn't this be reworked as a patch to Acme::Ook?
--
It's all fun and games until someone loses an eye.
Then it's a sport!
At 6:18 PM +0100 12/31/02, Jerome Quelin wrote:
Leopold Toetsch wrote:
> - currently I'm just printing on stdout the resulting parrot code,
> I lack an eval instruction in Parrot. Dan, Leo? :-)
Here is the solution of our perl6 bootstrapping problem, I'll make an
I ops ...
Nice to see how
Leopold Toetsch wrote:
> > - currently I'm just printing on stdout the resulting parrot code,
> > I lack an eval instruction in Parrot. Dan, Leo? :-)
> Here is the solution of our perl6 bootstrapping problem, I'll make an
> I ops ...
Nice to see how dummy languages make the whole stuff advance...
On Monday 30 December 2002 21:30, Leopold Toetsch wrote:
> Jerome Quelin (via RT) wrote:
> > # New Ticket Created by Jerome Quelin
> > # Please include the string: [perl #19610]
> > # in the subject line of all future correspondence about this issue.
> > # http://rt.perl.org/rt2/Ticket/Display.ht
Jerome Quelin (via RT) wrote:
# New Ticket Created by Jerome Quelin
# Please include the string: [perl #19610]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19610 >
- currently I'm just printing on stdout the resulting
On Mon, Dec 30, 2002 at 11:45:19PM +, Nicholas Clark wrote:
> Indeed. However, when I tried compiling my Ook! test program:
> I got this:
>
> Label KOO1_2 already exists at ../../assemble.pl line 557.
>
> (admittedly from a pre-built parrot that is about 2 weeks old)
Also on a clean checko
On Mon, Dec 30, 2002 at 11:09:07PM +, Jerome Quelin wrote:
> Ok, about this implementation:
> - this is a compiler (and not an interpreter) that spits Parrot
> assembly code (yes, I'm targeting Parrot).
> - it implements every Ook! instruction but the "Ook. Ook!" one. I'll
> work on it late
as 'one of the "let's implement a bunch of languages on parrot"
crew'. So, in order to prove him right definitely (and also because
orang-utans should also benefit from Parrot's speed), here's a new
language supported by Parrot: the Ook! language.
For the unl
Jerome Quelin wrote:
>
> Hi,
>
> I'm proud to provide you with a Befunge-93 interpreter written in Parrot! I'd
> like to thanks you all of the parrot team, for giving us such a marvelous toy
> to play with.
Applied... AIEE...
--
Jeff <[EMAIL PROTECTED]>
Hi,
I'm proud to provide you with a Befunge-93 interpreter written in Parrot! I'd
like to thanks you all of the parrot team, for giving us such a marvelous toy
to play with.
Note to Leon Brocard:
There's a lot more to do in order to provide a Befunge-98 compliant
interpreter, so don't worry!
Jeff wrote:
>
> For your edification/amusement/nightmares...
>
> A FORTH interpreter.
>
> Doesn't do much, but it -will- compile words. It accepts the following
> input:
>
> > 3 : square ( n -- n ) dup * ; : cube ( n -- n )
> square> dup square * ;
> cube> .
> 27>
>
> I'll be adding new words
For your edification/amusement/nightmares...
A FORTH interpreter.
Doesn't do much, but it -will- compile words. It accepts the following
input:
> 3 : square ( n -- n ) dup * ; : cube ( n -- n )
square> dup square * ;
cube> .
27>
I'll be adding new words as the fancy strikes me. As you can see
On Fri, 19 Oct 2001, Jeff wrote:
> For a -very- primitive Scheme -> Parrot compiler, see
>
> http://216.254.0.2/~jgoff/Files/scheme.tar.gz
Woo hoo!
> Test files (using the provided version of Test::More) are in the t/
> directory, and can be run by typing 'make test' at the command line. The
>
For a -very- primitive Scheme -> Parrot compiler, see
http://216.254.0.2/~jgoff/Files/scheme.tar.gz
This is purely proof-of-concept for a much more sophisticated
implementation. The current tarball has support for only integer math
operators and predicates, although there is minimal support for
At 03:55 PM 8/15/00 -0700, you wrote:
>LIST: perl6-language-errors
>CHAIR: Steve Simmons <[EMAIL PROTECTED]>
>MISSION:To develop RFCs related to error handling and exceptions
> in Perl 6, possibly combining existing RFCs into a more
> cohe
50 matches
Mail list logo
