Michael G Schwern:
# On Sun, Mar 17, 2002 at 09:21:12PM -0800, Brent Dax wrote:
# > # Remember, I am not a C programmer. I just took my perl
# 5.6.1 that's
# > # compiled with 64 bit ints and ran Configure.pl with it.
# >
# > Okay. When Configure asks:
# >
# > How big would you like integers
On Sun, Mar 17, 2002 at 09:21:12PM -0800, Brent Dax wrote:
> # Remember, I am not a C programmer. I just took my perl 5.6.1 that's
> # compiled with 64 bit ints and ran Configure.pl with it.
>
> Okay. When Configure asks:
>
> How big would you like integers to be? [long long]
>
> just t
>as you add 2 boolean fields, then you lose.
Where is my grammar cap?
As soon as you add 1 boolean you lose.
+2 would put you back to where you started.
-Melvin
At 11:15 PM 3/17/2002 -0500, Bryan C. Warnock wrote:
>On Friday 08 March 2002 23:02, Melvin Smith wrote:
> > I vote for non-enforcement of this one.
>
>Er, did you mean "removal"? Having rules that aren't enforced is
>counter-productive in the long run.
No, I meant, I want a special "get out of
Bryan C. Warnock:
# On Sunday 17 March 2002 00:23, Melvin Smith wrote:
# > Makes ok, alignment warnings. Tests run ok. Most warnings are
# > from -Wpadded. I was able to eliminate 1 or 2 by rearranging
# > members in structs, but some are due to unions of different size
# > types.
# >
# > We can e
At 10:29 PM 3/17/2002 -0500, Bryan C. Warnock wrote:
> > Ditching BOOLVAL in favor of UINTVAL might fix a couple as well.
>
>Until we want to add another one. In either case, UINTVAL is the wrong
>type. We'd want the natural word size, which I haven't figured out (beyond
>benchmarking) how to te
Michael G Schwern:
# On Sun, Mar 17, 2002 at 12:50:57PM -0800, Hong Zhang wrote:
# >
# > It looks like you are running in 32-bit environment, but
# > using 64-bit INTVAL. The INTVAL must be the same size as
# > void* in order to cast between them without warning.
# > Please try to reconfig using 3
On Friday 08 March 2002 23:02, Melvin Smith wrote:
> Just my 2 cents.
>
> This is my only nitpick with the coding standards.
>
> I never cared for the style of putting return type on a
> separate line above the function declaration header.
>
> I like it just as the prototype.
>
> I vote for no
On Sunday 10 March 2002 01:32, Melvin Smith wrote:
> I think it would be useful to add an init method for PMCs which takes
> a size argument constructor since there will be times when
> a language implementor wants to created a sized type.
>
> Right now init takes no arguments.
>
> It will defin
On Monday 11 March 2002 20:24, Alex Gough wrote:
> On Mon, 11 Mar 2002, Simon Glover wrote:
>
> >
> > For more fun in the same vein, try this:
> >
> > length S0
> > end
> >
> > In both cases the problem is that we're not checking the STRING*
> > pointer passed to the function before we sta
On Tuesday 12 March 2002 12:06, Melvin Smith wrote:
> Just my 2 pesos.
>
> When CPUs are 10% faster, would this little optimization matter?
Well, yes, since the optimization will then be 10% faster, too. ;-)
>
> A typical CPU traps invalid derefs by segfaulting the process,
> but the CPU itse
On Saturday 16 March 2002 07:48, Simon Cozens wrote:
> 645 return_me = *foo;
On a separate note, metasyntactic variable names aren't the best choice in
actual code.
--
Bryan C. Warnock
[EMAIL PROTECTED]
On Saturday 16 March 2002 12:03, Dan Sugalski wrote:
> And make immortal Buffers and PMCs. It's a nasty hack, but it solves
> the "what happens if I allocate a bunch of PMCs and the DOD collects
> them before I can use them" problem.
>
> Now'd be a good time to object if you've a better option.
On Saturday 16 March 2002 13:24, Michael G Schwern wrote:
> This is parrot built using a 5.6.1 with 64 bit integers. The tests
> pass ok, but there's a heap of warnings in the build. Here's the
> complete make output.
Known problem. We currently suck at most things not long or double.
My stomp
On Sunday 17 March 2002 00:23, Melvin Smith wrote:
> Makes ok, alignment warnings. Tests run ok. Most warnings are
> from -Wpadded. I was able to eliminate 1 or 2 by rearranging
> members in structs, but some are due to unions of different size
> types.
>
> We can either turn off -Wpadded or manu
On Sun, Mar 17, 2002 at 05:06:35PM -0800, Brent Dax wrote:
> # Checking some things by compiling and running another small C
> # program (this
> # could take a while):
> #
> # Building ./testparrotsizes.cfrom testparrotsizes_c.in...
> #
> #
> # #include "parrot/parrot.h"
> # #include
Michael G Schwern:
# On Sun, Mar 17, 2002 at 10:13:58AM -0800, Brent Dax wrote:
# > Lines in question:
# >
# >
# > foreach(grep {/^i_/} keys %Config) {
# > $c{$_}=$Config{$_};
# > $c{headers}.=defineifdef((/^i_(.*)$/));
# > }
# >
# > I think VMS is too lame to handle the grep line. Honest
On Sat, Mar 16, 2002 at 04:34:34PM -0500, Dan Sugalski wrote:
> Now's your time to speak up, please.
Ok, you asked for it. I just committed the regular expression
compiler. It has known bugs, but I am completely out of tuits for now,
and have been since about the time I announced this thing's exi
This is off a clean rsync of parrot-HEAD
The build is almost completely clean, with only the following errors.
packfile.c: In function `PackFile_check_segment_size':
packfile.c:129: warning: long int format, int arg (arg 5)
encodings/singlebyte.c: In function `singlebyte_skip_forward':
encodings
>personal dislike for VMS. I don't know enough about VMS to form an
>opinion on it--its popular days were before my time. ;^)
I never cared for the VMS command shell (I think it was DCL, been a few
years since I worked on it), but there is a lot to be learned
from the VMS architecture itself.
On Sun, Mar 17, 2002 at 12:50:57PM -0800, Hong Zhang wrote:
>
> It looks like you are running in 32-bit environment, but
> using 64-bit INTVAL. The INTVAL must be the same size as
> void* in order to cast between them without warning.
> Please try to reconfig using 32-bit INTVAL, or running
> pro
On Sun, Mar 17, 2002 at 10:16:13AM -0800, Brent Dax wrote:
> Michael G Schwern:
> # On Sat, Mar 16, 2002 at 02:36:45PM -0800, Hong Zhang wrote:
> # >
> # > Can you check what is the sizeof(INTVAL) and sizeof(void*)?
> # > Some warnings should not have happened.
> #
> # (Note: Not a C programmer)
>
On Sun, Mar 17, 2002 at 10:13:58AM -0800, Brent Dax wrote:
> Lines in question:
>
>
> foreach(grep {/^i_/} keys %Config) {
> $c{$_}=$Config{$_};
> $c{headers}.=defineifdef((/^i_(.*)$/));
> }
>
> I think VMS is too lame to handle the grep line. Honestly, I'd rather
> not change it to bo
It looks like you are running in 32-bit environment, but
using 64-bit INTVAL. The INTVAL must be the same size as
void* in order to cast between them without warning.
Please try to reconfig using 32-bit INTVAL, or running
process in 64-bit mode.
Hong
> -Original Message-
> From: Michael
At 11:52 AM -0800 3/17/02, Brent Dax wrote:
>Dan Sugalski:
># At 10:13 AM -0800 3/17/02, Brent Dax wrote:
># ># Probing Perl 5's configuration to determine which headers you
># ># have (this could
># ># take a while on slow machines)...
># ># Out of memory!
># ># %SYSTEM-F-ABORT, abort
># >
># >Li
I suspect that it's not that VMS can't handle it- it's more likely that
VMS does a better job of placing quotas on memory usage than other OSes.
There's probably something analogous to "ulimit" which would fix the
issue, but requiring that in order to build parrot isn't really reasonable.
If w
Dan Sugalski:
# At 10:13 AM -0800 3/17/02, Brent Dax wrote:
# ># Probing Perl 5's configuration to determine which headers you
# ># have (this could
# ># take a while on slow machines)...
# ># Out of memory!
# ># %SYSTEM-F-ABORT, abort
# >
# >Lines in question:
# >
# >
# >foreach(grep {/^i_/} keys
At 10:13 AM -0800 3/17/02, Brent Dax wrote:
># Probing Perl 5's configuration to determine which headers you
># have (this could
># take a while on slow machines)...
># Out of memory!
># %SYSTEM-F-ABORT, abort
>
>Lines in question:
>
>
>foreach(grep {/^i_/} keys %Config) {
> $c{$_}=$Config{$_}
Michael G Schwern:
# On Sat, Mar 16, 2002 at 02:36:45PM -0800, Hong Zhang wrote:
# >
# > Can you check what is the sizeof(INTVAL) and sizeof(void*)?
# > Some warnings should not have happened.
#
# (Note: Not a C programmer)
#
# INTVAL? I can't find where its defined.
INTVAL is in config.h. Make
Michael G Schwern:
# Using 5.005_03 on OpenVMS 7.3...
#
#
# Determining if your C compiler is actually gcc (this could
# take a while):
#
#
# Your C compiler is not gcc.
#
#
# Probing Perl 5's configuration to determine which headers you
# have (this could
# take a while on slow machines)...
# Out
At 7:34 PM -0500 3/16/02, Melvin Smith wrote:
>At 04:34 PM 3/16/2002 -0500, Dan Sugalski wrote:
>>Now's your time to speak up, please.
>
>Well I was about to try to add simple regexes to my
>little language before checking in the first version.
>
>I think one of the reasons noone is using them is
I came across Simon Cozens email
(http:[EMAIL PROTECTED]/msg08641.html) again
tonight and it got me thinking...
In Perl 6 are modules compiled down to pbc (Perl byte code) going to also
create metadata similar to what .NET has describing methods, use, etc.
I don't think it would be that dificult
32 matches
Mail list logo
