On 22/04/2008, Jeff Horwitz [EMAIL PROTECTED] wrote:
On Tue, 22 Apr 2008, Donald Hunter wrote:
hi donald!
hm, i thought i committed the fix for this, but apparently not. check out
r334 in the mod_parrot repository.
Great, that fixed my build problem, thanks. I needed to change
On Tue, 22 Apr 2008, Donald Hunter wrote:
Hi,
hi donald!
I'm trying to build mod_parrot against Parrot 0.6.1 and have found that
string_nprintf no longer exists. I see from ticket #44053 that the function
was removed since it had no users.
What's the preferred solution? Re-introduce
Hi,
I'm trying to build mod_parrot against Parrot 0.6.1 and have found that
string_nprintf no longer exists. I see from ticket #44053 that the
function was removed since it had no users.
What's the preferred solution? Re-introduce string_nprintf or modify
mod_parrot to use another method
On Tue, Apr 22, 2008 at 6:55 AM, Donald Hunter [EMAIL PROTECTED] wrote:
Hi,
I'm trying to build mod_parrot against Parrot 0.6.1 and have found that
string_nprintf no longer exists. I see from ticket #44053 that the function
was removed since it had no users.
What's the preferred solution
# New Ticket Created by Jeff Horwitz
# Please include the string: [perl #50064]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=50064
This patch modifies a single NCI signature to support mod_parrot 0.4.Index: src
On Monday 21 January 2008 07:38:10 Jeff Horwitz wrote:
This patch modifies a single NCI signature to support mod_parrot 0.4.
Thanks, applied as r25518.
-- c
From my journal:
I'm pleased to announce that after 2 years of hiatus and 6 months of
coding, mod_parrot 0.4 has been released. It's been worth the wait, as we
now have working mod_perl6 and PHP proof-of-concepts, per-vhost
interpreter pools, the framework for a more comprehensive test suite
thanks to the hallway track at OSCON, some help from particle, and many
many tuits this weekend, mod_parrot now builds against parrot HEAD, and
all tests pass. i went on hiatus way back in 2006 to wait for parrot to
mature a bit, and it's amazing how much has changed since i last worked
# New Ticket Created by Lambeck
# Please include the string: [perl #36818]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=36818
Hi all,
in order to make mod_parrot-0.3 work with parrot-0.2.3 there need to be some
On Sat, 2005-08-06 at 05:03 -0700, Lambeck wrote:
in order to make mod_parrot-0.3 work with parrot-0.2.3 there need to be some
additions to src/call_list.txt . These statements are included in the patch.
This patch is important because otherwise the users need to patch and
recompile parrot
i'm pleased to announce the release of mod_parrot 0.3. the most notable
changes include support for all apache hooks, autogeneration of
request_rec methods, and a mod_pugs proof of concept. it also supports
both the new (leo-ctx5) and old calling conventions.
you can download it at http
Jeff Horwitz [EMAIL PROTECTED] wrote:
mod_parrot 0.2 is now available from http://www.smashing.org/mod_parrot or
from SVN at http://svn.perl.org/parrot-modules/mod_parrot.
Steadily evolving, great.
major changes include support for parrot 0.1.2 (phoenix), the beginnings
of a thread-safe
On Tue, 29 Mar 2005, Leopold Toetsch wrote:
Jeff Horwitz [EMAIL PROTECTED] wrote:
mod_parrot 0.2 is now available from http://www.smashing.org/mod_parrot or
from SVN at http://svn.perl.org/parrot-modules/mod_parrot.
Steadily evolving, great.
major changes include support for parrot
Leopold Toetsch wrote:
One thing still missing is to retrieve the current namespace inside a
subroutine, which will be in RSN, e.g.:
$P0 = interpinfo .INTERPINFO_CURRENT_NAMESPACE
Actually it is:
$P0 = interpinfo .INTERPINFO_CURRENT_SUB
ns = $P0.get_name_space()
See the new tests in
mod_parrot 0.2 is now available from http://www.smashing.org/mod_parrot or
from SVN at http://svn.perl.org/parrot-modules/mod_parrot.
major changes include support for parrot 0.1.2 (phoenix), the beginnings
of a thread-safe interpreter pool, support for more apache hooks,
updated documentation
# New Ticket Created by Lambeck
# Please include the string: [perl #33191]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=33191
Hi all,
in order to make mod_parrot-0.1 work with parrot-0.1.1 there need to be some
I've just released mod_parrot 0.1. As I noted in my previous post a few
weeks ago, it now supports authentication handlers. Other major changes
include a testing framework (using Apache::Test), access to Apache
constants, and POD documentation.
You can download it here: http://www.smashing.org
i've just uploaded the mod_parrot source:
http://www.smashing.org/mod_parrot/dist/mod_parrot-0.0.tar.gz
this initial release allows you to register a parrot content handler and
encapsulates apache's request_rec structure in a parrot object. unlike
the original version, the current mod_parrot
i've made some good progress on mod_parrot. since so much has changed
in the past year, i decided to rewrite the thing from scratch. here's
what i've been able to implement so far:
* rewrite for apache 2 (might as well start with the latest)
* per-process interpreter persistence (using prefork
Okay, here's the scoop. Ages ago, Clever People whipped up
mod_parrot, an apache module that embedded parrot. This was really
cool.
Alas, Parrot wasn't up to snuff at the time, and the project
languished. This wasn't cool, but neither was it unsurprising.
I think we're at the point where
kevin falcone gave a short mod_parrot talk at YAPC this year. does he
want to lay some claim to it? i'd be willing to pick it up if nobody else
speaks up -- a decision i'm sure to regret... ;-)
on a related note, last year i wrote extproc_parrot, which lets you call
parrot bytecode
At 4:11 PM -0400 8/25/04, Jeff Horwitz wrote:
kevin falcone gave a short mod_parrot talk at YAPC this year. does he
want to lay some claim to it? i'd be willing to pick it up if nobody else
speaks up -- a decision i'm sure to regret... ;-)
I caught up with Kevin on irc (#parrot on irc.perl.org
I caught up with Kevin on irc (#parrot on irc.perl.org, for anyone
who cares :) and he lacks the tuits to do anything with it.
now that the summer is winding down, i've got plenty of those. so i guess
that's me volunteering.
-jeff
Chromatic [EMAIL PROTECTED] wrote:
On Mon, 2004-05-24 at 03:43, Leopold Toetsch wrote:
Yep. The main problem is that by far not all internal code paths are
using exceptions so that you could interfer the exit handling. This
needs of course being fixed somewhen.
Is this as simple and tedious
Paul Querna [EMAIL PROTECTED] wrote:
I have started work on building a new Apache 2.0 Module to run Parrot.
1) Parrot_exit() - This is used in many places after an error occurs.
This function calls any exit callbacks previously entered, and then
calls exit(). This is horrible from an
On Mon, 2004-05-24 at 03:43, Leopold Toetsch wrote:
Yep. The main problem is that by far not all internal code paths are
using exceptions so that you could interfer the exit handling. This
needs of course being fixed somewhen.
Is this as simple and tedious as replacing all Parrot_exit() calls
Hello,
I just started hacking on Parrot Yesterday, so if some of these
questions have easy answers, please point me in the right direction.(I
have read most of the PDDS / fair ammount of the other PODs).
I have started work on building a new Apache 2.0 Module to run Parrot.
The
TF == Tim Fries [EMAIL PROTECTED] writes:
TF Has there been any active development on mod_parrot since last
TF year?
active, no. I was consumed with the last 9 months of school.
TF The CVS on perl.org seems to have lost steam on the project 11 months
TF ago. This is an area I'm interested
Greetings,
Has there been any active development on mod_parrot since last year?
The CVS on perl.org seems to have lost steam on the project 11 months
ago. This is an area I'm interested in tinkering around with a bit to
get to learn Parrot better and possibly be useful at the same time, but
I
With a little bit of substitution magic, a serious abuse of dynamic
linking, a count or two of using static data improperly, mod_parrot
can now have scripts which output to the users' web browser.
I think they're coming to take me away... put me in a little blue
room for a while...
If you
So I know for the first-stage rollout, does Apache's module system support
Apache managing filehandles and modules calling apache's I/O routines, or
does it just do weird magic with I/O on normal filehandles?
I'm pretty sure that for a simple implementation, we only need to worry
about O
Robert Spier and I just had some fun.
Parrot for Apache. :-)
http://cvs.perl.org/cvsweb/mod_parrot/
It's really simplistic and doesn't actually work. As Robert just
told me, it'll be really ugly to get to actually send stuff back to
the browser until Parrot has some kind of real IO subsystem
32 matches
Mail list logo
