Jako is in a mostly working state. I just checked in a couple of minor
cleanups:
* Disable languages/jako/examples/sub.jako, since Parrot / IMCC
don't support .global int x
* Change languages/jako/examples/pmc.jako to preallocate a nice
PerlString PMC before attempting to set to a
Simon Glover [EMAIL PROTECTED] wrote:
If -O2 is used however, it prints '-1', and the hangs. Disassembly of
the optimized bytecode shows that it is being optimized to:
-O2 shouldn't do anything for PASM code and it seems that it got more
broken recently as it was. I'll disable it for now.
Kenneth A Graves [EMAIL PROTECTED] wrote:
On Fri, 2004-02-27 at 16:08, Kenneth A Graves wrote:
How do I verify which runloops/features are working?
CGoto core: make testg testC
JIT:make testj
I added or $^O eq 'freebsd' to t/pmc/{threads,timer}.t and those
tests run successfully.
S. Livingston [EMAIL PROTECTED] wrote:
I compiled on Tru64
uname -m -p -r -s -v
OSF1 V4.0 878 alpha
I compiled with the digital compiler, not gcc,
DEC C V5.6-075 on Digital UNIX V4.0 (Rev. 878)
I ran into the inet_pton problem described earlier.
I've committeed this
Andrew Dougherty [EMAIL PROTECTED] wrote:
On Fri, 27 Feb 2004, Leopold Toetsch wrote:
[ inet_aton vs inet_pton ]
We need a config test here.
Something like this ought to do the trick for now. Longer term, we need
to build up some infrastructure for testing for functions on our own. We
Goplat [EMAIL PROTECTED] wrote:
That defeats the whole point of 00ff-dos.t, which is to make sure parrot can
deal with lines ending in \r\n. IMO what should be done is to use \r\n in a
quoted string, instead of having the .t itself be \r\n (since that is what
was causing the problems, getting
Paul Cochrane [EMAIL PROTECTED] wrote:
Hi,
I got parrot to build on Alpha OSF1, but I can't get make test to go. Here's
what I see:
rolf:[524]/var/tmp/parrot/usr/bin/make test
perl t/harness --gc-debug --running-make-test -b t/op/*.t t/pmc/*.t
t/native_pbc/*.t imcc/t/*/*.t t/src/*.t
Gregor N. Purdy [EMAIL PROTECTED] wrote:
I was running the various languages/jako/examples and I ran
across this oddity (after doing a fresh 'make' of Parrot and
in the languages/jako directory):
[EMAIL PROTECTED] jako]$ ./jako examples/fact.jako
[EMAIL PROTECTED] jako]$ ../../parrot
Praise to Damian for Exegesis 7: the new formats sound very
well-thought-out, flexible, easy-to-use, and extensive -- as well as
being implemented and available right now. I've never used formats in
Perl 5, but I could see myself using Perl6::Form.
I have a few questions. Unfortunately I'm only
The :fill option gets a brief mention on page 10, but I didn't spot it
anywhere else or being used in an example:
There is also a general C:fill option that sets the default sequence
for any filling that isn't otherwise specified.
That suggests there's a hierarchy of options like this:
The C:page{:length} sub-option (page 12) is described in the text as
having a default value of infinity but in a comment in the example above
of being 60. How so?
Is that the text normally isn't split into pages at all (so effectively
giving a single page of infinite length), but as soon as
OK, I've given up on having completely separate mails and thrown
together a bunch of small points. Some of these are pointing out typos;
I mention them not to complain, but in case anybody's bothered about
correcting them to avoid future confusion.
* What happens if an undefined format is
[EMAIL PROTECTED] (Smylers) writes:
Also, not strictly to do with formats but raised by the above, how is
infinity written in Perl 6?
â
--
Complete the following sentence: People *ought* to weigh bricks, cats
and cinnamon in the same units because... - Ian Johnston
[EMAIL PROTECTED] (Smylers) writes:
Also, not strictly to do with formats but raised by the above, how is
infinity written in Perl 6?
â
?
--
dhd even though I know what a 'one time pad' is, it still sounds like
a feminine hygiene product.
First, thanks Damian for doing this, and good show!
Smylers already pointed out a few errors in the document, but
here are a few others I noticed:
* In Why, how now, ho! From whence ariseth this?
We have this near the top:
type FormArgs ::= Str|Array|Pair;
and this
In From the crown of his head to the sole of his foot... (clearly
a reference to a Gilligan's Island episode where Lovey said something
similar :), we have:
:header{ ..., odd = Act, $act, Scene $scene..., ... }
and below, text indicating that it will
prepend the act and scene
In the section He doth fill fields... we see an example of Fill
Justification where two spaces fit between every word. This doesn't
give us an idea of how spaces are distributed if the number of
spaces needed does not divide evenly into the number of interstices.
In the section More particulars
In Thou shalt have my best gown to make thee a pair..., we are
given a reason to use the option syntax vs. the pair constructing
fat comma C = : ...we're guaranteed that the key of the
resulting pair is a string, that the string [...] contains a valid
identifier, and that the compiler can check
In And now at length they overflow their banks. its not clear
how an overflow field gets tied to its initial non-overflow field.
In the recipe example given, how does it know to go with the
$method field instead of the $prep_time field? Is it basing off
of matching the horizontal extent of the
Gregor N. Purdy writes:
In And now at length they overflow their banks. its not clear
how an overflow field gets tied to its initial non-overflow field.
In the recipe example given, how does it know to go with the
$method field instead of the $prep_time field?
The definition given is:
An
The Exegesis mentions the Perl6::Slurp module, but I don't see it
on CPAN. Is it just a race condition?
Regards,
-- Gregor
--
Gregor Purdy[EMAIL PROTECTED]
Focus Research, Inc. http://www.focusresearch.com/
Gregor N. Purdy writes:
...we're guaranteed that the key of the resulting pair is a string,
that the string [...] contains a valid identifier, and that the
compiler can check the validity before the program starts.
We aren't told what validity checking the compiler is doing. I figure
its
I brought this up several months ago and was told that a new webpage was
in the works. Where in the works is it? Does it have an expected time
to leave the works? I agree with Mitchell that it is important to
maintain a public face (lest we send the wrong impression).
[...]
tcl failed to build? What was the error?
$ make
perl tcl.pl tcl.imc
../../parrot --output=tcl.pbc tcl.imc
error:imcc:Unknown PMC type 'var'
in file 'tcl.imc' line 11
make: *** [tcl.pbc] Error 1
$ pwd
[...]/parrot_2004-02-28_08/parrot/languages/tcl
Mitchell
Date: Sat, 28 Feb 2004
(1) ./README should mention perldoc . (perldoc -F?)
README points people at docs/parrot.pod and docs/intro.pod.
While perldoc is currently mentioned somewhere in the pods, by the
time folks see that, they've already been challenged - .pod? what's
a .pod? how do i read a .pod?. Even perl
On Saturday 28 February 2004 01:12 am, Mitchell N Charity wrote:
(1) LANGUAGES.STATUS is out of date.
I found (on linux x86 [1]):
These languages failed to build:
BASIC/interpreter
jako
miniperl
tcl
And these languages were quite broken (bad make test failures):
On Sat, Feb 28, 2004 at 02:17:05PM +, Smylers wrote:
(B: Also, not strictly to do with formats but raised by the above, how is
(B: infinity written in Perl 6 (for example, in C:page{:length($x)}
(B: how could C$x be assigned to infinity)?
(B
(BWhat we've said up till now is that Perl 6
On Fri, Feb 27, 2004 at 09:27:20PM -0700, John Williams wrote:
: On Fri, 27 Feb 2004, Luke Palmer wrote:
: John Williams writes:
: I want to get from here
:
:method bar_attr(?$val) is accessor {
: $.bar_attr = $val if exists $val;
: return $.bar_attr;
:}
:
: I
Ah.
Yes, this was one of the breakages from when Melvin tightened things up.
I'd commit a patch for it, but I have, in the margins of my notebook, a
reworked version that is much cleaner and implements more. I have a few
more things to clean up before I let this version go.
Someone with
And these languages were quite broken (bad make test failures):
[...]
m4
[...]
scheme
M4 and scheme pass all tests for me, on Gentoo Linux. myconfig is:
Ok, they both fail on my perl v5.6.0, and work on my v5.8.2.
The scheme test failures are perhaps a dependence of the
On Saturday 28 February 2004 02:17 pm, Mitchell N Charity wrote:
And these languages were quite broken (bad make test failures):
[...]
m4
[...]
scheme
M4 and scheme pass all tests for me, on Gentoo Linux. myconfig is:
Ok, they both fail on my perl v5.6.0, and
Smylers --
I think the claim in E7 is stronger, that not only does the string match
the identifier pattern, but that it is a 'valid' (known, declared)
identifier. Else, what would be the point of saying both:
* contains a valid identifier, and
* check the validity before the program starts
Smylers --
So, what I'm looking for is more explicit phrasing around immediately
above. In the example, the column range for the overflow field is
exactly the same as that of the $method field in the prior picture.
But, what does it do if it doesn't match *exactly*? Is it an error,
does it have
On Sat, Feb 28, 2004 at 02:42:47AM -0500, Austin Hastings wrote:
: Another hypothetical:
:
: Suppose you have a browser (which understands language traits)
: or a word processor (which stores style and/or font information)
: that is storing some not-text-only string-like things via scalar
:
On Sat, Feb 28, 2004 at 11:56:52AM -0800, Gregor N. Purdy wrote:
: Smylers --
:
: I think the claim in E7 is stronger, that not only does the string match
: the identifier pattern, but that it is a 'valid' (known, declared)
: identifier. Else, what would be the point of saying both:
:
: *
On Sat, Feb 28, 2004 at 11:59:15AM -0800, Gregor N. Purdy wrote:
: Smylers --
:
: So, what I'm looking for is more explicit phrasing around immediately
: above. In the example, the column range for the overflow field is
: exactly the same as that of the $method field in the prior picture.
: But,
On Sat, Feb 28, 2004 at 12:32:37PM -0800, Larry Wall wrote:
: Now I'm supposing that binds tighter than | as usual, so the
: brackets wouldn't always be necessary:
:
: ident french+
: |
: ident swahili+
Although, of course, that should probably be written:
ident [ french+ |
Gregor N. Purdy wrote:
Smylers already pointed out a few errors in the document, but
here are a few others I noticed:
* In Why, how now, ho! From whence ariseth this?
We have this near the top:
type FormArgs ::= Str|Array|Pair;
and this below:
type FormArgs ::=
Smylers wrote:
The C:page{:length} sub-option (page 12) is described in the text as
having a default value of infinity but in a comment in the example above
of being 60. How so?
Is that the text normally isn't split into pages at all (so effectively
giving a single page of infinite length), but
Gregor N. Purdy wrote:
In From the crown of his head to the sole of his foot... (clearly
a reference to a Gilligan's Island episode where Lovey said something
similar :), we have:
:header{ ..., odd = Act, $act, Scene $scene..., ... }
and below, text indicating that it will
prepend the
Gregor N. Purdy wrote:
So, what I'm looking for is more explicit phrasing around immediately
above. In the example, the column range for the overflow field is
exactly the same as that of the $method field in the prior picture.
But, what does it do if it doesn't match *exactly*? Is it an error,
Gregor N. Purdy wrote:
The Exegesis mentions the Perl6::Slurp module, but I don't see it
on CPAN. Is it just a race condition?
Race condition. That is, I'm racing to get it out. That process is being
slowed by the fact that I'm still designing parts of the interface in line
with feedback from
Smylers wrote:
Praise to Damian for Exegesis 7: the new formats sound very
well-thought-out, flexible, easy-to-use, and extensive -- as well as
being implemented and available right now. I've never used formats in
Perl 5, but I could see myself using Perl6::Form.
Thank-you.
I have a few
[EMAIL PROTECTED] (Damian Conway) writes:
Thanks for those. We'll leave them out overnight and see if the elves
will make them disappear from the various on-line versions. ;-)
It may take a *couple* of nights, but the elves will be at work.
--
Gods, you know your house is full of goths when
Larry Wall wrote:
On Sat, Feb 28, 2004 at 11:59:15AM -0800, Gregor N. Purdy wrote:
: Smylers --
:
: So, what I'm looking for is more explicit phrasing around immediately
: above. In the example, the column range for the overflow field is
: exactly the same as that of the $method field in the
Smylers wrote:
The :fill option gets a brief mention on page 10, but I didn't spot it
anywhere else or being used in an example:
There is also a general C:fill option that sets the default sequence
for any filling that isn't otherwise specified.
That suggests there's a hierarchy of options
Gregor N. Purdy wrote:
In the section He doth fill fields... we see an example of Fill
Justification where two spaces fit between every word. This doesn't
give us an idea of how spaces are distributed if the number of
spaces needed does not divide evenly into the number of interstices.
Currently
Luke Palmer wrote:
Mark A. Biggar writes:
Larry Wall wrote:
On Sat, Feb 28, 2004 at 11:59:15AM -0800, Gregor N. Purdy wrote:
: Smylers --
:
: So, what I'm looking for is more explicit phrasing around immediately
: above. In the example, the column range for the overflow field is
: exactly the
Luke Palmer wrote:
Arn't there cases where the overflow field want to be bigger then the
first field? Something the ends up looking like:
LABEL: texttexttextexttexttext
texttextexttextetexttexttextte
xttexttexttexttexttexttextttex
where LABEL is in one field and text... is in an oveflow block?
Simon Cozens wrote:
It may take a *couple* of nights, but the elves will be at work.
Bless their pointy little hats/ears/beards/shoes! ;-)
Damian
Mark A. Biggar wrote:
Expect wouldn't that produce a extra blank line if $text is short?
Nope. Formats only generate text lines if at least one of their fields
interpolates at least one character.
Damian
Damian Conway wrote:
Mark A. Biggar wrote:
Expect wouldn't that produce a extra blank line if $text is short?
Nope. Formats only generate text lines if at least one of their fields
interpolates at least one character.
Damian
What if I want to interpolate an empty string and let the fill
On Sat, 28 Feb 2004, Mitchell N Charity wrote:
(1) LANGUAGES.STATUS is out of date.
Just to round out the record, here's a summary of what I got on
Solaris 8, with Sun's compiler and Sun's perl5.005_03 for
'make languages' and 'make languages-test':
make languages:
befunge: OK
bf: OK
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #27200]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=27200
Stephane Peiry wrote:
On Mon, Feb 23, 2004 at 11:07:48AM +0100, Leopold
Given that the new webpage won't be replacing the old webpage in time
for this upcoming release...
I suggest we make a few simple modifications to the _existing
website_.
I'm not going to make any more changes to the existing website, but
since you asked nicely, I made these.
Also, are
Damian --
Good. I don't remember where I first heard about doing it that way
vs. from the left, but the results going from the right to left
are typically better looking than from left to right, and I use that
way exclusively now.
Regards,
-- Gregor
On Sat, 2004-02-28 at 15:54, Damian Conway
Leo --
Thanks for the pointer.
I made the change, and now I get consistent results. I'll check that in.
I am still not clear, though, on why we wouldn't have the same failure
in all cases. I'd think these should be equivalent:
* Running parrot on 'foo.imc'
* Running parrot on 'foo.pasm'
At 08:01 PM 2/28/2004 -0800, Gregor N. Purdy wrote:
I made the change, and now I get consistent results. I'll check that in.
I am still not clear, though, on why we wouldn't have the same failure
in all cases. I'd think these should be equivalent:
* Running parrot on 'foo.imc'
* Running
58 matches
Mail list logo
