Author: chip
Date: Tue Sep 5 10:42:07 2006
New Revision: 14416
Added:
trunk/docs/pdds/pdd07_codingstd.pod (contents, props changed)
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
Move pdd07 out of clip
Added: trunk/docs/pdds/pdd07_codingstd.pod
Author: chip
Date: Tue Sep 5 10:42:52 2006
New Revision: 14419
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
About 25% done with update of pdd07.
Modified: trunk/docs/pdds/pdd07_codingstd.pod
Author: chip
Date: Tue Sep 5 15:00:42 2006
New Revision: 14432
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
Move pdd07 out of clip
Modified: trunk/docs/pdds/pdd07_codingstd.pod
Author: chip
Date: Tue Sep 5 15:01:18 2006
New Revision: 14435
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
About 25% done with update of pdd07.
Modified: trunk/docs/pdds/pdd07_codingstd.pod
Author: chip
Date: Tue Sep 5 15:01:35 2006
New Revision: 14436
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Changes in other areas also in this revision:
Added:
trunk/editor/parrot.el (contents, props changed)
Modified:
trunk/ (props changed)
trunk/editor/README.pod
Log
Author: chip
Date: Wed Sep 6 15:57:05 2006
New Revision: 14452
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
Move pdd07 out of clip
Modified: trunk/docs/pdds/pdd07_codingstd.pod
==
Author: chip
Date: Wed Sep 6 15:57:18 2006
New Revision: 14453
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
Modified: trunk/docs/pdds/pdd07_codingstd.pod
==
Author: chip
Date: Wed Sep 6 15:57:40 2006
New Revision: 14454
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
Modified: trunk/docs/pdds/pdd07_codingstd.pod
==
Author: chip
Date: Wed Sep 6 15:57:46 2006
New Revision: 14455
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
About 25% done with update of pdd07.
Modified: trunk/docs/pdds/pdd07_codingstd.pod
==
Author: chip
Date: Tue Oct 3 12:36:36 2006
New Revision: 14840
Removed:
trunk/docs/pdds/clip/pdd07_codingstd.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
Remove redundant pdd07 (closes: #40419)
Author: chip
Date: Fri Nov 10 11:12:20 2006
New Revision: 15330
Modified:
trunk/docs/pdds/pdd03_calling_conventions.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
trunk/compilers/imcc/imcc.l
trunk/compilers/imcc/imcc.y
trunk/compilers/imcc
Author: chip
Date: Tue Nov 14 09:40:26 2006
New Revision: 15527
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
Incremental improvement to pdd07 "coding standards":
* Prefer "char
Author: chip
Date: Mon Mar 13 15:41:32 2006
New Revision: 11894
Modified:
trunk/docs/pdds/pdd03_calling_conventions.pod
Log:
Undeprecate the MAYBE_FLAT bit, which (contrary to my mistaken memory) is
not unused, but is in fact very often used for Perl 6.
New features: (1) When a hash value is
Author: chip
Date: Sun Apr 16 20:33:54 2006
New Revision: 12283
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Log:
* Added requirement that ."load_library"() throw an exception on
failure. Also noted that the exception is only covering for the lack of a
universal error PM
Author: chip
Date: Sun Apr 16 21:21:53 2006
New Revision: 12284
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Log:
* Documented clearly & consistently that all namespace opcodes start their
search in the HLL root namespace, *not* at the global root.
* Added a second namespace metho
Author: chip
Date: Mon Apr 17 08:35:24 2006
New Revision: 12289
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Log:
Rename name() method to get_name() for consistency and
to allow for eventual possibility of set_name().
Modified: trunk/docs/pdds/pdd21_namespaces.pod
Author: chip
Date: Tue May 16 13:27:30 2006
New Revision: 12706
Modified:
trunk/docs/pdds/clip/pdd02_vtables.pod
trunk/docs/pdds/clip/pdd15_objects.pod
Changes in other areas also in this revision:
Modified:
trunk/docs/ROADMAP.pod
trunk/docs/vtables.pod
trunk/src/ops/ops.num
Author: chip
Date: Tue May 23 11:06:17 2006
New Revision: 12774
Modified:
trunk/docs/pdds/clip/pdd23_exceptions.pod
Log:
Half-done. The new opcodes and directives are certain,
and can be the basis of implementation work immediately.
Modified: trunk/docs/pdds/clip/pdd23_exceptions.pod
Author: chip
Date: Fri Jun 30 13:10:33 2006
New Revision: 13070
Modified:
trunk/docs/pdds/clip/pdd23_exceptions.pod
Log:
Overhaul.
Take _that_, Coke!
Modified: trunk/docs/pdds/clip/pdd23_exceptions.pod
==
--- trunk
Author: chip
Date: Fri Jun 30 13:12:26 2006
New Revision: 13071
Added:
trunk/docs/pdds/pdd23_exceptions.pod
- copied unchanged from r13070, /trunk/docs/pdds/clip/pdd23_exceptions.pod
Removed:
trunk/docs/pdds/clip/pdd23_exceptions.pod
Log:
Rename pdd23 into docs/pdds.
Author: chip
Date: Sat Jul 1 11:26:02 2006
New Revision: 13092
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
* Exception handlers are now closures (or just plain subroutines),
not continuations.
* Eliminate the C opcode, as the handler returning is enough
of a clue that the next
Author: chip
Date: Sat Jul 1 11:26:44 2006
New Revision: 13093
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
oops, restore namespace on exception class in example code
Modified: trunk/docs/pdds/pdd23_exceptions.pod
Author: chip
Date: Sat Jul 1 11:30:02 2006
New Revision: 13094
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
rename 'caught' opcode to 'handled' for obscure reasons
Modified: trunk/docs/pdds/
Author: chip
Date: Sat Jul 1 12:27:31 2006
New Revision: 13097
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Log:
Consistently describe namespace identifiers accepted by namespace opcodes as
either key constants or string arrays, since both of those work in all cases
(or should
Author: chip
Date: Sat Jul 1 13:00:41 2006
New Revision: 13098
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Log:
Specify new compiler methods, compiler.'parse_name'(), which allows parsing
foreign language names using the foreign language's rules. (per Allison)
Author: chip
Date: Wed Jul 5 17:31:15 2006
New Revision: 13170
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Changes in other areas also in this revision:
Modified:
trunk/include/parrot/global.h
trunk/include/parrot/hll.h
trunk/src/builtin.c
trunk/src/global.c
trunk/src
Author: chip
Date: Thu Jul 6 13:05:47 2006
New Revision: 13183
Modified:
trunk/docs/pdds/pdd00_pdd.pod
Changes in other areas also in this revision:
Modified:
trunk/README
trunk/README.win32.pod
trunk/RELEASE_INSTRUCTIONS
trunk/compilers/imcc/README
trunk/docs/debug.pod
scratchpad and not have to search outward at
>runtime.
Once you start down that path, forever will it dominate your closure
implementation. I suggest you do lexical scopes right from the start.
Surely they're not that much harder than a trampoline Are they?
PS: I'm back.
t NUM, in NUM) {
+ $1 = 1.0 - cos($2);
goto NEXT();
}
--
Chip Salzenberg - a.k.a. -<[EMAIL PROTECTED]>
"It furthers one to have somewhere to go."
While editing *.pmc, I'm inclined to make various style details
consistent. But I don't know whose style rules rule in *.pmc.
If necessary, I'll be glad to create a pmc style guide.
--
Chip Salzenberg - a.k.a. -<[EMAIL PROTECTED]>
"It further
. If somebody else wants to take over this
> I'd only be too happy [...]
I'll be glad to. Lots of the PMC subsystems looks Topaz-like to me.
That's almost certainly a case of convergent evolution rather than
derivation, but in any case, the PMCs look really interesti
ting work that I can do over the net in between classes
(hint, hint :-)).
--
Chip Salzenberg - a.k.a. -<[EMAIL PROTECTED]>
"It furthers one to have somewhere to go."
uch all of it has been lifted, in one
> form or other, from folks with a lot more experience and talent than
> I have. I just file down the edges and add some putty to make things
> fit together right)
Originality is the art of concealing one's sources.
--
Chip Salzenberg
ow multiple :load routines.
That's a bug, Shirley.
> What we're looking for is more of a Parrot version of .par/.jar/.pkg:
> bundle up all the files you need for a particular application into a
> single file. Not a PBC, but some form of "archive" or "package" format.
I don't see any harm in .zip and .tar and [archive method of choice]
plugins.
--
Chip Salzenberg <[EMAIL PROTECTED]>
y
accessing our source code repository. Instructions for doing this are at
<http://www.parrotcode.org/source.html>.
I'd like to thank all our contributors for making this possible, and our
sponsors for supporting this project.
Share & Enjoy!
Chip Salzenberg <[EMAIL PROTECTED]>
If you have MS Project 98 or Project 2000 installed, and can load-and-save a
project file for me, please mail me. adTHANSKvance
--
Chip Salzenberg <[EMAIL PROTECTED]>
elop on Parrot (or help develop Parrot itself), we
strongly recommend that you keep up with the latest and best Parrot code by
accessing our source code repository. Instructions for doing this are at
<http://www.parrotcode.org/source.html>.
I'd like to thank all our contributors for making this possible, and our
sponsors for supporting this project.
Share & Enjoy!
Chip Salzenberg <[EMAIL PROTECTED]>
nterp"
-void pt_thread_prepare_for_run(Parrot_Interp d, Parrot_Interp s);
+void pt_thread_prepare_for_run(Parrot_Interp d, const Parrot_Interp s);
What's the purpose of this? It doesn't protect *s from changes. [time
passes] I now see that some of the existing functions already have this
construct. Perhaps you were just imitating them?
--
Chip Salzenberg <[EMAIL PROTECTED]>
HER NAMING THING
* Please rename 'ro_variant' to something ending in '_vtable',
e.g. 'ro_variant_vtable', to make clear that it's not a class pointer
or type number.
--
Chip Salzenberg <[EMAIL PROTECTED]>
On Thu, Aug 10, 2006 at 07:11:15PM -1000, Joshua Hoblitt wrote:
> On Thu, Aug 10, 2006 at 07:19:21PM -0700, Chip Salzenberg wrote:
> > * useless curlies
> >OTGH, the project needs automated filters for more coding standards,
> >including one that that notes (and
ment.[*] If people kept talking about it, and if I kept
trying to persuade them, back & forth... then, it'd be an argument.
[*] It's abuse. Arguments are down the hall.
--
Chip Salzenberg <[EMAIL PROTECTED]>
On Fri, Aug 11, 2006 at 04:38:59PM -0400, Charles Reiss wrote:
> On 8/10/06, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> > /* XXX is it okay to combine flatten/slurpy into one flag? */
> >
> > The answer is "No": "flat" is an output flag, &qu
.
> The hard part of doing it correctly is handling inheritance.
It's an interface guarantee, and as such I think it's OK that it can't be
overridden in a derived class. Agree?
> >A bigger issue for automatic read-only variant generation is that MMD
> >methods curren
So, given the below, looks like we've got everything sewn up and the
long-awaited day of the STM merge is upon us.
Charles, care to do the honors?
On Tue, Aug 15, 2006 at 06:31:38PM -0400, Charles Reiss wrote:
> On 8/15/06, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> >On Sat
On Thu, Aug 17, 2006 at 12:13:30PM -0700, Leopold Toetsch via RT wrote:
> Am Donnerstag, 17. August 2006 08:24 schrieb Chip Salzenberg:
> > The None class serves no useful (portable) purpose and it should be
> > removed, especially from the public interface of Hash.
>
> I&#
$P0 = new .Undef
...
$P1 = default hsh['key1'], $P0
$P1 = default hsh['key2'], $P0
...
It would work without the lookups too:
$S0 = default $S0, ''# if $S0 is null, assign it ''
what say?
--
Chip Salzenberg <[EMAIL PROTECTED]>
direct way
to indicate an error when the output type has no out-of-band values, like
INTVAL. And exceptions are still too expensive. So at present I'd consider
this a misbug.
--
Chip Salzenberg <[EMAIL PROTECTED]>
{ not replying to the ticket }
On Fri, Aug 18, 2006 at 01:10:07AM +0200, Leopold Toetsch wrote:
> Am Donnerstag, 17. August 2006 08:24 schrieb Chip Salzenberg:
> > The None class serves no useful (portable) purpose and it should be
> > removed, especially from the public in
et was
right. Besides, it's not like they aren't a renewable resource. :-)
--
Chip Salzenberg <[EMAIL PROTECTED]>
, this is NOT a style preference question. The only reason I'm bugging
the list with this question is to solicit stories of "80 columns are the max
supported by ". adTHANKSvance
--
Chip Salzenberg <[EMAIL PROTECTED]>
ible, and
> delete the tests that don't matter anymore.
I'm Chip Salzenberg, and I approve of this message.
> I've just checked in a CAGE task for this.
Thanks.
--
Chip Salzenberg <[EMAIL PROTECTED]>
Some selectivity is in order, or we'll have to target 1989 memory sizes,
disk capacities, and network bandwidth
PS: Allison gets to specify the doc formatting, if she likes. Exceptions
are technically trivial. See the bottom of the pdds for how a given file
can override the default word wrap column.
--
Chip Salzenberg <[EMAIL PROTECTED]>
you. My school's punch card machines were in the same room
as the TRS-80 Model I ("THE COMPUTER ROOM"). These kids today with their
hula hoops and fax machines and intarwebs...
--
Chip Salzenberg <[EMAIL PROTECTED]>
On Mon, Aug 21, 2006 at 06:05:08PM -0400, Mr. Shawn H. Corey wrote:
> Don't forget that some programs, like mailers, wrap at 80 characters.
I don't know of any mailer that is hard-coded at any given column width.
Do you?
--
Chip Salzenberg <[EMAIL PROTECTED]>
METHOD becomes redundant.
--
Chip Salzenberg <[EMAIL PROTECTED]>
rhaps I should
let that go unmentiond. Oops, too late. ("Bitter? Oh, a *tad*.")
> I do think pulling too hard at this thread might require a closer look at
> what's current in src/pmc/ vs. src/*.c vs src/ops/ (where's there's
> smoke...): a lot of the current state
It seems that I've managed to confuse svk again, as it continues to
re-commit old log messages with no content.
--
Chip Salzenberg <[EMAIL PROTECTED]>
On Fri, Nov 10, 2006 at 10:51:14PM -0500, Bob Rogers wrote:
>From: [EMAIL PROTECTED]
>Date: Fri, 10 Nov 2006 11:12:21 -0800 (PST)
>
>Author: chip
>Date: Fri Nov 10 11:12:20 2006
>New Revision: 15330
>
>. . .
>
>Log:
>Remove the
work in your initializations, work that
may be entirely pointless if the given function takes an early return for
some reason.
--
Chip Salzenberg <[EMAIL PROTECTED]>
this is the preferred format:
if (foo)
bar();
else
baz();
--
Chip Salzenberg <[EMAIL PROTECTED]>
On Tue, Oct 17, 2006 at 11:41:06PM +0200, Leopold Toetsch wrote:
> Anything that has the smallest smell of ever needing an extra statement after
> if or else shall use braces in the first place (IMHO).
Predicting the future is something humans are bad at, sadly.
--
Chip Salzenberg &
space refinements
+ Coroutine improvements
+ An impressive swarm of other bugfixes and enhancements
--
Chip Salzenberg <[EMAIL PROTECTED]>
g
Subversion or SVK to access our source code repository; see instructions at
http://www.parrotcode.org/source.html .
Thanks to all our contributors for making this possible, and our sponsors
for supporting this project.
Share & Enjoy!
--
Chip Salzenberg <[EMAIL PROTECTED]>
(Customized PMCs can of course respond with anything they like.)
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
>if (dest && *dest)
> res = *dest;
> else if (!s1 || !s2)
> res = string_make(interpreter, NULL, 0, NULL, 0, NULL);
What in $DEITY's name is *that*? It sure isn't a context diff.
A context diff is what you get from "diff -u" or "diff -c
erl too? Because Perl already has this.
Funny how we don't get complaints.
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
Shimmer in distance:
Floor wax *and* dessert topping!
Shine will be tasty.
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to
X in string
>*) find first character not of class X in string
>*) find boundary between X and not-X
>*) Find boundary defined by arbitrary code (mainly for word breaks)
Also, I imagine you'll want a backwards/forwards option on some of
them, to support the p6 equivalent of /a.*b/.
--
Chip Sa
According to Dan Sugalski:
> At 2:44 PM + 9/3/04, Chip Salzenberg wrote:
> >According to [EMAIL PROTECTED] (Dan Sugalski):
> >>*) extract substring
> >
> >Rather than that, wouldn't you prefer to make "substring of target
> >string" the act
ary for efficient regex work with minimal copying.
[*] Unless it's a _feature_ that given tied $a,
($a = "aaa") =~ s/a/b/g
would call STORE four times ("aaa", "baa", "bba", "bbb").
--
Chip Salzenberg - a.k.a. -<[EMAIL PROTECTED]>
"Persistence in one opinion has never been considered
a merit in political leaders." --Marcus Tullius Cicero
vant for this oddity:
($a = "aaa") =~ s{a}
{ $x++ ? substr($a,0,1) : 'b' }e;
Now, should that produce "bbb" or "baa"? I favor "baa", because I
think minimal stores are too important to compromise them just for
this bizarre use case.
--
Chip Salzen
o build a config file by hand. IMO. And yes, I *have*
done cross-compilation myself.
--
Chip Salzenberg - a.k.a. -<[EMAIL PROTECTED]>
"Persistence in one opinion has never been considered
a merit in political leaders." --Marcus Tullius Cicero
e captain can be wrong, but the
captain cannot be indecisive.
PS: Splunge.
--
Chip Salzenberg - a.k.a. -<[EMAIL PROTECTED]>
"Persistence in one opinion has never been considered
a merit in political leaders." --Marcus Tullius Cicero
mization modes where a single substitution like
> $genome ~~ s/TTAGGG//
> can be done "mostly in place".
Indeed, I had that in mind when I designed Topaz's "open the hood"
feature for string Scalars, which I mentioned earlier as a possible
model for optimizing
readlink() is exactly the kind of thing that must
be probed for.
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]>
"I don't really think it is a question of bright people and dumb
people, but rather people who can see the game they're playing and
those who can't." -- Joe Cosby
According to Dan Sugalski:
> I'm fine with mashing functions and variables into a single big mass...
Me too (FWIW). And I think it'll work.
PS: I've got the Glob Stick where I can reach it.
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]>
where it's up to the language implementor to design a name
mangling scheme, has the advantage of being known to work.
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]>
"I don't really think it is a question of bright people and dumb
people, but rather peop
According to Jeff Clites:
> But it's nice to have stuff that a compiler can optimize away in a
> standard run, and maybe leave in place when running/compiling a
> debug version [...]
my $i is register;
I See A Great Need.
--
Chip Salzenberg - a.k.a. -
methods are on their own, which is OK with me.
So, given this sub and tied $*var:
sub getvar { my $i = rand; $*var }
the FETCH method implementing $*var might not be able to see $i?
Which implies that there may be no pad and $i could be in a register?
--
Chip Salzenberg
According to Dan Sugalski:
> At 12:25 PM -0400 9/25/04, Chip Salzenberg wrote:
> > my $i is register;
>
> Except that makes things significantly sub-optimal in the face of
> continuations, since registers aren't preserved...
Well, I know I'd be willing to put in a f
xample. Don't you mean:
variables => { '$Foo' => },
i.e. with the '$' in the key?
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]>
"I don't really think it is a question of bright people and dumb
people, but rather people who can see the game they're playing and
those who can't." -- Joe Cosby
d categories, thus
avoiding lots of anticipated string tricks.
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]>
"I don't really think it is a question of bright people and dumb
people, but rather people who can see the game they're playing and
those who can't." -- Joe Cosby
According to Dan Sugalski:
> At 11:58 AM -0700 9/28/04, Jeff Clites wrote:
> >On Sep 28, 2004, at 11:26 AM, Chip Salzenberg wrote:
> >
> >>According to Jeff Clites:
> >>>top-level namespace (say this is namespace #1):
> >>>{
> >>
some method on this object. I won't tell you which method to
call. Just pick one. Guess if you have to."
Ruby apparently has a unified namespace. Perl doesn't have one of
those. Pretending it does is just closing your eyes and humming.
--
Chip Salzenberg - a.k.a. -
d the second half of the message you'd know
> that that's what I meant.
I read all of it. I know what you mean. What you are not realizing is
that the "appearance" of a unified namespace *is* a unified namespace.
A Perl runtime won't have the necessary information to
According to TOGoS:
> Chip said:
> > A Perl runtime won't have the necessary information
> > to present [a unified namespace].
>
> I'm not so sure about that. Most of the time, only one variable with
> a name will be defined ($foo, @foo, or &foo, but n
s is somewhat different; it's mapping a C#
language feature (for the CLR wouldn't have had this feature if C#
didn't need it) onto a language that lacks it.
On an even less related note, I'm really quite surprised that J#
doesn't use the bean method names. Or maybe
According to Chip Salzenberg:
> According to TOGoS:
> > Or explicit exports :) that way you only need to define the
> > interface once, and then all unified-namespace languages can use it.
>
> Asking Perl programmers to go out of their way to present foreign and
> unnat
According to Brent 'Dax' Royal-Gordon:
> Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> >parrot_alias(a, 'b', # dest: Python is unified, no need for a
> > category here
> > a, 'b', 'scalar') # src
According to Dan Sugalski:
> As such, I'd like to say a big thanks to Chip Salzenburg who's agreed
> to take the hat.
I thank you for your kind words, and for giving me the opportunity
again to work long hours and explain difficult and arbitrary design
decisions to enthusias
It seems to me that the most productive things to worry about, from a
design point of view, are the things that interest the hubristic
and/or impatient people.
Therefore, in the spirit of the Hindmost: If you're out ahead of me,
who are you and what are you doing?
--
Chip Salze
According to Chip Salzenberg:
> Therefore, in the spirit of the Hindmost: If you're out ahead of me,
> who are you and what are you doing?
It's been suggested to me on IRC that my previous message was a bit
opaque. Let me try again:
What design issues are crying for attention ri
The SET_NON_ZERO_NULL macro is silly. On any arch where null pointers
are not represented as all zeroes, the null pointer value is still
*spelled* "0" in source code. C always works, for all
values of FOO and all architectures.
If I'm missing something, please speak up.
--
or 0.0 other than all bits zero? :-)
I think so. While POSIX may specify IEEE floating point, I doubt that
ANSI does. :-,
--
Chip Salzenberg- a.k.a. -<[EMAIL PROTECTED]>
Open Source is not an excuse to write fun code
then leave the actual work to others.
Greatly
Missing The Point.
On the gripping hand, if you'd like to experiment with putting IMCC
into libparrot, bison's "-p prefix" option seems relevant: "Rename the
external symbols used in the parser so that they start with prefix
instead of yy." Maybe "-p Parrot_imcc_"?
[*] Is there already a version number policy sketched out?
--
Chip Salzenberg- a.k.a. -<[EMAIL PROTECTED]>
Open Source is not an excuse to write fun code
then leave the actual work to others.
sing. How is Perl 6 supposed to implement its
idea of %MY:: if there's no lexical scoping other than in .subs, and
there are no nested .subs?
--
Chip Salzenberg- a.k.a. -<[EMAIL PROTECTED]>
Open Source is not an excuse to write fun code
then leave the actual work to others.
whole transcript before
mailing a question about its contents.
PS: For any readers are puzzled as I was, "new_pad" and "store_lex"
combine to cover the nesting semantics.
--
Chip Salzenberg- a.k.a. -<[EMAIL PROTECTED]>
Open
like to suggest that we continue to do without a #parrot log,
and replace it with a tradition of giving informative people a good
pasting. For example, today, #parrot hosted this conversation:
<@chip> I don't think we should log IRC, there's too much chatter.
I'd
by the equivalent of Module::Starter or
h2xs, and all the author has to do is make sure he picks a good name
for it.
Again, I'm only mildly concerned about these issues. I'm only
spelling them out in detail in an attempt at clarity.
--
Chip Salzenberg- a.k.a. -<[EMAIL PROTECTED]>
Open Source is not an excuse to write fun code
then leave the actual work to others.
According to Ron Blaschke:
> Chip Salzenberg wrote:
> > How many variables need to be exported currently? I'd consider it an
> > API feature if there were no exported variables whatsoever ...
>
> Let's see...
> Parrot_base_vtables
> pio_stdio_layer
> op_ji
1 - 100 of 387 matches
Mail list logo
