Hi!
Ok, how are we going to proceeed? One can convert and install
eggdoc-based documentation in the setup script (manually).
Or we just handle it like in the old chicken-setup. But we need
a new idea for online docs that are based on eggdoc. egg-post-commit
should go (or only be kept for pre 4
On Wed, 27 Aug 2008, felix winkelmann wrote:
Hi!
Ok, how are we going to proceeed? One can convert and install
eggdoc-based documentation in the setup script (manually).
Or we just handle it like in the old chicken-setup. But we need
a new idea for online docs that are based on eggdoc.
On Mon, Aug 25, 2008 at 10:51:34PM -0700, Elf wrote:
i wasnt aware that we weren't supposed to document eggs that way anymore, i
thought it was just wiki preferred. all of my eggs are documented via
eggdoc, not the wiki. only times i use the wiki for my own egg documentation
is to spend
On Tue, Aug 26, 2008 at 7:00 AM, Ivan Raikov [EMAIL PROTECTED] wrote:
Just give me an exact specification and I'll add it (if possible).
Well, in SWIG you can specify an exception handler like this:
%exception
{
const char *err;
clear_exception();
$action
if ((err =
On Tue, Aug 26, 2008 at 7:00 AM, Ivan Raikov [EMAIL PROTECTED] wrote:
What has been dropped is the local documentation feature.
And generating online HTML documentation from an eggdoc script.
Now, that is still generated (by egg-post-commit). It is just not installed.
I can not remember
Hello!
I have added a page to the wiki listing the current status
of eggs which are or have to be ported to the new hygienic
chicken. Before Chicken 4 can be released, and this version
can become the official one, a large part of the eggs should
be ported and available in the release/4 branch.
On 25/08 11:38:53, felix winkelmann wrote:
I have added a page to the wiki listing the current status
of eggs which are or have to be ported to the new hygienic
[ snip ]
See
http://chicken.wiki.br/hygeinic-egg-port-a-mania
^^
On Mon, Aug 25, 2008 at 11:38:53AM +0200, felix winkelmann wrote:
Please contact me (or this list), if you need help or
advice in the porting step. Note that this is also a
convenient moment to get rid of obsolete extensions,
or stuff that doesn't have a maintainer anymore.
I'd like to stress
Would it be easy to create a SWIG module for the hygienic Chicken? I
would like to start with porting endian-port, but I don't want to
invest the time to restructure it to using the Chicken FFI directly.
Also, I would prefer if the eggdoc documentation option is
reinstated, and if future
On Mon, Aug 25, 2008 at 12:51 PM, Ivan Raikov [EMAIL PROTECTED] wrote:
Would it be easy to create a SWIG module for the hygienic Chicken? I
would like to start with porting endian-port, but I don't want to
invest the time to restructure it to using the Chicken FFI directly.
It should be
On Mon, Aug 25, 2008 at 11:38:53AM +0200, felix winkelmann wrote:
Hello!
I have added a page to the wiki listing the current status
of eggs which are or have to be ported to the new hygienic
chicken. Before Chicken 4 can be released, and this version
can become the official one, a large
Alan Post scripsit:
I've been watching the progress on the hygenic branch, but I haven't
been worried about porting code until now. I tend to use macros
here and there, but almost always in very simple #define-like uses:
(define-macro (char-number ch)
`(- (char-integer ,ch)
Alan Post wrote:
(define-macro (char-number ch)
`(- (char-integer ,ch)
(char-integer #\0)))
(define-macro (0= n)
`(= 0 ,n))
(define-macro (begin0 form . forms)
(let ((var (gensym)))
`(let ((,var ,form)) ,@forms ,var)))
If |define-macro| is no longer around, how would the above
felix winkelmann [EMAIL PROTECTED] writes:
It should be possible to use SWIG as usual, but it doesn't generate
modules. I haven't tried to do so, since I personally find SWIG
somewhat cumbersome to use (as opposed to easyffi, for example).
Agreed about cumbersome! I really wish I could
On Tue, 26 Aug 2008, Ivan Raikov wrote:
snip
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
On Tue, Aug 26, 2008 at 2:07 AM, Ivan Raikov [EMAIL PROTECTED] 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
felix winkelmann [EMAIL PROTECTED] writes:
Just give me an exact specification and I'll add it (if possible).
Well, in SWIG you can specify an exception handler like this:
%exception
{
const char *err;
clear_exception();
$action
if ((err = check_exception()))
{
On Tue, 26 Aug 2008, Ivan Raikov wrote:
snip
I can not remember that anybody ever used it
I use it for the majority of the eggs written and maintained by me.
i wasnt aware that we weren't supposed to document eggs that way anymore, i
thought it was just wiki preferred. all of my eggs
18 matches
Mail list logo
