Any reason *not* to make this change:
Index: include/parrot/string.h
===
RCS file: /cvs/public/parrot/include/parrot/string.h,v
retrieving revision 1.59
diff -d -u -r1.59 string.h
--- include/parrot/string.h 22 Apr 2004 08:55:06
At 3:56 PM -0500 6/10/04, Matt Fowles wrote:
All~
Speaking of basic PMC types, I remember a bunch of basic array PMCs
that were discussed recently, some for each register type, some
which autovivified, some which didn't etc. I believe that a
stringarray was actually inserted (although
At 10:50 AM +0100 6/11/04, Nicholas Clark wrote:
Is there any reason not to have a coding standard that typedef should be
used whenever possible (and non-uses must have their reason commented?)
Nope. So mote it be. typedefs for types, #defines for constants and
bizarre (*temporary*!) debugging
Dan Sugalski wrote:
I'm going to formally establish a basic set of
parrot PMC classes. We're going to now have:
Undef - The undefined value. Looks like 0, 0.0, false, or the empty
string, depending on how you peer at it. Can transform into any other
type. Assignment of an boolean, integer,
At 2:38 PM +0200 6/11/04, Bernhard Schmalhofer wrote:
Dan Sugalski wrote:
I'm going to formally establish a basic set of
parrot PMC classes. We're going to now have:
Undef - The undefined value. Looks like 0, 0.0, false, or the empty
string, depending on how you peer at it. Can transform
# New Ticket Created by Nicholas Clark
# Please include the string: [perl #30220]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=30220
---
osname= darwin
osvers= 7.3.0
arch= darwin-64int-2level
cc= ccache
All~
Are you suggesting that these things use the PMC classes for
String|Integer|Float or should they use STRING|INTVAL|FLOATVAL? Also,
looking through CVS there appears to already be
array.pmc -- basic resizable array
floatvalarray.pmc -- Array of FLOATVALs
intlist.pmc -- Array of
At 12:57 PM -0500 6/11/04, Matt Fowles wrote:
All~
Are you suggesting that these things use the PMC classes for
String|Integer|Float or should they use STRING|INTVAL|FLOATVAL?
Externally? They should use the classes. When you do a get_pmc_keyed
from a StringArray, the result should be a String
While I realize that Leo's doing conference stuff at the moment, I'd
like to start thinking about the next release. For this, I think I'd
specifically like to shoot for the redo of classes/ -- getting all
the PMCs we *want* actually in and working, and the ones we don't
marked deprecated,
I checked in more of PDD 17, detailing parrot's base types. Some of
those types definitely don't exist (like, say, the string and bignum
type...) and could definitely use implementing. Should be fairly
straightforward, and would be a good way to get up to speed on
writing PMC classes.
--
Time for these as well. There's a partial implementation of them in
types/bignum.c. I think it's time to move that to src/ (and the
header file to .h) and get it integrated into parrot.
--
Dan
--it's like this---
Dan Sugalski
11 matches
Mail list logo
