Re: Synopsis 26
I never could find the Pod-to-XHTML'd version of S26 -- the document attached to that email was S26.pod6, not S26.xhtml. I don't want to bug Damian, because obviously he has enough of life "happening", as it were. But is the XHTML'd version of S26 available anywhere? I haven't been able to find it, and I don't read POD as well as all you perl veterans =thom -- We would all like to vote for the best man, but he is never a candidate. On 11/22/06, Damian Conway <[EMAIL PROTECTED]> wrote: Many thanks to all those who offered feedback on the first draft, as a result of which you will see that there have been some major adjustments and some important simplications to the new Perl mark-up notation. The first release of (a Perl 5 implementation of) the parser is close to ready...within a week if life doesn't "happen" too much. I also have a prototype Pod-to-XHTML module implemented, in earnest whereof I have attached a Pod-to-XHTML'd version of the synopsis. Damian PS: As a few of you are already aware, I am in the midst of health crisis within my immediate family. This is likely to be on-going for the next month or more, so please accept my apologies in advance if my response-time is frustratingly slow.
Re: [perl #41915] [TODO] remove unused manifest-generating scripts
On 19/03/07, via RT Jerry Gay <[EMAIL PROTECTED]> wrote: # New Ticket Created by Jerry Gay # Please include the string: [perl #41915] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41915 > tools/dev/ has a number of unused and possibly broken scripts. of them, there seem to be a number related to manifest generation: gen_manifest_skip.pl mk_manifest_and_skip.pl mk_manifests.pl your mission: determine if one script can replace the work of three. ~jerry Just as a note, this ticket is related to #40911
[perl #41918] [PATCH] spelling fixes in src/library.c
# New Ticket Created by Mike Mattie
# Please include the string: [perl #41918]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41918 >
Here are the spelling fixes caught by jerry gay. thanks for the heads up.
based against src/library.c rev 17641
tested on i686-pc-gnu-linux
--- HEAD/src/library.c 2007-03-19 18:20:22.0 -0700
+++ parrot-0.4.9/src/library.c 2007-03-19 18:51:58.0 -0700
@@ -160,11 +160,11 @@
return 0;
}
-static const char path_seperator = '/';
+static const char path_separator = '/';
#ifdef WIN32
-static const char win32_path_seperator = '\\';
+static const char win32_path_separator = '\\';
/*
Converts a path with forward slashes to one with backward slashes.
@@ -176,8 +176,8 @@
assert(path->encoding == Parrot_fixed_8_encoding_ptr ||
path->encoding == Parrot_utf8_encoding_ptr);
-while (cnv = strchr(path->strstart, path_seperator))
-*cnv = win32_path_seperator;
+while (cnv = strchr(path->strstart, path_separator))
+*cnv = win32_path_separator;
}
#endif
@@ -206,33 +206,33 @@
/*
unary path arguement. the path string will have a
- trailing path-seperator appended if it is not
+ trailing path-separator appended if it is not
there already.
*/
static STRING*
-path_garuntee_trailing_seperator(Interp *interp, STRING *path )
+path_guarantee_trailing_separator(Interp *interp, STRING *path )
{
-STRING *path_seperator_string = string_chr(interp, path_seperator);
+STRING *path_separator_string = string_chr(interp, path_separator);
/* make sure the path has a trailing slash before appending the file */
if ( string_index(interp, path , path->strlen - 1)
- != string_index(interp, path_seperator_string, 0))
-path = string_append(interp, path , path_seperator_string);
+ != string_index(interp, path_separator_string, 0))
+path = string_append(interp, path , path_separator_string);
return path;
}
/*
binary path arguements, the left arg is modified.
- a trailing seperator is garunteed for the left
+ a trailing separator is guaranteed for the left
arguement and the right arguement is appended
*/
static STRING*
path_append(Interp *interp, STRING *l_path, STRING *r_path )
{
-l_path = path_garuntee_trailing_seperator(interp, l_path );
+l_path = path_guarantee_trailing_separator(interp, l_path );
l_path = string_append(interp, l_path , r_path);
return l_path;
@@ -241,7 +241,7 @@
/*
binary path arguements. A new sting is created
that is the concatentation of the two path components
- with a path-seperator.
+ with a path-separator.
*/
static STRING*
@@ -250,7 +250,7 @@
STRING* join;
join = string_copy(interp, l_path);
-join = path_garuntee_trailing_seperator(interp, join );
+join = path_guarantee_trailing_separator(interp, join );
join = string_append(interp, join , r_path);
return join;
signature.asc
Description: PGP signature
Re: [PATCH] Quiet a few alignment warnings
> On Monday 19 March 2007 11:56, Andy Dougherty wrote:
>
> > The only way to tell for sure if you have a working compiler is to try to
> > compile and run something. After the user has been prompted for all the
> > flags, simply try to compile and run a simple test program. If it works,
> > fine. If it doesn't, then complain with an informative error message. (It
> > may be appropriate to skip the 'run' step in a cross-compilation
> > environment and hope that the user got the flags right if the compilation
> > succeeds.)
On Mon, 19 Mar 2007, chromatic wrote:
>
> What's the minimally-useful, cross-platform way to compile, link, and run:
>
> int main() {
> return 0;
> }
>
> I'm happy to make the change, but I spent the weekend struggling to figure
> out
> how MSVC handles shared libraries, and I'm no longer sure that the easy
> approach is that easy.
You can probably get by with whatever scheme is currently used to compile,
link, and run all the other tests in Configure, such as those to determine
sizeof(opcode_t) and the like. Perl 5's Configure uses the following
program:
#include
int main() { printf("Ok\n"); return(0); }
The program includes output, and Configure tests for that output, because
we ran into cases where the program would compile, run, return a 'success'
exit value, but wouldn't actually print anything. The underlying problem
turned out to be a bug in SFIO's "iffe" configuration script (dealing with
_exit vs. exit, and the flushing of output buffers). So our "sanity" test
was expanded to include testing whether or not the program actually
printed what it was supposed to print.
--
Andy Dougherty [EMAIL PROTECTED]
Re: [perl #41168] graceful "no compiler" error message?
On Mon, 19 Mar 2007, chromatic wrote: > On Monday 19 March 2007 12:22, Andy Dougherty wrote: > > > I found the ticket that introduced this failing behavior, so I'm resending > > my message below with a fixed-up subject line to enter into RT. In brief, > > this patch incorrectly assumes that all compilers accept a '-h', '--help', > > or '/?' switch. Any compiler that doesn't is deemed 'not found', and > > there is no way to override it. Extending the list of options to try is > > not a sensible forward-looking portable strategy. > > I realize this patch precludes cross-compilation at the moment, but does it > work better for you, Andy? Alas, no. Here's what I get (again with --verbose=2). I don't know why it's reporting that the compiler is failling, and I don't know how to coax Configure to give me any more information (short of sprinking printf()s throughout). I can definitely compile that test program with the indicated flags. I don't have time to look at this further, however. Determining what C compiler and linker to use... Setting Configuration Data: ( cc => 'cc', ); Setting Configuration Data: ( link => 'cc', ); Setting Configuration Data: ( ld => 'cc', ); Setting Configuration Data: ( ccflags => '-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64', ); Setting Configuration Data: ( linkflags => ' -L/usr/local/lib -R/usr/local/lib ', ); Setting Configuration Data: ( ldflags => ' -L/usr/local/lib -R/usr/local/lib ', ); Setting Configuration Data: ( libs => '-lsocket -lnsl -ldl -lm', ); Setting Configuration Data: ( cxx => 'c++', ); Setting Configuration Data: ( cc_debug => '', link_debug => '', ld_debug => '', ); Setting Configuration Data: ( ccwarn => '', ); cc -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -c test.c Compilation failed with 'cc' -- Andy Dougherty [EMAIL PROTECTED]
[perl #41168] graceful "no compiler" error message?
On Tue Mar 20 12:13:15 2007, coke wrote: > per chromatic, this should probably be backed out. At least for the > 0.4.10 release. Backed out until we find another solution to the problem. Paul
[perl #41926] [PATCH] partial update of NEWS for 0.4.10
# New Ticket Created by Jerry Gay
# Please include the string: [perl #41926]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41926 >
attached inline is a partial update of NEWS for the 0.4.10 release.
i'm too hungry and tired now to finish it off, so won't somebody carry
it the last bit to the finish line for the release?
i've noted incomplete areas with XXX
~jerry
Index: NEWS
===
--- NEWS(revision 17658)
+++ NEWS(working copy)
@@ -1,5 +1,38 @@
# $Id$
+New in 0.4.10
+
+- Compilers:
+ + IMCC: Parrot calling conventions now available between two C PMCs
+ + PGE: Match object improvements
+ + smop: added Attribute and Class PMCs
+ + HLLCompiler: improvements for interactive mode
+- PAST:
+ + extended binding to a list of variables
+- Languages:
+ + Updated Lua, PHP ("Plumhead"), Tcl ("ParTcl"), Ruby ("Cardinal")
+ + New language: Pynie - a Python compiler for Parrot
+ + lua implements require and many other ops, improved regex support
+ + XXX
+- Design:
+ + PDD01 "Overview" - updated architecture and platform information
+ + PDD15 "Objects" - details on roles, objects, and classes added
+ + PDD22 "I/O" - ahheh async ops and Status PMC details
+- Documentation:
+ + Added guides for Metacommitter, Relase Manager, and Cage Cleaner roles
+ + XXX
+- Implementation:
+ + Object, Class, Role, and Attribute PMC implementation has begun
+ + Perl 5 module "Parrot::Embed" now compiles and links on all platforms
+ + XXX
+- Build:
+ + Major improvements in test coverage for 'ops2c.pl'
+ + XXX
+- Misc:
+ + many bugfixes, enhancements, and coding standard updates
+ + extended support for XXX
+ + Parrot now builds on XXX
+
New in 0.4.9
- Compilers:
Re: [perl #41168] graceful "no compiler" error message?
On Tuesday 20 March 2007 12:25, Andrew Dougherty wrote: > On Mon, 19 Mar 2007, chromatic wrote: > > I realize this patch precludes cross-compilation at the moment, but does > > it work better for you, Andy? > > Alas, no. Here's what I get (again with --verbose=2). I don't know why > it's reporting that the compiler is failling, and I don't know how to > coax Configure to give me any more information (short of sprinking > printf()s throughout). > > I can definitely compile that test program with the indicated flags. I > don't have time to look at this further, however. Alright, I'll work on a better patch. We've pulled the previous one from the upcoming release. -- c
[perl #41927] [PATCH] getting gen_manifest_skip() to return correct results quickly
# New Ticket Created by Paul Cochrane # Please include the string: [perl #41927] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41927 > This patch is a collaborative effort by firstly Coke, myself and then particle on #parrot. It makes the gen_manifest_skip() method of Parrot::Distribution return the list of ignored files in parrot in an appropriately short amount of time. The test t/distro/manifest_skip.t should now work as expected, and only give a few failures, namely: perl t/distro/manifest_skip.t 1..2 # this may take a while... not ok 1 - all files in MANIFEST.SKIP are also in svn:ignore # Failed test (t/distro/manifest_skip.t at line 52) # File in MANIFEST.SKIP but not ignored by SVN: # ^languages/perl6/src/.*\.pbc$ # ^languages/perl6/src/.*\.pbc/ # ^languages/perl6/src/builtins_gen\.pir$ # ^languages/perl6/src/builtins_gen\.pir/ not ok 2 - all svn:ignore files are in MANIFEST.SKIP # Failed test (t/distro/manifest_skip.t at line 54) # Files ignored by SVN but not in MANIFEST.SKIP: # ^languages/APL/lib/$ # ^languages/APL/lib// # ^t/$ # ^t// # Looks like you failed 2 tests of 2. Regards, Paul
[perl #41927] [PATCH] getting gen_manifest_skip() to return correct results quickly
Actually bothering to attach the patch this time... parrot_distro.patch Description: Binary data
[perl #41195] [BUG]: Change to Configure.pl causing 'make' to fail on Darwin
Reverted order of Configure.pl steps, just for you. =-) On Fri Mar 16 19:24:55 2007, [EMAIL PROTECTED] wrote: > Results confirmed again at r17522 tonight.
Parrot 0.4.10 released ...
... At least as far as PAUSE. Web site updated. Once it hits CPAN, I'll push the rest of the announcements out. Thanks to everyone who submitted patches or ideas, for their help in getting this out the door. Code slush is over, spring is here, commit away. -- Will "Coke" Coleda [EMAIL PROTECTED]
