I took a gander at the below branch and I I like the idea. However, as I was browsing through the new tree layout there were some thoughts/questions that came to mind.
I guess I'm not clear as to what the difference is between ./clownfish/perl and ./clownfish/cfc/perl. I'm seeing binding code in both paths, or at least what I believe is binding code. With this current layout does that mean there would be eventually a ./clownfish/ruby or is the perl directory just an artifact of the current Perl porting effort? I'm guessing after reading through your e-mail again that code in the cfc directory is only compiler specific? You mention there is work to be done with duplicating test files, could you give an example as to which tests need to be ported or duplicated? I'm also thrilled to see Lucy being forked on github! Thanks, Logan On Fri, Sep 21, 2012 at 3:13 PM, Marvin Humphrey <[email protected]>wrote: > Greets, > > I believe that we need to separate Clownfish and CFC into different > directories and build them as distinct CPAN/etc modules. > > * `Clownfish::CFC` is a compiler written in C. It has no prerequisites > aside from the host language. > * `Clownfish` is the Clownfish core (Hash, CharBuf, VTable, Method, > etc.). > It depends on `Clownfish::CFC`. > > I've prepared a branch on Github that illustrates the layout: > > https://github.com/rectang/lucy/tree/cfish_core/clownfish > > * All content in $REPOS/clownfish/ moves down one directory into > $REPOS/clownfish/cfc/. (Alternately, it could move sideways into > $REPOS/cfc/.) > * The new directories $REPOS/clownfish/core and $REPOS/clownfish/perl > consist of selected content extracted and adapted from $REPOS/core/ and > $REPOS/perl/. > > There's plenty more work to do -- such as duping test files -- but what's > there now should be enough to serve as a proof-of-concept. > > The plan here is to copy the Clownfish core, work on it until it builds on > its > own, then integrate it into the Lucy core and once that's complete, delete > the > originals from the Lucy core. > > There's not much that's new here except for the disruption of moving CFC's > files around. If we were already on Git I would have just committed these > changes into a feature branch within our own repository, but Github will do > for now. > > PS: I'm going to try a Github pull request for this feature branch as an > experiment. I think the notification will go to [email protected] > then we'll set up forwarding. > > Marvin Humphrey >
