Re: [Chicken-users] hygienic egg PORT-A-MANIA!

[felix winkelmann]

On Tue, Aug 26, 2008 at 2:07 AM, Ivan Raikov <address@hidden> wrote:
>
>   Agreed about cumbersome! I really wish I could use easyffi for
> endian-port, but the problem is that SWIG has the ability of wrapping
> every invocation of a C function with an error handler, which of
> course slows things down, but was an invaluable debugging tool when I
> was developing mat5-lib. Something like the SWIG %exception directive
> might be a useful feature to add to easyffi, actually.

Just give me an exact specification and I'll add it (if possible).

> I also remember
> that I did something with SWIG typemaps that allowed in/out arguments,
> and I am not sure how to reproduce those semantics with the native
> Chicken FFI, other than writing a Scheme wrapper for each C procedure
> that has in/out arguments.

Easyffi makes this actually quite easy.

>
>> Could you describe in more detail what you mean by eggdoc documentation
>> option? And what "sweeping changes" exactly are you talking about?
>
>  The "eggdoc option" was the ability to generate online HTML
> documentation from an eggdoc script. The sweeping change is that the
> eggdoc option was dropped by decree.
>

What has been dropped is the local documentation feature. I can not
remember that anybody ever used it and it is likely to be better to have
a single place for maintaining the documentation (the wiki). I agree that
the wiki pages might not meet everyones taste, but that's how we do
documentation in the moment. Doesn't svnwiki allow heavy customization
of single pages via svn properties? egg-post-commit (which is still running,
and will do so for as long as chicken 3.x.x is supported) could do the
eggdoc->wiki conversion (possibly with embedded HTML) and set
custom css or template for these pages.

>
>> So, if I understand you correctly, you would like to have an automated
>> method of generating wiki pages from eggdoc (automated on commit,
>> that is)?
>
>  Yes, but I also want the HTML pages generated from wiki pages to
> have the same look and feel as HTML pages generated by eggdoc. Maybe
> this is just a matter of using the right style classes in the HTML,
> but take a look for example in the documentation for digraph and
> formular. eggdoc seems to do a much better job at delineating the
> sections and highlighting the procedure headers, and it also has neat
> boxes for the code examples and the license text, while the wiki pages
> use this weird dashed line thing.
>

This is all style and can be changed, or not?


cheers,
felix