Re: GSoC 2016: proposal accepted!

[Daniel J. <dan...@gm...>]

> CLISP style is more geared towards "compactness" (e.g., only the closing
> brace is ever on its own line, never the opening - unless it is the
> first in a function and thus in the first column; no more than 2 spaces
> for indentation &c).

> I suggest sticking with the current conventions for now.

I stick with the var macro and the CLISP style then, falling back to GNU
where CLISP style is "underspecified".


> Your next step after making the release might be removing varbrace and
> requiring C99 - are there any major compilers which don't support it?

As far as I know all support it at least to the extend that we could use
what's provided by gnulib. I'll investigate more on that after GSOC :)


> Not really.  CLISP is GNU GPL v2+, so all your code is to be released
> under that license; I assume you understand that. :-)
> A simple note in an e-mail that you acknowledge and accept that fact and
> do consent to releasing your code under GPLv2+ is fine.

I understand, acknowledge and accept that all of my code for CLISP is to be
released under GNU GPL v2+.


> If you have no questions for a week, please send e-mail here describing
> your progress.
> I am afraid you will be asking questions more frequently than sending
> progress reports though :-)

That's more than likely :)

I'm currently still working through the code in order to understand better
how the various parts fit together (it's still "community bonding period",
so I guess this is ok). Compiling with -fdump-rtl-expand and using egypt
helped a lot. I'm also having a hard time reproducing some crashes when
running under GDB, which is probably due to lots of places with undefined
behaviour. I'll try to get rid of them soon.

The testsuite is really impressive, though it doesn't help much when making
little changes. Thus I think about adding some tests that are closer to what
they tests.

I'm not really experienced with keeping a changelog. As the CLISP
changelog seems to be pretty detailed: How do you maintain it?

There are two accepted projects for libffcall:
https://summerofcode.withgoogle.com/projects/#5894719238307840
https://summerofcode.withgoogle.com/projects/#5412443132002304
Do you know anything about these? As far as I know CLISP is the
main "user" of that library - shall I try to contact them to
know "what they're up to"?