Chromatic <[EMAIL PROTECTED]> wrote:
> int SDLCALL TTF_SizeText(TTF_Font *font, const char *text, int *w, int
> *h);
> *w and *h are out parameters.
> Per my reading of the NCI PDD and the code, this isn't yet supported.
Then the POD is missing some items:
,--[ src/call_list.txt ]
| # 2 - point
# New Ticket Created by chromatic
# Please include the string: [perl #29200]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=29200 >
I've just come across the following signature for which I want to write
NCI bindings:
/
On 4/26/2004 2:16 PM, Rod Adams wrote:
Larry Wall wrote:
In general it's probably a lousy idea to rely on #!/usr/bin/perl6 to
select language since you want the version number to select the
version of Parrot you're running, not the version of Perl.
One thing that occurred to me over the weekend i
> Okay, I've skimped on the explanations
> (I thought they were obvious, but that's
> just not true), so it's time to get things
> down.
w007, w00t. That is correct. :)
> (And yes, this means store_global
> will be relatively little-used)
Would a few operators like
'find_or_store_reference_glob
Okay, I've skimped on the explanations (I thought they were obvious,
but that';s just not true), so it's time to get things down.
Parrot's got two main variable 'types'--value and reference.
Value types are types that are directly referenced--types whose PMCs
actually represent themselves. When
> "Larry" == Larry Wall <[EMAIL PROTECTED]> writes:
Larry> It would be a (roughly) zero growth option to simply
Larry> switch to :x syntax for command-line switches instead of -x syntax.
Larry> Any program that uses colon switches instead of minus switches would
Larry> then automatically be
On Mon, 2004-04-26 at 08:12, Dan Sugalski wrote:
> At 9:34 PM -0400 4/25/04, Bryan C. Warnock wrote:
> >On Sun, 2004-04-25 at 16:34, Dan Sugalski wrote:
> >> Just a heads up, there are two things that have been pointed out.
> >>
> >> First, the transset op is transcharset. The abbreviation was a
On Mon, 26 Apr 2004 12:40:08 +0200, Ron Blaschke wrote:
> On Mon, 26 Apr 2004 11:48:22 +0200, Leopold Toetsch wrote:
>>> After, so I already got the interpreter.str file. I guess VC gets confused
>>> with the _CONST_STRING(i, __LINE__) thingy, where __LINE__ doesn't get
>>> expanded, and the whol
why not add a -6 perl flag:
perl -6 foo.pl
perl -6e 'print "yahoo\n"'
-corris
On Apr 26, 2004, at 11:09 AM, Juerd wrote:
Jonathan Scott Duff skribis 2004-04-26 13:02 (-0500):
I know this sounds slightly irrational but I don't like using shifted
characters to offset my command line switches. A
Larry Wall wrote:
In general it's probably a lousy idea to rely on #!/usr/bin/perl6 to
select language since you want the version number to select the
version of Parrot you're running, not the version of Perl.
One thing that occurred to me over the weekend is that we could fix all
the one-liners u
Jonathan Scott Duff skribis 2004-04-26 13:02 (-0500):
> I know this sounds slightly irrational but I don't like using shifted
> characters to offset my command line switches. Also, that colon seems
> *way* overloaded. :-) How about = instead?
Overloaded, but similar to :pairs and s:modifiers.
On Mon, Apr 26, 2004 at 10:44:57AM -0700, Larry Wall wrote:
> One thing that occurred to me over the weekend is that we could fix all
> the one-liners using a similar strategy to the package/module/class
> switch. It would be a (roughly) zero growth option to simply
> switch to :x syntax for comma
On Mon, Apr 26, 2004 at 06:48:56PM +0100, Simon Cozens wrote:
: [EMAIL PROTECTED] (Larry Wall) writes:
: > It would be a (roughly) zero growth option to simply
: > switch to :x syntax for command-line switches instead of -x syntax.
:
: And POSIX be damned!
And maybe we should rename POSIX to NEGI
[EMAIL PROTECTED] (Larry Wall) writes:
> It would be a (roughly) zero growth option to simply
> switch to :x syntax for command-line switches instead of -x syntax.
And POSIX be damned!
--
A person is smart. People are dumb, panicky dangerous animals and you know it.
- Agent J, Men in Black
On Thu, Apr 15, 2004 at 07:23:28PM +0200, Johan Vromans wrote:
: Ten years ago I was perfectly happy to start all my perl programs with
: /usr/bin/perl5. Today, I would be quite unhappy if I *still* needed to
: do it that way.
In general it's probably a lousy idea to rely on #!/usr/bin/perl6 to
se
On Fri, 2004-04-23 at 19:52, Damian Conway wrote:
> Aaron Sherman wrote:
> > Now, I know that the Apoc on modules has not been written, and by that
> > time Larry will have thought of this, but I thought I'd point out that
> > some mechanism will have to exist in modules to indicate not only that
On Sun, Apr 25, 2004 at 08:16:30PM -0700, Dave Whipp wrote:
> Abhijit A. Mahabal wrote:
>
> >>> *{"Foo::name1"} = -> $a { $a->{name1} };
> >>
> >>If I read A12 correctly, this could be written as:
> >>
> >> &Foo::$name1 := -> $a {$a.name1};
> >>
> >
> >
> >Could be; that sounds somewhat right, but
I am not sure if this message will make it to the list as I am posting it
using the www.perldiscuss.com interface. Cygwin has been failing to build
since at least the 21st. I suspect it has been since ICU went in. I
checked the tinderbox report but it is not listed.
FWIW - PLATFORMS is also inc
I am not happy about the versioning proposal.
While A12 listed many properties that could apply to a a module such as
version, subject, author etc, the versioning declaration
class Dog-1.2.1-cpan:JRANDOM;
leaves me a little cold.
Issues:
1) Why does this only use Version and Author? Supp
At 12:14 AM -0700 4/26/04, Jeff Clites wrote:
On Apr 25, 2004, at 11:59 PM, Luke Palmer wrote:
Jeff Clites writes:
I don't (right off) know of any other language which has something "in
between" variables and objects. That is, containers. They're feeling a
bit artificial.
Well... Perl 5.
Well, ther
At 9:34 PM -0400 4/25/04, Bryan C. Warnock wrote:
On Sun, 2004-04-25 at 16:34, Dan Sugalski wrote:
Just a heads up, there are two things that have been pointed out.
First, the transset op is transcharset. The abbreviation was a bit sloppy.
Second, in spots where "character" is used, substitute "
On Mon, 26 Apr 2004 11:48:22 +0200, Leopold Toetsch wrote:
>> After, so I already got the interpreter.str file. I guess VC gets confused
>> with the _CONST_STRING(i, __LINE__) thingy, where __LINE__ doesn't get
>> expanded, and the whole results in _CONST_STRING_ instead of
>> _CONST_STRING_1309,
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> After, so I already got the interpreter.str file. I guess VC gets confused
> with the _CONST_STRING(i, __LINE__) thingy, where __LINE__ doesn't get
> expanded, and the whole results in _CONST_STRING_ instead of
> _CONST_STRING_1309, etc.
> Now, here come
Leo,
I've been away from email for the weekend, so sorry for the delay.
Leopold Toetsch wrote:
Well C and C<$I13> or some such is the same for the compiler. Both
need a Parrot register allocation. If they aren't reused after this
instruction, there isn't any problem to put these into the same
regis
On Sun, 25 Apr 2004 22:37:44 +0200, Leopold Toetsch wrote:
>> Your problem seems to be related to the %.str: %.c inference rule, which
>> nmake doesn't understand. For nmake, this should read
>> .c.str:
>> $(PERL) build_tools\c2str.pl $< > $@
> That's already in CVS ;)
Great. :-)
>
>>
On Mon, 26 Apr 2004 08:46:05 +0100, Jonathan Worthington wrote:
>> Main Makefile contain line
>> .c.str: build_tools\c2str.pl
>>
>> But nmake do not understand this construction, only
>>
>> .c.str:
>> .
>>
> This is a problem I flagged up earlier, but I haven't had time to check
> leo's lat
On Sun, 2004-04-25 at 16:34, Dan Sugalski wrote:
> Just a heads up, there are two things that have been pointed out.
>
> First, the transset op is transcharset. The abbreviation was a bit sloppy.
>
> Second, in spots where "character" is used, substitute "grapheme", as
> I'm going to. Noting, of
"Nick Kostirya" <[EMAIL PROTECTED]> wrote:
>
> Main Makefile contain line
> .c.str: build_tools\c2str.pl
>
> But nmake do not understand this construction, only
>
> .c.str:
> .
>
This is a problem I flagged up earlier, but I haven't had time to check
leo's latest fix. Looking at that line,
Hello.
Main Makefile contain line
.c.str: build_tools\c2str.pl
But nmake do not understand this construction, only
.c.str:
.
Nick.
On Apr 25, 2004, at 11:59 PM, Luke Palmer wrote:
Jeff Clites writes:
I don't (right off) know of any other language which has something "in
between" variables and objects. That is, containers. They're feeling a
bit artificial.
Well... Perl 5.
Well, there's that. :)
But--how does that manifest itsel
Jeff Clites writes:
> I don't (right off) know of any other language which has something "in
> between" variables and objects. That is, containers. They're feeling a
> bit artificial.
Well... Perl 5.
Luke
31 matches
Mail list logo
