On Saturday 23 June 2007 08:48:34 Mark Glines wrote:
> string_from_literal() was added in r19260, to handle the
> string_from_cstring(interp, "some constant string", 0) case more
> efficiently. Rather than doing a strlen() at runtime, it does a
> sizeof() at compile time. That patch also fixed up
On 22/06/07, brian d foy <[EMAIL PROTECTED]> wrote:
===Per class documentation, not per file documentation
Related to the one above, I'd like to have NAME, SYNOPSIS, etc. for
each class, not just per file. Well, what I really want is the
Smalltalk class and method browsers, but I know I'm no
chromatic wrote:
> On Tuesday 12 June 2007 22:28:26 Ron Blaschke wrote:
>
>> I tried to build r18933 and received the following error message:
>>
>> ...
>> src\global_setup.c
>> src\interpreter.c
>> In file included from src\interpreter.c:38:
>> ./include/parrot/oplib/core_ops.h:1: internal compil
On Sunday 24 June 2007 04:48:19 Ron Blaschke wrote:
> Thanks for picking this up. The problem was caused by C<#pragma once>
> which MinGW GCC 3.4.2 seems to choke on. There was some discussion on
> the list ("Removing #pragma") too.
It looks like r18945 should have fixed the problem; can you co
On Tue Feb 13 08:01:12 2007, ptc wrote:
> The profiling options specified in config/init/defaults.pm should be
> moved into their own 'step' of the configure process.
Paul: Can you explain your rationale for this?
kid51
On Tue Feb 13 08:06:53 2007, ptc wrote:
> The profiling options used in config/init/defaults.pm are specific to
> gcc. This should probably be specified in the relevant hints file.
The profiling options code in config/init/defaults.pm reads:
if ( $conf->options->get('profile') ) {
$c
On Sun, 24 Jun 2007 21:13:14 -0700
"James Keenan via RT" <[EMAIL PROTECTED]> wrote:
> The profiling options code in config/init/defaults.pm reads:
>
> if ( $conf->options->get('profile') ) {
> $conf->data->set(
> cc_debug => " -pg ",
> ld_debug => " -pg ",
>
On Fri Jun 22 18:17:49 2007, jkeen at verizon.net wrote:
> Write unit tests for config/init/manifest.pm,
> the module whose functionality executes Parrot
> configuration step init::manifest.
>
> Some tests have already been written for this module in the
> 'reconfigure' branch of the Parrot re
Getting back to the Web Module,
the following could help a lot
if there were in the core or as a 'core' downloadable bundle :
- DBI
- ORM system
- Caching system
- Sessions (server side cookies)
- XML parser
- JSON parser
I guess that it will be fair enough for actual web apps.
templating system
