Opened 15 years ago
Closed 15 years ago
#90 closed task (wontfix)
Compiled SLIB support
Reported by: | Tony Sidaway | Owned by: | Tony Sidaway |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | extensions | Version: | 4.1.x |
Keywords: | slib egg compiled | Cc: | |
Estimated difficulty: |
Description
I'm working on strategies for integrating SLIB release 3b2 into Chicken as a small series of eggs each containing a number of compiled SLIB modules packaged as Chicken modules. As far as possible, existing Chicken code that provides SLIB features will be relied on.
Work to date comprises a SLIB module analyzer that packages a SLIB source module as a Chicken module and translates dependencies such as (require 'FEATURE), (require-if 'compiling 'FEATURE) to the equivalent Chicken require-extension, import and so on. When compiled, the modules work well with Chicken 4 and each other.
Much work still needs to be done particularly in integrating the various SLIB macro systems with compiled code.
Present thinking is that SLIB's catalog system will *not* be supported as, with proper treatment, it's made redundant by the egg system which is one of Chicken's greatest assets.
Change History (4)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
Status: | new → accepted |
---|
I'm currently looking at portability issues in general.
comment:3 Changed 15 years ago by
Are you still working on this? Otherwise we should close the ticket.
Replying to tonysidaway:
A big task for sure. But SLIB contains a lot of good code.
Clever, but in various failed attempts at integrating SLIB I came to the conclusion that it's a mess and not suited for batch-compiling Schemes. But scavenging what's useful is a good idea.
I'll suggest to ignore those.
I fully agree.