From: James Keenan (via RT) <[EMAIL PROTECTED]>
Date: Fri, 01 Jun 2007 16:46:06 -0700
Tonight, on both Linux and Darwin, I configured with the '--test' option to
Configure.pl that runs, among other things, the build tools tests once
Configure.pl itself has completed. These tests ge
On Jun 1, 2007, at 8:20 PM, Steve Peters wrote:
I can't see any need for such a macro other than for the minor
obfuscation
that it allows. For most of the Parrot code, I haven't SET_NULL()
used, and
I haven't used it myself. I'm a bit curious how much it is
actually used.
I know why we
On 6/1/07, Ruud H.G. van Tol <[EMAIL PROTECTED]> wrote:
John Macdonald schreef:
> "hash
> browned potatos" which is a hash of chopped potato, onion,
> and sometimetimes other things fried brown.
It's usually "hash browns" or "hashed browns", and I've always assumed
the former to be a shortened
On Jun 1, 2007, at 8:20 PM, Steve Peters wrote:
I can't see any need for such a macro other than for the minor
obfuscation
that it allows. For most of the Parrot code, I haven't SET_NULL()
used, and
I haven't used it myself. I'm a bit curious how much it is
actually used.
$ ack SET_N
On Fri, Jun 01, 2007 at 07:53:35PM -0500, Andy Lester wrote:
> From include/parrot/parrot.h:
>
> /* weird architectures might need this, s. C-FAQ 5.17
> *
> * the SET_NULL macros are only for system, where a NULL pointer
> * isn't represented by zeroes, so don't use these, for resetting
> * non-nu
Here's a bit of an explanation of why I const like I do:
http://xoa.petdance.com/Use_const_proactively
One of my jobs in Perl 5 and Parrot has been to apply const as much
as humanly possible.
== Const your local variables
The following is adapted from C++ Coding Standards by Herb Sutter and
On Friday 01 June 2007 16:51:18 Steve Peters wrote:
> The attached patch gets Parrot partially compiles with C++ (g++ actually).
> This work gets the compile going through the start of the imcc compiler.
Danger!
The patch to src/stm/waitlist.c causes segfaults in t/stm/runtime.t, test 3:
Progra
From include/parrot/parrot.h:
/* weird architectures might need this, s. C-FAQ 5.17
*
* the SET_NULL macros are only for system, where a NULL pointer
* isn't represented by zeroes, so don't use these, for resetting
* non-null pointers
*/
#ifdef HAS_NON_ZERO_NULL
# define SET_NULL(x) x = NULL
#
John Macdonald schreef:
> "hash
> browned potatos" which is a hash of chopped potato, onion,
> and sometimetimes other things fried brown.
That comes from the French haché, meaning chopped. Best with lots of
small pieces of beef in it as well.
--
Groet, Ruud
# New Ticket Created by Steve Peters
# Please include the string: [perl #43108]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43108 >
The attached patch gets Parrot partially compiles with C++ (g++ actually).
This work get
# New Ticket Created by James Keenan
# Please include the string: [perl #43107]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43107 >
---
osname= linux
osvers= 2.6.15
arch= i386-linux-thread-multi
cc= cc
---
Flags:
# New Ticket Created by "Mehmet Yavuz Selim Soyturk"
# Please include the string: [perl #43105]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43105 >
Function mmd_expand_y in src/mmd.c allocates new memory for the mmd
tabl
On Fri, Jun 01, 2007 at 01:04:48PM -0700, [EMAIL PROTECTED] wrote:
> Log:
> [Configure] Move the visibility hints into the GCC hints and enable it only
> for GCC 4.x and later. This makes it work other places than Linux and fixes
> the compilation for earlier GCC versions.
Works for me! :-)
T
On Friday 01 June 2007 13:39:32 Mehmet Yavuz Selim Soyturk wrote:
> Function mmd_expand_y in src/mmd.c allocates new memory for the mmd
> table, but does not initialize the newy allocated memory to NULL,
> which causes segfaults for some cases. The attached patch solves that
> problem.
I thought
Here's a bit of an explanation of why I const like I do:
http://xoa.petdance.com/Use_const_proactively
One of my jobs in Perl 5 and Parrot has been to apply const as much
as humanly possible.
== Const your local variables
The following is adapted from C++ Coding Standards by Herb Sutter and
# New Ticket Created by Mark Glines
# Please include the string: [perl #43102]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43102 >
While testing/trying to fix RT #42938, I noticed an additional test
failure in t/pmc/thre
On Jun 1, 2007, at 3:26 PM, chromatic wrote:
Log:
Add function attributes for noreturn to help GCC
Are those C89 attributes? Do they break other compilers?
They're stolen from p5, and they're macros that go away if you don't
define things like -DHASATTRIBUTE_NORETURN.
I'm all over the
From my wiki at http://xoa.petdance.com/Use_const_proactively
Const your local variables
The following is adapted from C++ Coding Standards by Herb Sutter and
Andrei Alexandrescu (with some C++-specific stuff removed):
const is your friend: Immutable values are easier to understand,
t
It seems to work in general, but in some cases (especially when I
allocate too much memory) it causes me a segfault
or an error like: Trace/breakpoint trap (core dumped)
It was caused by some unitialized memory in src/mmd.c. rt #43105 solves it.
--
Mehmet
On Friday 01 June 2007 13:21:52 [EMAIL PROTECTED] wrote:
> Log:
> Add function attributes for noreturn to help GCC
Are those C89 attributes? Do they break other compilers?
-- c
On 6/1/07, Doug McNutt <[EMAIL PROTECTED]> wrote:
At 09:15 -0700 6/1/07, Larry Wall wrote:
>: To conclude, as hash definitely tastes better than a dictionary, we
>: should stick to that name. ;)
>:
>: At least nobody can say that Perl is bad taste!
>
>Then maybe we should rename Array to Skewer o
Author: larry
Date: Fri Jun 1 12:44:27 2007
New Revision: 14412
Modified:
doc/trunk/design/syn/S06.pod
Log:
note that parsed/reparsed also influences whether trailing bracket is assumed
Modified: doc/trunk/design/syn/S06.pod
==
At 09:15 -0700 6/1/07, Larry Wall wrote:
>: To conclude, as hash definitely tastes better than a dictionary, we
>: should stick to that name. ;)
>:
>: At least nobody can say that Perl is bad taste!
>
>Then maybe we should rename Array to Skewer or Kabob or some such...
>
>Hmm, except it's hard to
I think this patch fixes the visibility problem with Linux and GCC versions
before 4.0. I think it also enables symbol hiding on other platforms with
GCC.
-- c
=== config/auto/gcc.pm
==
--- config/auto/gcc.pm (revision 3726)
+++ c
On Fri, Jun 01, 2007 at 06:52:37AM -0400, Mark J. Reed wrote:
: On 6/1/07, Larry Wall <[EMAIL PROTECTED]> wrote:
: >Nope. Hash is mostly about meaning, and very little about implementation.
: >Please don't assume that I name things according to Standard Names in
: >Computer Science. I name things
Hello,
I have two pmc classes PjsNumber and PjsBoolean, which define
bitwise_and like this:
PMC* bitwise_and(PMC* value, PMC* dest) {
FLOATVAL a, b;
if (! dest) {
dest = pmc_new(INTERP, dynpmc_PjsNumber);
} else if (dest->vtable->base_type != dynpmc_PjsNumber)
On Thursday 31 May 2007 18:01:55 James E Keenan wrote:
> > "Invoking the compiler on a simple source file, then checking that the
> > generated code exists seems such an obvious test that there must be a
> > fatal flaw in it. What am I missing?"
>
> This patch grew out of Hackathon Toronto and was
On Fri, Jun 01, 2007 at 06:05:58PM +0200, Thomas Wittek wrote:
: Daniel Hulme:
: >> Larry Wall:
: >>> I name things in English. Hash is just something that is disordered
: >
: >> I'm not a native english speaker, but I've never heard or read the word
: >> "hash" outside CS.
: >
: > you've never
Daniel Hulme:
>> Larry Wall:
>>> I name things in English. Hash is just something that is disordered
>
>> I'm not a native english speaker, but I've never heard or read the word
>> "hash" outside CS.
>
> you've never eaten "corned beef hash".
To conclude, as hash definitely tastes better than a
On Thu, 31 May 2007 23:09:54 -0700
Mark Glines <[EMAIL PROTECTED]> wrote:
> Might be worth it to prereserve 8 bytes or so, to avoid having to
> realloc as often, if this will be called a lot. Currently it just
> reallocs the minimum necessary to fit the existing string, the new
> character and a n
On Fri, Jun 01, 2007 at 10:30:08AM -0400, John Macdonald wrote:
> > "...make a hash of things" (meaning, a mess)
> > "corned beef hash"
>
> That's two people that have given the same list, but both
> have omitted the more common (in modern times) phrase "hash
> browned potatos" which is a hash of
On Fri, Jun 01, 2007 at 07:07:06AM -0400, Brandon S. Allbery KF8NH wrote:
>
> On Jun 1, 2007, at 5:44 , Thomas Wittek wrote:
>
> >Larry Wall:
> >>Nope. Hash is mostly about meaning, and very little about
> >>implementation.
> >>Please don't assume that I name things according to Standard Names
Let's not forget that the CS meaning of "hash" didn't spring forth
fully-formed from the skull of Donald Knuth or anything. A "hash
function" is so called because it "makes a hash of" the inputs. That
is, its output, while deterministic, is at first glance a random
rearrangement of the inputs. H
On Jun 1, 2007, at 5:44 , Thomas Wittek wrote:
Larry Wall:
Nope. Hash is mostly about meaning, and very little about
implementation.
Please don't assume that I name things according to Standard Names in
Computer Science. I name things in English. Hash is just something
that is disordered,
On 6/1/07, Larry Wall <[EMAIL PROTECTED]> wrote:
Nope. Hash is mostly about meaning, and very little about implementation.
Please don't assume that I name things according to Standard Names in
Computer Science. I name things in English.
Then why did we need a separate "use English" pragma? :)
On Fri, Jun 01, 2007 at 11:44:53AM +0200, Thomas Wittek wrote:
> Larry Wall:
> > Nope. Hash is mostly about meaning, and very little about implementation.
> > Please don't assume that I name things according to Standard Names in
> > Computer Science. I name things in English. Hash is just someth
Larry Wall:
> Nope. Hash is mostly about meaning, and very little about implementation.
> Please don't assume that I name things according to Standard Names in
> Computer Science. I name things in English. Hash is just something
> that is disordered, which describes the associative array interfa
37 matches
Mail list logo
