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 parrot
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' gen
> 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, a
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #27200]
# in the subject line of all future correspondence about this issue.
# 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 Toetsch
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
col
On Fri, Feb 27, 2004 at 10:08:33PM -0500, Joseph Ryan wrote:
: Larry Wall wrote:
:
: >On Fri, Feb 27, 2004 at 09:08:31AM -0500, Dan Sugalski wrote:
: >: Nope. If a language wants to provide get/set methods for class
: >: attributes it needs to create those methods at compilation time.
: >
: >For
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
> 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
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 commit
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):
> BA
(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 f
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 01
> 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).
[.
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
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, ge
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/
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. W
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 thi
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 succe
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.
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 st
I saw the report that Jako wasn't working right with the latest
Parrot, so I went to investigate.
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/fac
22 matches
Mail list logo
