The Marpa namespace

refer to the "Marpa Team". At the moment, this is simply me. Other projects of the size and complexity of Marpa are managed by multi-person teams, and I hope that will become the case with Marpa. Thanks, jeffrey kegler

Re: PDF in Marpa::XS distribution?

The consensus in this forum seems be against the uploading of PDF's, or at least of ones of the size I am asking about. So I won't do it. -- jeffrey kegler On Mon, Jul 18, 2011 at 2:07 PM, Andreas J. Koenig wrote: >>>>>> On Sun, 17 Jul 2011 09:43:01 -0700,

PDF in Marpa::XS distribution?

igned to do, and cannot do. Thanks, jeffrey kegler

PDF in Marpa::XS distribution?

I'd like feedback on a question. My feeling is that internals documentation is important, that disk is relatively cheap, and that I should include the PDF file that contains Marpa's internal documentation with the CPAN distribution. But I'd like to know if others agree. Marpa::XS, my XS version

Marpa::* and Parse::Marpa::* CPAN Namespace

pa, and even use the name, with the assurance that they do not have to depend on any response from me. By way of justifying my reserving the name "Marpa": Marpa predates PAUSE, and "Marpa" is a name unlikely to be of use to anyone else. Thanks, Jeffrey Kegler

Re: Tidy up your PAUSE directories

On Mar 31, 2:51 am, tim.bu...@pobox.com (Tim Bunce) wrote: > It would be handy if there was a way for authors to indicate that > new maintainers are sought. Perhaps via the META.yaml/(.json) file. It would also be handy if that (or another) mechanism would also indicate "orphaned modules" -- modul

Re: configure_requires, build_requires, requires

Btw, this is probably as good an opportunity as any for me to express my gratitude to those who created Module::Build, as well as those who make the whole CPAN infra-structure available. @Eric: Perhaps the very useful "phamphlet" you wrote could be added to the Module::Build documents. Since its

Re: Prerequistie for Marpa::HTML

I created ticket 55909 in queue 'Module-Build' for this issue. I am agnostic on whether this is a documentation bug or a misimplementation. I eventually put the requirement in both 'requires' and 'build_requires', but that's just because I want to get my module tested. It does look like, going f

Re: Prerequistie for Marpa::HTML

avior of Module::Build would be more in accord with the following: "Modules listed in this section are necessary to build and install the given module. If a listed module is necessary for regular usage as well as the build and install, the listed module also needs to be specified using the 'r

Prerequistie for Marpa::HTML

rerequisite? 2.) Is my set-up still at fault? META.yml, which is created by Module::build has a "Marpa: 0.100" line, which I hoped would suffice. 3.) Is this a problem with some of the cpantesters setups. thanks, jeffrey kegler