Re: Halloween release
Melvin Smith [EMAIL PROTECTED] wrote: I propose a Halloween release. Nothing fancy, just something fun. :) We should be able to reach some sort of minor milestone to justify it I'm sure. Too much in flux currently, though not only one milestone seem to be near. -Melvin leo
Re: [perl #24267] Inconsistent behaviour of logical or op
Simon Glover [EMAIL PROTECTED] wrote: I don't think your fix is correct, since: Yep, you are right, sorry. Having done some more nosing around, I see that PerlString doesn't actually have its own implementation of logical_or; instead, it falls back on the scalar.pmc version, which does: So does now PerlInt. The implementation in scalar.pmc is good enough. Simon Thanks, leo
Re: A less controvertial API addition
Dan Sugalski [EMAIL PROTECTED] wrote: We probably need two API entries. One, a vararg version, that just takes a bunch of PMC pointers (or some sort of (ick) parameter signature), and a second that assumes you've set the registers up properly already. Done both now. The (ick) signature variant is Parrot_runops_fromc_args() needs some testing though, and some clarifaction WRT return conventions. It could also preserve registers if a flag is given or setup an exception handler, but its for sure somewhat slower then the direct calls in delegate.pmc. Dan leo
[PS] obsolete files
Here is a list of files that I consider to be unused: * ops2cgc.pl unused, functionality is in ops2c.pl * make.pl unused?, seems outdated * classes/csub.pmc AFAIK unused, we have NCI, method_util is outdated * classes/pointer.pmc used AFAIK only by rx.ops - should be a ManagedStruct If no one hollers, I'll remove these and change rx.ops to use a ManagedStruct PMC. leo
Re: cvs commit: parrot/classes delegate.pmc
Dan Sugalski [EMAIL PROTECTED] wrote: 1.1 parrot/classes/delegate.pmc /* These need to be elsewhere */ #define PARROT_VTABLE_INIT_METHNAME __init Done. These defines are now autogenerated by Vtable.pm and live in vtable.h. Hope that's ok. A PASM include vtable_methods.pasm is generated too. leo
Re: Halloween release
On Wed, 22 Oct 2003, Melvin Smith wrote: I propose a Halloween release. Nothing fancy, just something fun. :) We should be able to reach some sort of minor milestone to justify it I'm sure. Oct 31, the screaming pumkin release? :) Sounds good -- lets see where we stand on Monday and go from there. Dan --it's like this--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Re: [COMMIT] imcc moves out of languages
Shouldn't imcc/docs (eventually) be docs/imcc, and imcc/t be t/imcc? Mike On Thursday, Oct 23, 2003, at 04:29 Europe/Berlin, Melvin Smith wrote: IMCC has graduated from the parrot/languages/imcc directory to parrot/imcc. Please update your trees. We may still want to move the main up to the parrot directory and possibly do an include/imcc directory, but I'm not sure. Test builds on my machine, so I think everything is back to intact for now. -Melvin
Re: [COMMIT] imcc moves out of languages
On Thu, 23 Oct 2003, Michael Scott wrote: Shouldn't imcc/docs (eventually) be docs/imcc, and imcc/t be t/imcc? Yeah, but lets deal with the initial aftermat first... On Thursday, Oct 23, 2003, at 04:29 Europe/Berlin, Melvin Smith wrote: IMCC has graduated from the parrot/languages/imcc directory to parrot/imcc. Please update your trees. We may still want to move the main up to the parrot directory and possibly do an include/imcc directory, but I'm not sure. Test builds on my machine, so I think everything is back to intact for now. -Melvin Dan --it's like this--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Re: [COMMIT] imcc moves out of languages
Almost forgot: imcc/examples to be (eventually) examples/imcc. Mike
Re: [COMMIT] imcc moves out of languages
At 08:41 AM 10/23/2003 +0200, Leopold Toetsch wrote: Robert Spier [EMAIL PROTECTED] wrote: [ quoting reordered ] Melvin Smith wrote: IMCC has graduated from the parrot/languages/imcc directory to parrot/imcc. Arghh[1] Ok guys, let us not make mountains out of molehills. So much for preserving repository history. Yep. Is the history gone, or are you able to do something for it? Does it really matter at 0.0.11 ?? [1] There was a lot of discussion on the list, how and why we will move files around. Melvin, please (re)read p6i or perl.perl6.internals Leo, there is always a lot of discussion, and my apologies for not reading every last line, I do my best between jobs. We have a snapshot from last night before my change. If it means that much, hopefully Robert can work some magic, or move it back where it was and I'll happily clean up the mess. -Melvin
Re: [PS] obsolete files
On Thu, 23 Oct 2003, Leopold Toetsch wrote: Here is a list of files that I consider to be unused: * ops2cgc.pl unused, functionality is in ops2c.pl * make.pl unused?, seems outdated * classes/csub.pmc AFAIK unused, we have NCI, method_util is outdated * classes/pointer.pmc used AFAIK only by rx.ops - should be a ManagedStruct If no one hollers, I'll remove these and change rx.ops to use a ManagedStruct PMC. Can I also suggest: optimizer.pl lib/Parrot/Optimizer.pm They haven't been touched for 20 months / 16 months respectively, I don't know of anybody using them, and I think that IMCC makes them obsolete. Simon
Re: [PS] obsolete files
Simon Glover wrote: On Thu, 23 Oct 2003, Leopold Toetsch wrote: Here is a list of files that I consider to be unused: Can I also suggest: optimizer.pl lib/Parrot/Optimizer.pm They haven't been touched for 20 months / 16 months respectively, I don't know of anybody using them, and I think that IMCC makes them obsolete. Yep, that's right. BTW, what about the perl PackFile stuff, unused and outdated too? Simon Thanks, leo
More file moves
Robert (the great god of CVS) is going to do the final set of big moves later on. Or possibly already has, depending on when you get this. This may, probably will, break things for a while. The scoop is: *.ops and ops.num are in the ops directory, where all ops should go from now on. *.c is in the base directory All the .pl files except for Configure.pl are in the build_tools directory When this is done I'll fix up the MANIFEST and makefile programs to make this all work properly. Dan --it's like this--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Re: [PS] obsolete files
docs/parrot_assembly.pod is just an earlier version of PDD 6. On Thursday, Oct 23, 2003, at 18:34 Europe/Berlin, Leopold Toetsch wrote: Simon Glover wrote: On Thu, 23 Oct 2003, Leopold Toetsch wrote: Here is a list of files that I consider to be unused: Can I also suggest: optimizer.pl lib/Parrot/Optimizer.pm They haven't been touched for 20 months / 16 months respectively, I don't know of anybody using them, and I think that IMCC makes them obsolete. Yep, that's right. BTW, what about the perl PackFile stuff, unused and outdated too? Simon Thanks, leo
Re: More file moves
Robert (the great god of CVS) is going to do the final set of big moves later on. Or possibly already has, depending on when you get this. This may, probably will, break things for a while. The scoop is: I have done this, and there is blood all over the walls. When this is done I'll fix up the MANIFEST and makefile programs to make this all work properly. Dan is off to clean this up now. I hope he's got lots of bleach and rubber gloves. (I recommend not doing a CVS update until Dan says he's reattached the head.) -R
Re: [COMMIT] imcc moves out of languages
Robert Spier [EMAIL PROTECTED] wrote: So much for preserving repository history. Yep. Is the history gone, or are you able to do something for it? I've reattached the history to the files. All should be well. Thanks again for keeping the machinery running, leo
Re: More file moves
On Thu, 23 Oct 2003, Dan Sugalski wrote: *.ops and ops.num are in the ops directory, where all ops should go from now on. *.c is in the base directory Um, it actually appears to be in the src directory; the base directory is empty. Was this an intentional change of plan? Simon
Re: More file moves
On Thu, 23 Oct 2003, Simon Glover wrote: On Thu, 23 Oct 2003, Dan Sugalski wrote: *.ops and ops.num are in the ops directory, where all ops should go from now on. *.c is in the base directory Um, it actually appears to be in the src directory; the base directory is empty. Was this an intentional change of plan? Yes. Plans changed between mail and implementation, courtesy of IRC chats. :) Dan --it's like this--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Re: [COMMIT] imcc moves out of languages
Thanks Robert for the fixup. Nothing like throwing a grenade to get people scrambling. -Melvin -Original Message- From: Robert Spier [EMAIL PROTECTED] Sent: Oct 23, 2003 1:33 PM To: [EMAIL PROTECTED] Subject: Re: [COMMIT] imcc moves out of languages So much for preserving repository history. Yep. Is the history gone, or are you able to do something for it? I've reattached the history to the files. All should be well. Depending on when you last updated, you _may_ see weird warnings on your next update -- they should be harmless. -R
Almost, but not quite, there
And I could certainly do with some help at this point. Parrot is *almost* put back together. There's some weird linking problem that's keeping parrot from working out as it should, and I've not been able to track it down. If anyone feels like syncing up and giving it a shot, I'd not mind it at all. Dan --it's like this--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Re: [PS] obsolete files
Leopold Toetsch wrote: Here is a list of files that I consider to be unused: Hmmm... obsolete... unused... sounds a lot like languages/perl6 :-P - Joe
Re: Almost, but not quite, there
At 4:43 PM -0400 10/23/03, Dan Sugalski wrote: And I could certainly do with some help at this point. Parrot is *almost* put back together. There's some weird linking problem that's keeping parrot from working out as it should, and I've not been able to track it down. If anyone feels like syncing up and giving it a shot, I'd not mind it at all. And now we're fine, and even test good with the JIT. Woohoo! Time to thump it some and see what I missed. -- Dan --it's like this--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Re: Almost, but not quite, there
On Thu, 23 Oct 2003, Dan Sugalski wrote:
At 4:43 PM -0400 10/23/03, Dan Sugalski wrote:
And I could certainly do with some help at this point.
Parrot is *almost* put back together. There's some weird linking problem
that's keeping parrot from working out as it should, and I've not been
able to track it down. If anyone feels like syncing up and giving it a
shot, I'd not mind it at all.
And now we're fine, and even test good with the JIT. Woohoo!
Time to thump it some and see what I missed.
Well, I've just stumbled across one problem: if you run Configure
with --ask, then it won't accept its own default list of ops files.
The problem is this bit of config/inter/ops.pl:
{
$ops=prompt('Which opcode files would you like?', $ops);
if($ops !~ m{^\s*core\.ops}) {
print core.ops must be the first selection.\n;
redo;
}
}
}
Configure lists ops/core.ops as the first in the list of default ops
files, but this doesn't match the regex. The patch below fixes this
on Unix, but probably isn't portable to Win32; I imagine there's a
better way to fix it.
Simon
Index: config/inter/ops.pl
===
RCS file: /cvs/public/parrot/config/inter/ops.pl,v
retrieving revision 1.2
diff -u -r1.2 ops.pl
--- config/inter/ops.pl 23 Oct 2003 19:21:30 - 1.2
+++ config/inter/ops.pl 23 Oct 2003 22:19:39 -
@@ -34,7 +34,7 @@
{
$ops=prompt('Which opcode files would you like?', $ops);
- if($ops !~ m{^\s*core\.ops}) {
+ if($ops !~ m{^ops/\s*core\.ops}) {
print core.ops must be the first selection.\n;
redo;
}
