Andreas Bernauer <firstname.lastname@example.org> writes:
> On 10/7/05, Andreas Rottmann <email@example.com> wrote:
>> Since I'd like to be able to run SUnet on Scheme48, I have wondered
>> what the best way would be to achive this; here are excerpts of my
>> exchange with Michael Sperber:
>> Since currently these
>> constants are hardcoded to match the constants used in the
>> corresponding C API, my idea was to have a platform-specific mapping
>> procedure, e.g. PROTOCOL-FAMILY->OS-INTEGER, that maps the finite type
>> instances to their C constant counterparts.
>> Of course these changes will break backwards compatibility, hence code
>> using the network API must be adapted or the old interface
> I'm currently not so much into SUnet and scsh, but what's the point in
> porting SUnet from scsh to Scheme48 and at the same time breaking
> backwards compatibility? I am not sure if I understand you correctly:
> when people want to add something to SUnet, will they have to write
> one version for scsh and one version for Scheme48?
If I understood Mike Sperber correctly, he has this steps in mind:
1) Clean up the network API in scsh
2) Rebuild that API on s48 - on that point scsh and s48 have
compatible network interfaces
3) Port SUnet to the new network API
I would be glad if he could comment that this is really what he has in
mind, or correct me, since I'm not sure.
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | firstname.lastname@example.org
http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Make free software, not war!