On Fri, 2006-04-21 at 13:27 -0700, [EMAIL PROTECTED] wrote:
> Bitwise operations on a C generally fail unless the
> +C in question can provide an abstract C interface somehow.
> +Coercion to C should generally invalidate the C interface.
> +As a generic type C may be instantiated as (or bound to) a
>From S06:
*
As we saw earlier, "zip" produces little arrays by taking one element
from each list in turn, so
(0..2; 'a'..'c') ==> my @;tmp;
for @;tmp.zip { say }
produces [0,'a'],[1,'b'],[2,'c']. If you don't want the subarrays, then
use C instead:
(0..2; 'a'..'c') ==> my @;tm
What backends support packed native arrays at this point? And what's
the performance like?
Native access to packed arrays is the big thing I'm looking for before I
port a pile of source filtered Perl 5 code to Perl 6. It's a simple 3D
engine, so all of the libraries I need to work with want to w
On Sun, 2007-02-25 at 12:15 -0800, Jonathan Lang wrote:
> I submit that you'll have even more luck discouraging such things if
> you can give a reasonable and believable timeline as to when the 6.0
> spec will be ready and perl 6.1 features can start being considered.
As I mentioned in another thr
On Sun, 2007-02-25 at 13:26 -0800, chromatic wrote:
> On Sunday 25 February 2007 12:56, Geoffrey Broadwell wrote:
>
> > As I mentioned in another thread, but didn't make clear in that email: I
> > don't need a "finished" spec. I need the *current* ver
On Sun, 2007-02-25 at 14:16 -0800, chromatic wrote:
> On Sunday 25 February 2007 13:57, Geoffrey Broadwell wrote:
>
> > I'm not trying to say that the implementors should rush either, nor am I
> > complaining about current status; I grok the dynamics of volunteer code.
>
On Mon, 2007-02-26 at 08:25 -0600, Patrick R. Michaud wrote:
> On Sun, Feb 25, 2007 at 03:48:47PM -0800, chromatic wrote:
> > On Sunday 25 February 2007 12:40, Geoffrey Broadwell wrote:
> >
> > > What backends support packed native arrays at this point? And what'
> Pugs at the moment support all of the above, using the Perl 5 bridge
> for "use perl5:SDL" and "use perl5:OpenGL". So the sole requirement
> seems to be:
Cool beans. I'd had some simple OpenGL code working-with-hacks on Pugs
many months ago, but I did not know the current status after all the
On Tue, 2007-02-27 at 03:02 +0800, Audrey Tang wrote:
> 2007/2/27, Geoffrey Broadwell <[EMAIL PROTECTED]>:
> > Are you looking for Perl code that creates such packed arrays and passes
> > them to OpenGL? Or are you looking for links to manpages for the OpenGL
> >
On Mon, 2007-02-26 at 16:29 -0800, chromatic wrote:
> On Monday 26 February 2007 11:29, Geoffrey Broadwell wrote:
>
> > Does Perl 6 on Parrot have Perl 5 connectivity?
>
> Not until Perl 6 can use PIR code. After that, it depends on what you want
> to
> do with the
I'd like to request that num16 and therefore complex16 be added to S09,
and made optional just as num128 and complex128 are. The half-sized
floating point type is commonly used in computer graphics and widely
supported by GPUs and High Dynamic Range image formats such as OpenEXR.
-'f
How are the bitwise shifts defined on low level types? In particular,
for right shift, does high bit extension or zero fill occur? Does the
answer depend on whether the low level type is signed or not?
On the flip side, it seems more useful if we have both operators
available for either signed o
Does Perl 6 have (bit/string) rotation ops? Especially bit rotation on
low-level integer types would be Nifty for making some numeric
algorithms cleaner, more self documenting, and potentially faster than
forcing the use of a combination of other bitwise ops to do the same
thing.
-'f
What happens when a low-level type overflows or underflows? For
example, if you decrement an int1 twice, what happens?
If you increment a uint8 past 255, do you get:
1. A uint8 with value 0?
2. A uint16 with value 256?
3. A failure?
What about incrementing an int8 past 127? Do you get:
1. An
What happens when you cast between low-level types? If the source value
is out of range of the destination type, do you get:
1. An exception?
2. Clip to finite range always?
3. Clip to finite range for ints, clip to infinities for nums?
4. Exception when dest is int, clip to infinities when dest
How do you specify that you want to byte-stringify a compact struct,
rather than "normal" stringify it?
Does the byte-stringified version include internal and/or trailing
alignment padding? How do you specify the other choices?
Whether or not trailing padding is included when byte-stringifying a
On Tue, 2007-02-27 at 09:20 -0800, Geoffrey Broadwell wrote:
> How is casting and coersion handled with expressions involving mixed low
> and high level types?
>
> For example, what is the output of this?
>
> my Int $ten = 10;
> my int4 $a = 0;
> my in
How is casting and coersion handled with expressions involving mixed low
and high level types?
For example, what is the output of this?
my Int $ten = 10;
my int4 $a = 0;
my int4 $b;
$b = ($a + 2.4 * $ten) / 4;
say $b;
The answers to the above questions may alter my view o
On Wed, 2007-03-07 at 21:35 -0800, [EMAIL PROTECTED] wrote:
> +So these are in sorted version order:
> +
> +1.2.0.999
> +1.2.1_01
> +1.2.1_2
> +1.2.1_003
> +1.2.1a1
> +1.2.1.alpha1
> +1.2.1b1
> +1.2.1.beta1
> +1.2.1.gamma
> +1.2.1α1
> +1.2.1β1
> +1.2.
The first entry in my new weekly "Perl etc." O'Reilly blog is up:
http://www.oreillynet.com/pub/wlg/7928
When I mentioned it on #perl6, nothingmuch suggested I post to p6l as
well. So here you go. :-)
-'f
I love doing binary codecs for Raku[1]! How you approach this really
depends on what formats and protocols you want to create Raku modules for.
The first thing you need to be able to do is test if your codec is
correct. It is notoriously easy to make a tiny mistake in a protocol
implementati
rotocol, do
you know how to port it to perl or perl6?
https://ignite.apache.org/docs/latest/binary-client-protocol/binary-client-protocol
I was using their python/ruby clients, but there is not a perl version.
Thanks.
Piper
On Tue, Jan 4, 2022 at 11:15 AM Geoffrey Broadwell <mailto:g...@sonic.n
On Fri, 2007-04-13 at 19:00 -0700, Jonathan Lang wrote:
> Please. I've always found the "opendir ... readdir ... closedir" set
> to be clunky.
>
> Also: why distinguish between "open" and "opendir"? If the string is
> the name of a file, 'open' means "open the file"; if it is the name of
> a dir
On Thu, 2007-09-06 at 12:37 -0700, Larry Wall wrote:
> Yow. ICATBW.
The what now?
-'f
Not too put too strong a bias on it, but:
XML processors are a dime a dozen. There is no way for us to know *now*
what the "best" XML processor(s) will be a decade from now, and Perl 6
is intended to be a very long term language. And frankly there are
enough different use cases to ensure that no
On Wed, 2007-11-28 at 19:59 +0100, James Fuller wrote:
> XML Parser is what I am talking about
OK -- do you want an event-based parser? Do you want a DOM parser? Do
you want a simplified tree generator parser? Do you care about memory
limitations? Run time?
Does the parser need to be robust a
On Wed, 2007-11-28 at 11:46 -0800, chromatic wrote:
> The criterion for including a module in the core is "Is this necessary to get
> and install other modules?" not "Why not include this module?"
WELL SAID.
-'f
On Thu, 2008-07-17 at 22:50 +0200, Reini Urban wrote:
> The problem I had with the w32api libs was -lglut32. with linking
> directly to the dll /usr/bin/glut32.dll everything works fine, and I'll
> get rid of freeglut as default.
I'm not sure I understand what you meant here.
> Now I only have
I've noticed several patches from you today in which you're adding code
to try to load an existing library under additional library names for
cygwin support. It's beginning to look like this is a common operation.
I needed this for the OpenGL bindings, so I wrote a utility routine in
runtime/parr
I noticed a couple commits overnight for Lua to support OpenGL. I'm a
bit confused by them, since they don't seem to actually *do* anything,
just lots of (hopefully automatically generated!) scaffolding.
fperrad: How do these bindings actually work?
Everyone:
We're getting to the stage that HLL
On Mon, 2008-07-21 at 09:34 +0200, François Perrad wrote:
> Geoffrey Broadwell a écrit :
> > fperrad: How do these bindings actually work?
> There'll work with runtime/parrot/library/OpenGL.pir.
OK ... so what could be improved about runtime/parrot/library/OpenGL.pir
so that y
On Tue, 2008-07-22 at 09:03 +0200, François Perrad wrote:
> Ok, talking about libraries :
> Lua compiler & Lua Standard Libraries are complete (as far as the
> current Parrot supports it).
> So, since April 2008, I wrote some extension libraries for Lua
> Since mid-June 2008, I tried to write exte
On Tue, 2008-07-22 at 15:37 -0700, chromatic wrote:
> The wiki page at:
>
> http://www.perlfoundation.org/parrot/index.cgi?inter_hll_mapping_notes
>
> seems to be missing the rationale for *why* it's necessary to map types
> between languages? (Also see "If Perl 6 has to care about the in
On Tue, 2008-07-22 at 22:58 -0400, Bob Rogers wrote:
>So I would argue that (1) what seem like differences in numbers in
> the various languages are really differences in the way those languages
> define their numeric operators, not in the numbers themselves;
I disagree. How do you represent
On Wed, 2008-07-23 at 10:11 -0400, Bob Rogers wrote:
> True. But passing a Complex to any language that does not have a
> concept of Complex is going to cause problems if the language tries to
> treat it as anything but a black box. And a black box doesn't require a
> special representation.
But
On Wed, 2008-07-23 at 17:09 +0200, François Perrad wrote:
> > >From a couple comments you make later, it sounds like you're aiming to
> > be perfectly API compatible with the original library implementations
> > for Lua and PHP, so that moving to Parrot is a "drop-in" replacement as
> > far as the
On Fri, 2008-07-25 at 13:40 +0200, Peter Gibbs wrote:
> +HUGEINTVAL num;
Does this really need to be a HUGEINTVAL? Why is INTVAL not sufficient?
-'f
On Fri, 2008-07-25 at 22:18 +0200, Peter Gibbs wrote:
> typedef HUGEINTVAL(*sprintf_getint_t) (PARROT_INTERP,INTVAL,
> SPRINTF_OBJ *);
>
> So, since obj->getint returns a HUGEINTVAL, I gave it one to store the
> result in.
Fair enough, that's good enough for me.
> As to why sprintf_obj is
On Sun, 2008-07-27 at 13:13 +0200, Reini Urban wrote:
> +stat $I0, conf_file, 0
> +if $I0 goto conf
> +
> +# If installed into /usr/lib/parrot, not /usr/runtime/parrot
> +# This logic has to be reversed when installed versions should
> run faster
> +# than source builds.
Re
On Sun, 2008-07-27 at 12:10 -0700, Will Coleda via RT wrote:
> On Sun, Jul 27, 2008 at 1:08 PM, via RT Geoffrey Broadwell
> <[EMAIL PROTECTED]> wrote:
> > # New Ticket Created by Geoffrey Broadwell
> > # Please include the string: [perl #57344]
> > # in
I'll reply to the rest of this (if someone doesn't beat me to it)
tomorrow, but just wanted to comment on your closing comment:
On Sun, 2008-07-27 at 22:25 -0700, jerry gay wrote:
> that's an install tree
> policy, and as far as i'm concerned, it hasn't been addressed yet
> (along with many other
On Tue, 2008-08-05 at 13:20 -0400, Will Coleda wrote:
> On Tue, Aug 5, 2008 at 1:10 PM, chromatic <[EMAIL PROTECTED]> wrote:
> > Gah, no maintenance releases please! See "Mommy, why did it take over five
> > years to release a new stable version of Perl 5 with a bugfix I made in
> > 2002?"
>
> Per
On Tue, 2008-08-05 at 11:19 -0400, Jesse Vincent wrote:
> ["branch" feature]
This sounds very useful. Is the SVK paradigm changing so that online
use is assumed, and offline is a mode to switch to temporarily? I'm
used to thinking of SVK in one two ways:
1. As a better SVN client for normal
On Tue, 2008-08-05 at 12:54 -0700, chromatic wrote:
> On Tuesday 05 August 2008 12:35:50 Geoffrey Broadwell wrote:
> > bugfixes that should be backported to one or more already released
> > versions and re-released immediately.
>
> I can see patching the previous release
On Tue, 2008-08-05 at 16:19 -0400, Michael Peters wrote:
> We also need to think about deprecation cycles. If you deprecate a
> feature in 1 version and then it disappears in the next then the time
> between when my code works and when it doesn't is only 6 months. Some
> distros provide support
On Fri, 2008-08-15 at 07:00 -0700, Will Coleda wrote:
> #not ok 1 - Line length ok
> # Failed test 'Line length ok'
> # at t/codingstd/linelength.t line 80.
> # Lines longer than coding standard limit (100 columns) in 1 files:
> # /home/smoke/parrot/compilers/pirc/new/pirsymbol.c:256: 104 cols
On Fri, 2008-08-15 at 11:57 -0400, Will Coleda wrote:
> >> This causes -all- smolder reports to be marked as failures.
> >
> > Perhaps 'make codetest' or 'make codingstd_tests' should be an automated
> > commit hurdle? Meaning, SVN won't allow the commit if those don't pass.
>
> Assuming we actua
On Mon, 2008-08-18 at 17:44 -0400, Michael Peters wrote:
> Allison Randal wrote:
>
> > It's true that you can't get a Python array and expect it to respond to
> > all the same method calls as a Tcl array. But that Python array is just
> > another variable type, that accepts keyed access and meth
On Wed, 2008-08-20 at 22:20 +0200, Ron Blaschke wrote:
> I think we need a way to select the calling convention for a function,
> similar to, or maybe even part of, the signature. Also, it would be
> good to have a way to select a calling convention when loading a
> library, as a calling conventio
On Thu, 2008-08-28 at 00:03 -0700, Allison Randal wrote:
> Briefly discussed on the phone with Patrick, Jerry, and chromatic: The
> versions of the math opcodes that modify an existing destination PMC
> instead of creating a new destination PMC are not useful to HLLs,
> because they make assumpt
On Tue, 2008-09-02 at 12:32 -0700, Darren Duncan wrote:
> Now a common factor to both of my proposals is that this Test.pm is
> intentionally kept as simple as possible and contains just the
> functionality needed to bootstrap the official Perl 6 test suite; if the
> official test suite doesn't
On Thu, 2008-09-18 at 07:34 -0500, Patrick R. Michaud wrote:
> > "Aggregating coroutine" and "aggregating yield" aren't nearly as zippy
> > as 'gather' and 'take', but they're more meaningful to a broader
> > audience, which may help the feature spread.
I don't buy this. The Perl 6 terms are
On Thu, 2008-09-18 at 10:28 -0700, jerry gay wrote:
> On Thu, Sep 18, 2008 at 10:21 AM, Patrick R. Michaud <[EMAIL PROTECTED]>
> wrote:
> > On Thu, Sep 18, 2008 at 09:06:44AM -0700, jerry gay wrote:
> >> what some refer to as "traits", perl 6 calls "roles".
The Perl 6 name is a better, more natur
On Wed, 2008-09-24 at 18:09 -0500, Patrick R. Michaud wrote:
> On Thu, Sep 25, 2008 at 12:10:35AM +0200, Reini Urban wrote:
> > 2008/9/24 Patrick R. Michaud <[EMAIL PROTECTED]>:
> > > So, in order to get the behavior you're describing from the interactive
> > > prompt, we'll probably need more than
Tom Christiansen:
> > Don't we have to solve all this to get the Perl 6 debugger
> > working anyway?
>
> Although I'm unsure why that might be, I also recognize the possibility
> that there may well exist hypothetical documents, unread by me, which
> mandate some scenario or behavior wherein the
On Fri, 2008-10-03 at 08:55 -0700, Will Coleda wrote:
> Index: Makefile.PL
> ===
> -BEGIN { require 5.008 }
> +BEGIN { require 5.8.6 }
> Index: Configure.pl
> ===
> -use
On Sun, 2008-10-05 at 17:05 -0700, [EMAIL PROTECTED] wrote:
> +C<< infix:<...> >>, the series operator.
Lovely, just lovely.
> +1, 3, 5 ... *# odd numbers
> +1. 2. 4 ... *# powers of 2
Did you mean to use commas on that second line?
-'f
On Wed, 2008-11-26 at 11:34 -0800, Darren Duncan wrote:
> I agree with the idea of making Perl 6's filesystem/etc interface more
> abstract,
> as previously discussed, and also that users should be able to choose between
> different levels of abstraction where that makes sense, either picking a
On Tue, 2008-12-02 at 08:50 +0100, Carl Mäsak wrote:
> Darren (>):
> > Bit
> > Blob
> > Set
> > Bag
> > Mapping
> >
> > How does one write anonymous value literals of those types? And I mean
> > directly, not by writing a literal of some other type and using a conversion
> > function to deriv
On Tue, 2008-12-02 at 13:07 -0700, David Green wrote:
> On 2008-Dec-2, at 12:33 pm, Geoffrey Broadwell wrote:
> > On Tue, 2008-12-02 at 08:50 +0100, Carl Mäsak wrote:
> >> Darren (>):
> >>> How does one write anonymous value literals of those types?
> >
On Tue, 2008-12-02 at 21:21 +0100, Leon Timmermans wrote:
> If you really want it, a macro can fix all of this for you.
> That's the beauty of macros: these kinds of things are possible if you
> need them.
Sure, but user-written macros are also an easy out that allows one to
avoid making hard deci
On Fri, 2008-12-05 at 09:10 -0600, Andy Lester wrote:
> On Dec 5, 2008, at 4:13 AM, Simon Cozens wrote:
>
> > I just ran this code, which worked with the expected results:
>
>
> Beautiful. Posted to Perlbuzz.
>
> http://perlbuzz.com/2008/12/database-access-in-perl-6-is-coming-along-nicely.html
On Fri, 2008-12-05 at 13:13 -0600, Andy Lester wrote:
> On Dec 5, 2008, at 1:11 PM, Geoffrey Broadwell wrote:
> > I can't, because as Perlbuzz oh-so-helpfully tells me when I try to
> > submit my comment: "Registration is required." With no indication how
> >
On Tue, 2008-12-23 at 17:31 -0800, Will Coleda via RT wrote:
> chromatic mentioned on #parrot that if we remove PIC, we're going to break
> all the
> predereferenced runcores. After some discussion, this probably means ripping
> out:
>
> 16:42 <@chromatic> Everything other than the default core
In the below Perl 5 code, I refactored to pull the two halves of the PID
file handling out of init_server(), but to do so, I had to return a sub
from pid_file_handler() that acted as a "continuation". The syntax is a
bit ugly, though. Is there a cleaner way to this in Perl 6?
##
sub init_ser
On Fri, 2009-01-02 at 00:30 +0200, Leon Timmermans wrote:
> I can't help wondering "why does pid_file_handler need to be split up
> in the first place?" Why wouldn't it be possible to simply call
> pid_file_handler after become_daemon?
Two answers:
1. If an error occurs that will not allow the PI
On Fri, 2009-01-02 at 14:19 +0200, Leon Timmermans wrote:
> When going OO, I'd say an augment()/inner() approach would be
> cleanest. See
> http://search.cpan.org/~drolsky/Moose/lib/Moose/Cookbook/Basics/Recipe6.pod
> for an example. I don't know how to express that in Perl 6 though.
There's no d
On Fri, 2009-01-02 at 17:08 +0100, pugs-comm...@feather.perl6.nl wrote:
> +=head2 Synopsis
> +
> + multi sub perl6(
> +Bool :a($autosplit),
> +Bool :c($check-syntax),
> +Bool :$doc,
> +:e($execute),
> +:$execute-lax, #TODO fix illegal -e6 syntax. -6? not legal. -x? hrmm
> +
Thank you for the quick turnaround!
On Fri, 2009-01-02 at 10:55 -0800, jerry gay wrote:
> On Fri, Jan 2, 2009 at 09:27, Geoffrey Broadwell wrote:
> > It's also not
> > obvious what a boolean named $doc does -- which probably means either
> > that it's not supposed
On Fri, 2009-01-02 at 22:56 +0100, Aristotle Pagaltzis wrote:
> > When I asked this question on #perl6, pmurias suggested using
> > gather/take syntax, but that didn't feel right to me either --
> > it's contrived in a similar way to using a one-off closure.
>
> Contrived how?
Meaning, the gather
On Fri, 2009-01-02 at 12:27 -0800, jerry gay wrote:
> oh, yes, whoops! i responded to someone else in #pugs earlier, and
> forgot to address the item here. C replaces p5's
> C (that's the latest idea from damian, although it seems not
> to be published yet).
Ah, I get it! What about perldoc's spe
On Thu, 2009-01-08 at 23:06 +0100, pugs-comm...@feather.perl6.nl wrote:
> +=item -0 *octal/hex*
> +
> +Sets input record separator. Missing due to lack of specification in
> +L. There is a comment about this in the L
> +section at the end of this document.
I use this option quite a bit -- but on
On Sun, 2009-01-11 at 12:39 -0500, Andrew Whitworth wrote:
> This is something that obviously needs to be avoided. PASM doesn't
> require that P42 be the 42nd register in an array. It only requires
> that values put into P42 aren't overwritten and the register isn't
> repurposed later. The simplest
On Mon, 2009-01-12 at 07:01 -0800, Ovid wrote:
> - Original Message
>
>
> > > > I could optionally make the following work:
> > > >
> > > > $string.trim(:leading<0>);
> > > > $string.trim(:trailing<0>);
>
> Alternatively, those could be ltrim() and rtrim(). If you need to
> dynamica
On Thu, 2009-01-15 at 16:03 -0800, Darren Duncan wrote:
> Patrick R. Michaud wrote (on p6c):
> > On Thu, Jan 15, 2009 at 08:53:33AM +0100, Moritz Lenz wrote:
> >> Another thing to keep in mind is that once we start to have a Perl 6
> >> prelude, we might decide to be nice neighbors and share it wit
On Wed, 2009-01-21 at 14:23 +, Peter Scott wrote:
> On Wed, 21 Jan 2009 13:35:50 +0100, Carl Mäsak wrote:
> > I'm trying to explain to myself why I don't like this idea at all. I'm
> > only partially successful. Other people seem to have no problem with it,
> > so I might just be wrong, or part
On Fri, 2009-01-30 at 08:12 +0100, pugs-comm...@feather.perl6.nl wrote:
> @@ -103,7 +106,7 @@
> =item *
>
> POD sections may be used reliably as multiline comments in Perl 6.
> -Unlike in Perl 5, POD syntax now requires that C<=begin comment>
> +Unlike in Perl 5, POD syntax now lets you use C<=
On Tue, 2009-02-17 at 22:38 +1100, Timothy S. Nelson wrote:
> My third thought is that it would be very useful also to have
> date/time objects that integrate well with eg. ctime, mtime, and the like;
> I'd
> start with Time::Piece as a model.
>
> http://search.cpan.org/dist/Time-Piece/Pi
On Thu, 2009-02-19 at 22:57 +1100, Timothy S. Nelson wrote:
> On Thu, 19 Feb 2009, Carl Mäsak wrote:
> > A tree is a graph without cycles.
That's insufficient. In fact, there are a number of ways that the
general concept of an acyclic graph must be constrained before you get
something you can cal
On Fri, 2009-02-20 at 15:33 -0600, Dave Rolsky wrote:
> Of course, if you're dealing with TAI only, you're safe for constants up
> to ONE_WEEK.
So we just define ONE_MONTH as 4 * ONE_WEEK, right?
*duck*
-'f
On Tue, 2009-02-24 at 12:31 -0800, Jon Lang wrote:
> $y ± 5 # same as ($y - 5) | ($y + 5)
> $y within 5 # same as ($y - 5) .. ($y + 5)
Oh, that's just beautiful.
-'f
> > Could you change to simply bounce with a
> > message:
> >
> > --
> > Please submit reports to Parrot using the web interface:
> >
> > https://trac.parrot.org/parrot/newticket
> >
> > Thanks,
> > The Parrot Team
> > --
> >
> > Thanks!
> > Allison
Out of curiosity, why don't we allow
On Sat, 2009-03-14 at 14:07 -0700, fREW Schmidt wrote:
> # New Ticket Created by fREW Schmidt
> # Please include the string: [perl #63874]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=63874 >
>
>
> , perl6
I'm al
On Mon, 2008-01-07 at 11:51 -0800, chromatic via RT wrote:
> On Monday 07 January 2008 08:18:24 Geoffrey Broadwell wrote:
> > It seems like this should be available from interpinfo in PIR ... and
> > since 'parrot -v' displays optimization information, it should probabl
Right now, Parrot's support for NCI callbacks (C code calling back into
PIR code) is relatively limited. In particular, there are at least the
following limitations:
1. The return type must be void (C library does not expect a response).
2. The callback must have exactly two arguments (from both
On Wed, 2008-01-16 at 22:38 -0700, Paul Seamons wrote:
> > I am starting to implement a GLUT and OpenGL binding for Parrot.
>
> I started down this path several months ago. The following is the thread on
> the topic.
>
> http://tinyurl.com/3crzpu
OK, read it now. I think I got a little farthe
On Sat, 2008-01-19 at 17:25 +1300, Allison Randal wrote:
> Geoffrey Broadwell wrote:
> > On Wed, 2008-01-16 at 22:38 -0700, Paul Seamons wrote:
> >>> I am starting to implement a GLUT and OpenGL binding for Parrot.
> [...]
> > I don't often get concentrated t
On Sat, 2008-01-19 at 16:12 -0600, Patrick R. Michaud wrote:
> On Fri, Jan 18, 2008 at 09:41:01PM -0800, Geoffrey Broadwell wrote:
> > "Null PMC access in invoke(); misspelled sub name in function call?"
>
> I fear this error message may actually send a beginner do
On Tue, 2008-02-12 at 21:36 -0500, Bob Rogers wrote:
> From: chromatic <[EMAIL PROTECTED]>
>Date: Tue, 12 Feb 2008 17:03:31 -0800
>
>On Tuesday 12 February 2008 16:55:06 Geoffrey Broadwell wrote:
>
>> Feh. Please someone tell me there is a ligh
On Tue, 2008-02-12 at 12:46 -0500, Bob Rogers wrote:
> From: Andrew Parker <[EMAIL PROTECTED]>
>Date: Tue, 12 Feb 2008 15:17:03 +0100
>
>Thanks for the pointer, Bob. I read through it and it might be
>tangentially related to this. That problem is about scopes being
>modeled b
On Wed, 2008-02-13 at 14:21 +, [EMAIL PROTECTED] wrote:
> >
> > On a more rational note, has any thought been given to what "good enough
> > performance for release" will be?
>
> Should we perhaps add a performance benchmark to the tests?
>
> Normalising it to account for hardware variations
On Thu, 2008-02-21 at 18:45 -0500, Joshua Gatcomb wrote:
> On Thu, Feb 21, 2008 at 4:23 PM, chromatic <[EMAIL PROTECTED]> wrote:
> 2. Allow people to choose where their money will go (if that's what they
> want to do)
Someone earlier in this thread mentioned that this can't be done
directly beca
Typo nit:
On Tue, 2008-02-26 at 09:42 -0800, [EMAIL PROTECTED] wrote:
> +file in the Standard Dialect (which itself has versions that correspond
> +to the same version of the official Perl test suite. Eval strings,
Appears to be missing a ')' before the '.'
-'f
On Tue, 2008-03-11 at 23:01 +0100, Ron Blaschke wrote:
> Andy Lester wrote:
> >
> > On Mar 11, 2008, at 2:43 PM, Ron Blaschke wrote:
> >
> >> It ties pointers to INTVALs, which I guess it shouldn't.
> >
> >
> > As I read the mail, it seems like the only problem we have is in casting
> > the po
>From the point of view of someone working through the PCT tutorial
(quite rockin', BTW!):
On Wed, 2008-03-26 at 14:25 +0100, Klaas-Jan Stol wrote:
> having used NQP a bit, I feel like I'm missing a few things. I'm not
> entirely sure what the fate of NQP is; will it always be a bootstrap
> stage
On Wed, 2008-03-26 at 09:31 -0700, Grafman wrote:
He lives! Just kidding, I know you've had actual paid work going
on. :-)
> Hi chromatic - as you know, I took over the Perl OpenGL project over a
> year ago - you had mentioned that I might consider doing a port to
> Parrot; Geoffrey had suggest
On Wed, 2008-03-26 at 16:27 -0700, Bob Free wrote:
> Cool - great to hear from you - sorry that it's been a while since I've
> posted an update!
Real life can be so darned intrusive ;-)
> It'd be great to have you participate - you've done quite a lot for POGL.
> Regarding your work/ideas
Imagine my delight upon reading this in the Perl 6 Design Team minutes:
* also had a contact from someone who wants to port OpenGL to Parrot
* not Geoff Broadwell
* seems like a very serious approach
Ouch! You wound me, sir!
Just for the record, I've attached my OpenGL/GLUT proof of concept
On Tue, 2008-04-01 at 16:19 -0700, [EMAIL PROTECTED] wrote:
> +The Unicode Standard defines a I (commonly simplified to
> just
> +I) as one or more characters forming a visible whole when displayed,
Typo ---^
-'f
On Wed, 2008-04-02 at 14:16 -0700, [EMAIL PROTECTED] wrote:
> =head3 Directives used for Parrot calling conventions.
>
> +{{ A bit of a radical idea, but now would be the time to decide on this:
> + Remove the whole "long-style" invocation syntax altogether.
> + Only allow the short version.
1 - 100 of 188 matches
Mail list logo
