Sorry I was on holiday. Yes this can be closed.
On 21 Sep 2005, at 09:45, Joshua Hoblitt via RT wrote:
[mikescott - Thu Oct 09 11:49:45 2003]:
If someone happens to have dlcompat
http://www.opendarwin.org/projects/dlcompat/
installed on OS X then the following patch will let Parrot be
Hello all,
Maybe some of you remember how I used to have endless hours in Berlin
to fiddle with Parrot documentation. Then I got a job, moved back to
London, and disappeared.
I can't say I have been following the list closely, but I have read the
occasional summary from time to time. I'm out
I've had this list lying around for too long, but never seem to find
time to make it all shiny and complete.
I want to have another go at the html documentation. But before I start
I'd prefer to have a good list of everything Parrot. That way I can
build a proper subject view of the project.
I've checked in some changes which fix this.
I would would like to close the ticket but I can't.
For some reason when I log in to RT as mikescott I have zero
visibility/permission. Logging in as guest solves the visibility but
not the permission problem. I've raised this issue before but no
On 12 May 2004, at 17:38, Brent 'Dax' Royal-Gordon wrote:
It's Parrot telling you that something happened.
Squawk?
Mike
I just moved from Berlin to London and started a new job, so haven't
had time recently for Parrot documentation. Indeed there is plenty to
be done. I should be back on the case in a week or two.
Mike
On 7 May 2004, at 17:13, Simon Glover wrote:
No. The closest we have to something like this
On 14 Apr 2004, at 20:16, Larry Wall wrote:
I think the idea of tagging complete strings with language is not
terribly useful. If it's to be of much use at all, then it should
be generalized to a metaproperty system for applying any property to
any range of characters within a string, such that
On 13 Apr 2004, at 23:43, Dan Sugalski wrote:
I've been assuming it's a left-side wins, as you're tacking onto an
existing string, so you'd get English in all cases. Alternately you
could get an exception. The end result of a mixed-language operation
could certainly be the Dunno language or
On 12 Apr 2004, at 17:43, Dan Sugalski wrote:
IW: Mush together (either concatenate or substr replacement) two
strings of different languages but same charset
TP: Checks to see if that's allowed. If not, an exception is thrown.
If so, we do the operation. If one string is manipulated the
On 13 Apr 2004, at 22:48, Dan Sugalski wrote:
Note that the language might be Dunno. :) There'll be a default
that's assigned to input data and suchlike things, and the language
markers in the strings can be overridden by code.
Would this be right?
English + English = English
English +
Just thought I'd mention that I'm in the process of trying to get
strings.pod updated to reflect the current state of affairs.
Mike
I notice that on OS X t/native_pbc/number.t is no longer skipped and is
failing. I'm wondering if this is intentional?
Looking into this I noticed that 'make pdump' fails because it needs
ICU.
Here's a patch for config/gen/makefiles/root.in.
root_in.patch
Description: Binary data
Mike
On 10 Apr 2004, at 15:04, Leopold Toetsch wrote:
Not only pdump. All utils built by make world. I'd suggest to include
an $(ALL_PARROT_LIBS) to each target.
+ $(LIBPARROT) $(LIBICUCORE) $(LIBICUDATA) $(C_LIBS)
instead of that.
Ok. I'll do that and commit it.
Mike
Thanks to Will Coleda, I finally added docs/submissions.pod - how to
submit bug reports, patches and new files to Parrot.
Mike
I've updated the docs for the ops parsing system.
make html-clean; make html
You'll find it under Perl Modules/Operations and Ops/Tools.
Mike
I've been all over the ops2c system recently filling in the
documentation (it'll get committed this weekend sometime) so number 2
is something I can certainly do.
BTW is there a reason for the colon at the start of the hints?
Mike
On 27 Mar 2004, at 08:15, Leopold Toetsch wrote:
Opcodes
Just committed some new docs for the Parrot::* modules.
make html-clean; make html
Mike
I'm trying to write some documentation for the ops2c system at the
moment and have a question.
In Parrot::OpsFile::read_ops() a Parrot::Op's type is set to 'inline'
or 'function', yet in Parrot::Op type is expected to be 'auto' or
'manual'.
Auto ops have a 'goto NEXT()' appended to their
languages/tcl/.cvsignore is the only .cvsignore in the MANIFEST and a
fresh checkout is failing with
t/src/manifest..ok 2/4# Failed test (t/src/manifest.t at
line 51)
# Missing files in CVS:
# languages/tcl/.cvsignore
I assume this means languages/tcl/.cvsignore should not be
On 16 Mar 2004, at 05:21, Will Coleda wrote:
[...]
If the =head3 is the culprit, then:
./Configure.pl
./docs/debug.pod
./docs/dev/dod.dev
./docs/ops/rx.pod
./docs/pdds/pdd11_extending.pod
./docs/pmc/subs.pod
./imcc/docs/calling_conventions.pod
./imcc/docs/imcfaq.pod
On 6 Mar 2004, at 05:31, Robert Spier wrote:
[...]
The problem isn't today. It's the trend and next month, when
someone decides they need to add some other module, and has a
precedent to follow. Then, suddenly we end up with 30 different
modules included in our distribution, each one changed
Fpath/file and CPerl::Module now become links in the HTML docs, if
the target file contains POD.
make html-clean
make html
Mike
On 7 Feb 2004, at 00:53, Michael Scott wrote:
On 6 Feb 2004, at 22:32, Leopold Toetsch wrote:
- icu
- lib/Test/*
- lib/Pod/*
are all standard thingys. I'm not thinking that we are gonna
reinventing wheels nor that we are gonna copying existing wheels, so
I'd
vote for just removing all that from
On 4 Mar 2004, at 15:51, Dan Sugalski wrote:
[...]
I'd like to remove non-modified, non-parrot Perl modules from lib and
install them via CPAN.pm.
No. Sorry, definitely not. Parrot's config isn't going to install
perl modules off the 'net any more than it's going to run apt-get on
systems
I just reported this as a bug on Pod::Simple::HTML.
The problem is in line 168-9
my $out = $to if defined $to and length $to;
$out .= # . $section if defined $section and length $section;
One of those Deprecated use of my() in conditional cases they've been
talking about on
Applied.
I would close the ticket but RT tells me I have no permission to view
it.
Mike
On 2 Mar 2004, at 14:34, [EMAIL PROTECTED] (via RT) wrote:
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #27308]
# in the subject line of all future correspondence about
I've added two targets to the Makefile.
html: Generate HTML documentation from POD in the sources.
html-clean: Remove the HTML documentation.
Mike
On 29 Feb 2004, at 03:07, Robert Spier wrote:
[...]
Someone else can take care of this for him. (And I know he'd love it
if someone stepped forward to become official web content maintainer.)
We'll provide that person with resources and support, and it'll be
quite fun and easy for everyone.
On 26 Feb 2004, at 18:57, Mitchell N Charity wrote:
A perl by any other name, may be a different perl.
perl and /usr/bin/perl are both common in #!'s.
I been changing them to #! perl -w when i find them, which is why
your list covers the places I haven't visited. The good thing about the
bang
this.
Am I right or wrong? Let those with greater knowledge speak...
Mike
On 24 Feb 2004, at 01:31, Will Coleda wrote:
my .cvsrc has update -dP, and I still get the same problem with the
platforms directory. (OS X)
On Monday, February 23, 2004, at 04:50 PM, Michael Scott wrote:
I have
On 24 Feb 2004, at 15:06, Arvindh Rajesh Tamilmani wrote:
Does the following command work?
$ cvs co '!parrot/platforms' parrot
# the order should be preserved.
on tcsh it gives me
cvs co '!parrot/platforms' parrot
tcsh: parrot/platforms: Event not found.
but on sh it did
... and in tcsh (OS X)
cvs co '\!parrot/platforms' parrot
Mike
I have this problem too.
cvs [update aborted]: could not chdir to platforms: Not a directory
Same problem even if I do a new check out.
cvs [checkout aborted]: could not chdir to parrot/platforms: Not a
directory
There is no local platforms directory, yet CVS wants to go to it, so I
assume
Done, thanks.
On 22 Feb 2004, at 14:39, Arvindh Rajesh Tamilmani wrote:
I didn't specify -kb when I added the images.
I suppose that's it.
$ cvs admin -kb file # corrects the repository
$ cvs update -A file # updates the working copy
should fix the problem.
But I wonder how -kCOPY got
All that metadata up front in the PDDs is a bit off-putting. I'm
thinking of going through all of them and putting it at the end. Any
objections?
Also, throughout the distribution we use variously TITLE (aka TITEL)
and NAME with and without the file path.
I've been using
=head1 NAME
My fault. I didn't specify -kb when I added the images. I suppose
that's it.
I'll hold off trying to fix it for the moment, in the hope that someone
with more CVS knowledge will beat me to it.
Mike
On 21 Feb 2004, at 23:05, Steve Fink wrote:
.
.
.
P docs/pmc/subs.pod
cvs server:
Thanks, applied.
On 20 Feb 2004, at 01:56, chromatic wrote:
On Thu, 2004-02-19 at 16:34, Michael Scott wrote:
One thing that would help is if people ran
perl tools/docs/write_docs.pl -d -s
on various platforms and told me if it works - or what they did to
make
it work - because I only have
On 19 Feb 2004, at 20:59, Simon Glover wrote:
pdd12_assembly.pod -- what was the intent of this? (i.e. is there
stuff
that isn't covered in pdd06_pasm.pod that should go in here, or can
we just dump this and recycle the number?)
Yes it should go. It's just an earlier version of pdd06.
I'm
On 10 Feb 2004, at 14:09, The Perl 6 Summarizer wrote:
I wonder how long it'll be before someone reimplements
them in in PIR...
or Perl6 perchance.
On 9 Feb 2004, at 01:49, Nicholas Clark wrote:
Have the LZW patents(*) expired everywhere yet
google tells me there's one down and seven to go
http://www.kuro5hin.org/story/2003/6/19/35919/4079
I just pinched it from parrotcode.org. Does that make me a felon?
Mike
I have to write some unit tests for the Parrot::IO::* and
Parrot::Docs::* modules and I'm wondering where to put them.
How about creating t/perl and adding Parrot_IO_*.t etc? Or should I go
for a t/perl/Parrot/IO/*.t approach? Someone help me make up my mind.
No need for them to be run with
Suppose I could make a few changes to Pod-Simple, then our problem
would be solved.
But, being serious, say I'd decided to use Template-Toolkit, it would
never have occurred to me to shove all of that in CVS. It always
surprised me a that ICU was there, rather than just what was needed to
get
On 6 Feb 2004, at 22:32, Leopold Toetsch wrote:
- icu
- lib/Test/*
- lib/Pod/*
are all standard thingys. I'm not thinking that we are gonna
reinventing wheels nor that we are gonna copying existing wheels, so
I'd
vote for just removing all that from CVS.
yep
All non-trivial packages have some
Ah, ok, my bad then. I'd just assumed that, apart from any need for
modification, the other things were there simply to save having to tell
everyone to go off and get them. I don't intend to change Pod-Simple if
I can possibly help it, so it's ok by me to delete lib/Pod, if that's
the
I've added the Perl modules for the docs tools to lib/Parrot/IO and
lib/Parrot/Docs. I've also added Pod-Simple (2.05) and Pod-Escapes
(1.03) which they use.
Running
perl tools/docs/write_docs.pl
should build the html tree in docs/html. I'd be interested to know of
any problems encountered.
an example use
http://www.speex.org/API/refman/speex__bits_8h.html#a2
Follow the links, including to the annotated source file.
Tim.
On Thu, Jan 29, 2004 at 07:20:50PM +0100, Michael Scott wrote:
I've add inline docs to everything in src (except for malloc.c and
malloc-trace.c).
At times I wondered
I've add inline docs to everything in src (except for malloc.c and
malloc-trace.c).
At times I wondered whether this was the right thing to do. For
example, in mmd.c, where Dan had already created a mmd.pod, I ended up
duplicating information. At other times I reckoned that what was needed
On 25 Jan 2004, at 00:50, Gordon Henriksen wrote:
[...]
Is there something so terribly wrong with English? How about a general
scheme of adjective* noun? So, respectively,
MixedArray
Array
FixedArray
StringArray
FixedStringArray
Array is what Perl familiars will usually want.
Did I miss
A few notes on the benchmarks can be found/added here
http://www.vendian.org/parrot/wiki/bin/view.cgi/Main/
ParrotDistributionExamples#benchmarking
Mike
On 26 Jan 2004, at 00:14, Luke Palmer wrote:
Matt Fowles writes:
All~
Of late it seems that everybody has been throwing around their own
Is there a reason why the names have to be so terse?
Mutable is not a bad word for able-to-change. (Cribbed from Cocoa,
though there the immutability is absolute).
*) Array - fixed-size, mixed-type array
*) MutablePArray - variable-sized PMC array
*) PArray - Fixed-size PMC array
*)
2004, at 19:33, Dan Sugalski wrote:
At 10:42 AM +0100 1/21/04, Michael Scott wrote:
Perhaps the most controversial feature of all this is that I'm using
rows of 80 '#'s as visual delimiters to distinguish documentation
sections from code.
Please don't. If you really, really must, chop it down
Duh. Rereading that I can see I got my numbers in a twist. I've been
adding them where missing.
On 22 Jan 2004, at 19:39, Dan Sugalski wrote:
At 2:06 PM +0100 1/19/04, Michael Scott wrote:
Some files have CVS version $Id strings, some don't.
While tidying up the documentation I'm visiting
PDD 7 Conventions and Guidelines for Parrot Source Code has a section
on Code Comments that has been followed for C code. I'm about to
change this.
The existing documentation headers will be replaced with pod headers
contained within C multi-line comment delimiters. I'm going to stick to
I've committed updates to the documentation in the Perl scripts in
build_tools, classes and tools/dev.
http://homepage.mac.com/michael_scott/Parrot/docs/html
All scripts now run with -w (turned up a harmless bug in
Parrot::Vtables, which I fixed).
CVS $Id and copyright notices were also
Some files have CVS version $Id strings, some don't.
While tidying up the documentation I'm visiting every file. I can
either:
1) add them when missing
2) remove them when present
3) do nothing
I was inclined to (1) until I reflected that it did preserve a relation
between local and repository
On 17 Jan 2004, at 21:47, Leopold Toetsch wrote:
[...]
BTW don't we have some docs/*.pod with a summary of sending patches?
Also the Fgettingingstarted.pod seems to be missing in the tree.
I have a submissions.pod on the wiki which I'll put in. Problem is at
the moment I can't see either the
They're already commited.
On 16 Jan 2004, at 00:21, chromatic wrote:
On Thu, 2004-01-15 at 15:02, Michael Scott wrote:
So, after migrating from Pod::Checker to Pod-Simple, I've cleared up
all the pod errors and done a rudimentary html tree.
Do you have patches to fix the errors in CVS
Maybe we can use someone else's solution...
http://lists.ximian.com/archives/public/mono-list/2003-November/
016731.html
On 16 Jan 2004, at 00:33, Jonathan Worthington wrote:
- Original Message -
From: Dan Sugalski [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 15,
I'm attempting to update Configure.pl --help to include all the
options. I parsed the files in config so I reckon I have all the
options, I'd just be grateful if anyone can point out any
misunderstandings. The expnetwork option defines EXP_NETWORKING in
config.h, but this is unused. Should it
Is this relevant?
http://oss.software.ibm.com/icu/userguide/formatNumbers.html
I'm still not clear in my mind what the plan is with regard to ICU. Is
it intended eventually to be:
a) an always-there part of parrot, or
b) just a sometimes-there thing that gets linked in if you mess with
Well I did originally have this in mind, but the more I looked into it
the more I thought it needed someone with unicode experience.
It seems to me that the unicode world is full of ah but in North
Icelandic Yiddish aleph is considered to be an infinitely composite
character and other such
So, after migrating from Pod::Checker to Pod-Simple, I've cleared up
all the pod errors and done a rudimentary html tree. The state of
parrot pod can be seen here
http://homepage.mac.com/michael_scott/Parrot/docs/html/. That's every
file that has pod in it. Obviously there are a few files such
$Config{archname} wasn't getting parsed quite right on OS X and so JIT
wasn't getting detected in some cases. I checked in a fix for that.
It's certainly nice to see the tests run faster.
make test
All tests successful, 49 subtests skipped.
Files=90, Tests=1289, 138 wallclock secs (47.38 cusr +
You'll find some diagrams here which might help.
http://www.vendian.org/parrot/wiki/bin/view.cgi/Main/
ParrotDiagramsString
On 13 Jan 2004, at 22:06, Robert Eaglestone wrote:
OK, I'm looking at the Parrot String documentation, and I've
got questions. It's not like the docs are a total mess,
I'm currently building some docs related modules which will allow us to
create an html tree from the pod, inline stuff included.
I cleaned up all the pod errors last week and was going to report on
that but got sidetracked when I realised that POD::Checker diverged
somewhat from Perl's own pod
For those of you who like perusing gobs of autogenerated info, take a
look at
http://homepage.mac.com/michael_scott/Parrot/pod_report.html
where I've put up a list of Parrot POD errors as seen by podchecker.
I've started to put together a bunch Perl modules which will allow us
autogenerate
I just downloaded and tried to build Parrot and make failed with
In file included from include/parrot/pmc.h:18,
from include/parrot/parrot.h:250,
from imcc/imc.h:18,
from imcc/main.c:17:
include/parrot/thread.h:103: error: conflicting types for
On 22 Dec 2003, at 23:59, Elizabeth Mattijsen wrote:
snip
I think we need a change of mindset. Instead of seeing threaded
programs as the special case, we would need to see that the single
threaded program is the special case. See how many people use POE for
event handling, and through what
1) What is Parrot documentation?
It seems to me that the problem presented by information about Parrot
is that it exists in different layers and contexts.
The presence of the docs directory in CVS is deceptive. It suggests
that it's contents are in some way definitive. But, in practice, the
snip ...too much undocumentation going on.
One of the reasons I started putting stuff on the wiki was because I
could see that updating documentation was not a high priority.
On the wiki I neither have to have CVS checkin rights, nor do I have to
wait for someone with those rights to act upon
In an attempt to understand what the plan is with regard to ICU and
Parrot strings in general, I've been gathering together links to
previous bits of discussion on:
http://www.vendian.org/parrot/wiki/bin/view.cgi/Main/
ParrotDistributionUnicodeSupport
Obviously what is still needed is
Reeducation succeeded.
I resolved #24030 and #24038 by changing the Status field and hitting
Save Changes, then I noticed there was a Resolve option on the top
righthand side which asks for details for a notification email. I'm
wondering which is the approved way?
I ask because I'll add a
On 30 Oct 2003, at 07:20, Robert Spier wrote:
Some of patches on that list that are mine.
#24030 Obsolete
#24038 Obsolete
#24043 Applied
#24063 Applied
#24177 Rejected
#24188 Applied
I tried to update the status of #24177 but got Permission Denied.
Any chance of that being changed so I could
Some of patches on that list that are mine.
#24030 Obsolete
#24038 Obsolete
#24043 Applied
#24063 Applied
#24177 Rejected
#24188 Applied
I tried to update the status of #24177 but got Permission Denied.
Any chance of that being changed so I could update them myself?
Mike
On Wednesday, Oct 22,
Shouldn't imcc/docs (eventually) be docs/imcc, and imcc/t be t/imcc?
Mike
On Thursday, Oct 23, 2003, at 04:29 Europe/Berlin, Melvin Smith wrote:
IMCC has graduated from the parrot/languages/imcc directory to
parrot/imcc.
Please update your trees.
We may still want to move the main up to the
Almost forgot: imcc/examples to be (eventually) examples/imcc.
Mike
docs/parrot_assembly.pod is just an earlier version of PDD 6.
On Thursday, Oct 23, 2003, at 18:34 Europe/Berlin, Leopold Toetsch
wrote:
Simon Glover wrote:
On Thu, 23 Oct 2003, Leopold Toetsch wrote:
Here is a list of files that I consider to be unused:
Can I also suggest:
optimizer.pl
On Friday, Oct 10, 2003, at 14:22 Europe/Berlin, Dan Sugalski wrote:
On Fri, 10 Oct 2003, Leopold Toetsch wrote:
Michael Scott [EMAIL PROTECTED] wrote:
config/gen/platform/darwin.c
Add conditional code for PARROT_HAS_HEADER_DLFCN.
Could you please rediff the patch w/o the whitespace
docs/parrot_assembly.pod is just an earlier version of PDD 6.
An empowered person should remove it.
Mike
If anyone has anything else, I have a page for this on the wiki.
What's not in the Parrot distribution?
http://www.vendian.org/parrot/wiki/bin/view.cgi/Main/ParrotExtrasTOC
On Wednesday, Oct 8, 2003, at 11:38 Europe/Berlin, Jos Visser wrote:
Hi,
Mightn't it be (is this English by the way? :-) a
On Tuesday, Oct 7, 2003, at 17:51 Europe/Berlin, Dan Sugalski wrote:
WHich ought ot be some sort of really bad '50s era black and white
giant
atomic monster movie. But anyway.
ICU now configures and builds on at least some platforms. That means
it's
time to build an encoding and chartype
leo -- appending myconfig to bug reports can't harm - never.
Inspired by this bit of wisdom, (and my own earlier silliness with a
useless backtrace), I've updated Aldo's patch faq to cover submissions
to Parrot in general. I suggest it should go in docs.
http://www.parrotcode.org/patchfaq can
On Friday, Oct 3, 2003, at 16:12 Europe/Berlin, Dan Sugalski wrote:
Do we currently have anything that looks at the /*=for foo bar baz
docs
embedded in the C code? I see it's in some (but not all) of the C
files,
and I wanted to double-check the rules as I'm starting the extension
code
stuff,
On Friday, Oct 3, 2003, at 16:58 Europe/Berlin, Dan Sugalski wrote:
When (says the man with poor access to his mail archives at the moment
:)?
21st Sept 2003
I just heard from Steven R. Loomis (ICU) about this. They have a better
solution which will go into ICU 2.8.
For those interested, it turns out that gcc -MMD writes out the
dependency file by itself, therefore redirecting stdout, which contains
preprocessed text, to the file was wrong.
Here's
On Thursday, Oct 2, 2003, at 04:48 Europe/Berlin, Robert Spier wrote:
[snip]
(We probably could simplify things by requiring GNU make.. but I'm not
going to start that now.)
Now that you mention it ... ICU requires GNU make.
Mike
On Tuesday, Sep 30, 2003, at 15:44 Europe/Berlin, Juergen Boemmels
wrote:
Michael Scott [EMAIL PROTECTED] writes:
Here are some tests for the io.h API that should go in t/src/io.t.
Ah yes. I know I submitted one too. I thought it got committed a long
time ago but maybe it wasn't. I will try
On Tuesday, Sep 30, 2003, at 19:20 Europe/Berlin, Juergen Boemmels
wrote:
Michael Scott [EMAIL PROTECTED] writes:
On Tuesday, Sep 30, 2003, at 15:44 Europe/Berlin, Juergen Boemmels
wrote:
Michael Scott [EMAIL PROTECTED] writes:
Here are some tests for the io.h API that should go in t/src/io.t
On Tuesday, Sep 30, 2003, at 19:31 Europe/Berlin, Melvin Smith wrote:
Since PIO_parse_open_flags just assists the IO code in fulfilling
an API, but is not part of the published API, I would suggest that it
be moved into the private, but before tests are written for it, there
should be a spec
sent upstreadm it will keep our life simpler in the future.
-R
Michael Scott (via RT) wrote:
# New Ticket Created by Michael Scott # Please include the string:
[perl #24043]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id
=0xbb50) at hash.c:406
#4 0x2b5c in main (argc=1, argv=0xbc2c) at CrashingTest.c:36
#5 0x27f8 in _start (argc=1, argv=0xbc2c, envp=0xbc34)
at /SourceCache/Csu/Csu-45/crt.c:267
#6 0x2678 in start ()
JEff
On Thursday, September 25, 2003, at 08:22 AM, Michael Scott wrote
Given Leo's new scheme for C code tests, I suggest that we add a header
to be included in the test, and modify Parrot::Test so that it knows to
add the header's location to the command.
This patch puts the header in parrot/t/c_test_header.h.
The correct scheme for a C test can now be:
On Thursday, Sep 25, 2003, at 00:41 Europe/Berlin, Robert Spier wrote:
Which version of ICU is in parrot/icu. Maybe 2.6 would be the most
likely to build.
As an update would probably best be done by delete and replace,
perhaps
it could coincide with the great renaming?
Actually, it would be best
Here are some tests for the io.h API that should go in t/src/io.t.
Maybe some of the expected results are debatable.
Should PIO_parse_open_flags think that is the same as ?
Should PIO_fdopen open ok on stdout with invalid flags like ;-) or ?
Also, successive calls to PIO_seek with SEEK_CUR
On Thursday, Sep 25, 2003, at 13:20 Europe/Berlin, Leopold Toetsch
wrote:
Michael Scott [EMAIL PROTECTED] wrote:
t/src/hash.t
test 7 fails on Mac OS X 10.2.6 (gcc 3.3) because BIGLEN is too big:
9.
100_000 chars for the key doesn't seem to be very big.
Wher does it fail?
Can you debug/back
On Thursday, Sep 25, 2003, at 16:06 Europe/Berlin, Michael Scott wrote:
On Thursday, Sep 25, 2003, at 13:20 Europe/Berlin, Leopold Toetsch
wrote:
Michael Scott [EMAIL PROTECTED] wrote:
t/src/hash.t
test 7 fails on Mac OS X 10.2.6 (gcc 3.3) because BIGLEN is too big:
9.
100_000 chars
I'm sitting here watching CVS download ICU and I'm wondering whether it
wouldn't be better if it was removed from the repository?
It could be replaced by parrot/icu/README to give some sense of
continuity.
Maybe this could be done during the great renaming?
The appropriate version could then
would probably best be done by delete and replace, perhaps
it could coincide with the great renaming?
Mike
On Wednesday, Sep 24, 2003, at 15:30 Europe/Berlin, Dan Sugalski wrote:
On Wed, 24 Sep 2003, Michael Scott wrote:
I'm sitting here watching CVS download ICU and I'm wondering whether
On OS X 10.2.6 (gcc 3.3) make dies with:
perl build_nativecall.pl call_list.txt
nci.c
nci.c: In function `pcf_i_42p':
nci.c:454: error: invalid lvalue in unary `'
Here are some unit tests for the hash.h interface which are PerlHash
free. It could be argued that they're superfluous, but given that there
may well be other hash PMCs that use this code eventually, it might be
worth testing it independently.
Mike
hash.t
Description: application/text
1 - 100 of 101 matches
Mail list logo
