Some random thoughts on versions:
1.> One should not be able to install Alpha and Beta modules into the
standard library path without SPECIFICALLY indicating it (--INSTALLBETA). If
the option isn't given, then it installs the module in ./blib/ ('use blib').
2.> 'use strict' and '-w' should
Here's a reference to the Bartlett 'mostly-copying' GC collector.
ftp://gatekeeper.dec.com/pub/DEC/WRL/research-reports/WRL-TR-88.2.pdf
Hans Boehm also has a decent GC reference page with links to Bartlett's, but
his GC is mark/sweep.
http://www.hpl.hp.com/personal/Hans_Boehm/gc/index.html
Grant M
Personally, I'm not sure that Perl 6 even needs to worry about any of this. I
think as long as Perl can manipulate the characters without screwing them up in
any way, that should be fine. As far as support for locale specifics, maybe it
would just be best to do what Perl does now, but allow overlo
> Another example is the chinese has no definite
> sorting order, period. The commonly used scheme are
> phonetic-based or stroke-based. Since many characters
> have more than one pronounciations (context sensitive)
> and more than one forms (simplified and traditional).
> So if we have a mix cont
I can't really believe that this would be a problem, but if they're integrated
alphabets from different locales, will there be issues with sorting (if we're
not planning to use the locale)? Are there instances where like characters were
combined that will affect the sort orders?
Grant M.
> Oh, for heaven's sake, don't be silly. Our goal is to write Perl 6.
> We haven't done that yet. That was our goal, so we failed?
Don't be ridiculous. With that as our goal, the ONLY way we could fail is to
NEVER write Perl 6. Unicode, on the other hand, was originally released for
public consum
Before people get their panties in a bunch, I'm not dissing Unicode. The point
that I am trying to make is that Unicode will probably never make everyone
happy. It WILL likely become widely accepted, and should offer the best
solution yet to integrating the major character sets into one.
> If the
The problem as I see it, is not that the mechanism can't handle the languages,
it is that the Latin/Gothic countries chose first, and gave what's left to the
Oriental countries.
This is evident in the "Musical Symbols" and even "Byzantine Musical Symbols".
Are these character sets more important
Actually, there are already languages named 'Parrot' and 'Poly' (links
below). Besides, I'm getting tired of animals . What about something
more fun, like "Magoo" or "Gilligan"? Or maybe we could move to insects, like
"Mantis" or "Wasp".
If we have to go with an animal, though, I like "Buzza
Dan Sugalski wrote:
>If we do, then something as simple as this:
>
> while () {
> $count++ if /bar/;
> print OUT $_;
> }
>
>would potentially result in the output file being rather different from the
>input file. Equivalent, yes, but different. Whether that's bad or not is an
>
If your interest is in speed alone, then adding UTF_16 might offer options as
well:
FORMAT (enc_flags):
7|6|5|4|3|2|1|0
x x 0 0 1 x x x = UTF_8
x x 0 1 0 x x x = UTF_16
x x 1 0 0 x x x = UTF_32
then:
#define UTF 56
utf_encoding = UTF & enc_flags;
if( utf_encoding ) {
cout << "String is UTF_"
I think I see where you are coming from on the issue of CGI. I think that
although we are approaching it from different angles, we are somewhat on the
same track. I say "Content-Length", you say "memory limits". What I am trying
to say (although I've never been really good at explaining myself)
On Wed, Feb 21, 2001 at 02:05:19PM -0500, Stephen P. Potter wrote:
> If they're going to have to go in and add a "require <6" already, its easier
> to just modify the #! line (and less coding for us).
Duh, <> the #! line. I'm awake now, though. ;)
Grant M.
I've gotta stop getting up before noon.
This is probably way too late, but does this make any sense: could p6 allow
(for the first few versions anyway) a "require <6;" directive?
My thought was that during the install process, the admin would be prompted
as to whether or not they wished to retain 'full' backward compatibility, and
if
I agree with Damien that the Sun description sounds less portable, which we all
know in the Perl world is crucial (>80 ports)(although Sun mentions 16-bit
DOS/Win). Any GC implementation needs to try to 'not break' the existing stuff.
Other questions are somewhat dependent upon what language is us
15 matches
Mail list logo
