incubator-lucy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marvin Humphrey (JIRA)" <>
Subject [jira] Updated: (LUCY-40) Core object model
Date Mon, 14 Sep 2009 22:19:58 GMT


Marvin Humphrey updated LUCY-40:

    Attachment: core_object_model_support.diff

In addition to the files attached to the sub-issues of LUCY-40, two more
changes are necessary to get the core object model working.  

First, core_object_model_support.diff must be applied.  It primarily undoes a
bunch of temporary hacks, such as commented-out pound-includes.  It also fixes
a couple latent bugs and inserts some THROW code now that Err is available.

Second, you need a local copy of ppport.h.  This file is generated by the
Devel::PPPort, which recommends that you distribute it along with your code:


Don't direct the users of your module to download Devel::PPPort . They are
most probably no XS writers. Also, don't make ppport.h optional. Rather, just
take the most recent copy of ppport.h that you can find (e.g. by generating it
with the latest Devel::PPPort release from CPAN), copy it into your project,
adjust your project to use it, and distribute the header along with your

However, the generated ppport.h file contains the usual Perl license

This program is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.

I don't imagine that distributing ppport.h is compatible with the Apache
license, and I'm looking into what our options are.

> Core object model
> -----------------
>                 Key: LUCY-40
>                 URL:
>             Project: Lucy
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Marvin Humphrey
>            Assignee: Marvin Humphrey
>            Priority: Blocker
>         Attachments: core_object_model_support.diff
> Implement the classes that comprise Lucy's core object model: Obj, VTable,
> CharBuf, Hash, VArray and Err.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message