Hi there,
While adding support for handling keyboard events to the SDL bindings
(see the attached patch; it's not for applying, as the documentation is
lacking and the interface exposes too many details), I discovered that
the alignment of members within a struct matters quite a bit.
That is, to
Jonathan Worthington [EMAIL PROTECTED] wrote:
Hi,
Back from unwellness and the subsequent need to catch up with a stack of
stuff, I finally found time to sync up my parrot tree and try a Win32 build.
Turns out it fails in event.c with a whole string of errors and warnings:-
events.c(67) :
Vladimir Lipsky [EMAIL PROTECTED] wrote:
From: Leopold Toetsch [EMAIL PROTECTED]
Yep, that's right. As our PMC size isn't a power of 2, there is a small
chance that Cvtable and Cstr_val are in different cache lines and
Even if the PMC size were a power of two, it woudn't necessitate Cvtable
Tim Bunce [EMAIL PROTECTED] wrote:
Yeah, I think getting the docs better will be an aggressive goal for
the next release.
How's this all looking now we're in Feb?
There is still a lot of outdated (or unimplemented?) stuff in assembly
related docs.
WRT release :)
,--[ p6i
Chromatic [EMAIL PROTECTED] wrote:
That is, to make the keyed struct work correctly, I had to add extra
bytes of padding in the appropriate places.
Have a look at the third initializer param - this is the offset of the
item in bytes.
(Albeit untested - seems you got the code to test it :)
Is
Okay, here's a quick scoop and status.
*) I'd like to shoot for a Feb 14th release. Names wanted. (I'm
partial to the bleeding heart release, but not that partial)
*) Namespaces are going to use the:
find_global Px, [key; key; key], final_name_string
format. I may add in a dummy:
Pete Lomax wrote:
Leo clarified this as a problem with backward branch circa 3/12/03:
Sorry to be a pain in the butt, but I need to be told that there has
been no improvement in the last two months on this ;-(
..sub _main
goto L1
test:
$I1 = 1
ret
L1:
$I2 = 2
On Tue, Feb 03, 2004 at 09:23:58AM +0100, Leopold Toetsch wrote:
Tim Bunce [EMAIL PROTECTED] wrote:
Yeah, I think getting the docs better will be an aggressive goal for
the next release.
How's this all looking now we're in Feb?
There is still a lot of outdated (or unimplemented?) stuff
Pete Lomax [EMAIL PROTECTED] wrote:
Leo clarified this as a problem with backward branch circa 3/12/03:
Surely it can't just be me that thinks this is rather fundamental?
How fundamental *is* the problem, can it *ever* be fixed?
It can be fixed. It'll take a lot of overhead. Following all
On Feb 2, 2004, at 9:53 PM, Kurt Starsinic wrote:
I realize this is a tad OT, but can anyone tell me how I can get Emacs
to properly display Unicode characters? I expect that others on the
list could benefit, too.
(require 'un-define)
Since I really don't understand Lisp, and since that
On Feb 3, 2004, at 7:13 AM, Kurt Starsinic wrote:
No joke. You'll need to have the mule-ucs module installed.
A quick Google search turns up plenty of sources.
Oh, I have Emacs 21.3.50. Mule is gone.
You'll also need to have the appropriate fonts installed, of
course.
You may need to
: =item * Comments
:
: We've already gone over this, but it'd be good to have the ability for
: parsers to (somehow) feed into one another, [...]
... I don't think it's out of the realm of possibility for
Perl 6 to support strings with embedded objects as funny characters.
In the limit, a
On Tuesday 03 February 2004 20:46, Tels wrote:
PS: Thanx for your suggestion, but what exactly does this do:
sub ok
{
@_ = 1;
goto Test::More::ok;
}
Pass a single (1), or only the first argument? *puzzled*
It passes a single (1) :-( It should be
$#_ = 0;
I got too
If I could just change Test; to Test::More; without hundreds of warnings
springing on me I know I would convert the test scripts and then change
them step by step over to the new code (or not change them at all, because
don't change working code..)
If you don't mind adding a
use
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Tuesday 03 February 2004 21:41, Fergal Daly wrote:
If I could just change Test; to Test::More; without hundreds of
warnings springing on me I know I would convert the test scripts and
then change them step by step over to the new code (or not
[EMAIL PROTECTED] (Leopold Toetsch) writes:
It can be fixed. It'll take a lot of overhead. Following all branches in
spaghetti code is a PITA.
Just don't do that. Separate your subs in distinct compilation units.
And then you don't need to worry about the fact that Parrot running
On Tue, Feb 03, 2004 at 04:35:46PM +, Harry Jackson wrote:
[... ]
Question:
Since Dan has said that objects are nearly finished is there any point
spending too much time working on this. Would our time be better spent
helping to get objects finished pronto.
I think so. It's basically a
At 1:12 AM + 2/3/04, Pete Lomax wrote:
Leo clarified this as a problem with backward branch circa 3/12/03:
Sorry to be a pain in the butt, but I need to be told that there has
been no improvement in the last two months on this ;-(
Short answer: Don't do that.
Longer answer: IMCC ought to
Dan Sugalski wrote:
Okay, here's a quick scoop and status.
*) I'd like to shoot for a Feb 14th release. Names wanted. (I'm partial
to the bleeding heart release, but not that partial)
You can always find some reference to a bird in it somewhere
http://www.newadvent.org/cathen/15254a.htm
We
On Tue, 2004-02-03 at 00:58, Leopold Toetsch wrote:
Have a look at the third initializer param - this is the offset of the
item in bytes.
Oh, right. That completely slipped my mind.
(Albeit untested - seems you got the code to test it :)
Okay, I'll turn this into a test case.
NCI is per
Dan Sugalski wrote:
Your code is fine. It *should* work. That it doesn't is a bug, which
needs fixing. For now you're going to have to work around it.
I would have swore the code was wrong. Am I being naive thinking that a
call to a sub is different than what looked like a call to a label. On
# New Ticket Created by Dan Sugalski
# Please include the string: [perl #25948]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=25948
the following code trips up IMCC's temp lifetime tracing:
.sub _main
-BEGIN PGP SIGNED MESSAGE-
Moin,
is there a re reason that the following warns:
% perl -MTest::More -le 'plan tests = 1; ok (1,1)'
1..1
# You named your test '1'. You shouldn't use numbers for your test
names.
# Very confusing.
and this
On Tuesday, February 3, 2004, at 05:44 pm, Tels wrote:
[snip]
This has prevented me from converting several huge old testsuites
from
use Test; to use Test::More; because I know that I would then have
to
go and add testnames to thousand of tests (e.g. all tests that test for
number output). This
On Tue, Feb 03, 2004 at 06:44:04PM +0100, Tels ([EMAIL PROTECTED]) wrote:
is there a re reason that the following warns:
% perl -MTest::More -le 'plan tests = 1; ok (1,1)'
1..1
# You named your test '1'. You shouldn't use numbers for your test
names.
#
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Tuesday 03 February 2004 19:26, Andy Lester wrote:
On Tue, Feb 03, 2004 at 06:44:04PM +0100, Tels ([EMAIL PROTECTED])
wrote:
is there a re reason that the following warns:
% perl -MTest::More -le 'plan tests = 1; ok (1,1)'
1..1
On Tue, 2004-02-03 at 12:46, Tels wrote:
I still think a big warning should be added to Test::More beeing _not_ a
drop-in replacement to Test.
I can only remember calling it a drop-in replacement for Test::Simple.
-- c
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Tuesday 03 February 2004 19:08, Adrian Howard wrote:
On Tuesday, February 3, 2004, at 05:44 pm, Tels wrote:
[snip]
This has prevented me from converting several huge old testsuites
from
use Test; to use Test::More; because I know that I would
On Tue, Feb 03, 2004 at 08:41:13PM +, Fergal Daly wrote:
package MyModule::OKSwapper;
require Test::More;
require Exporter;
@ISA = qw( Exporter);
@EXPORT= qw( ok );
sub ok
{
@_ = 1;
goto Test::More::ok;
}
Then, when you fix all the ok()s in a file, just delete the
Here's a version that actually works. Feel free to take this module and
run with it.
Trying to use this module uncovered a bug in Test::More::plan() where this:
plan tests = 1;
is the equivalent of
plan tests = 1;
Test::More-import;
Thus you pretty much must do:
use Test::More tests
On Feb 02, David Wheeler wrote:
On Feb 2, 2004, at 9:53 PM, Kurt Starsinic wrote:
I realize this is a tad OT, but can anyone tell me how I can get Emacs
to properly display Unicode characters? I expect that others on the
list could benefit, too.
(require 'un-define)
Since I really
Larry Wall writes:
On Mon, Feb 02, 2004 at 02:09:33AM -0700, Luke Palmer wrote:
: method if_statement::code($rc) { # $rc is the regcounter
: self.item[0].code($rc.next('condition'))
: ~ unless $rc{condition}, $rc{Lfalse}\n
: ~ self.item[1].code($rc.next)
:
The Perl 6 Summary for the week ending 20040201
Welcome once again to Gateshead, where the skies are grey, the view is
uninspiring, and the workmen across the road seem determined to fall off
the ladder before they get the double glazing fitted.
But enough of the gay Gateshead
Luke Palmer wrote:
Austin Hastings writes:
Hmm. The text and examples so far have been about methods and this
seems to be about multi-methods. Correct me if I'm wrong ...
You're wrong. Consider my example, where via single inheritance we reach a
layered list of methods, each of which
34 matches
Mail list logo
