From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] New language?
Date: Wed, 17 Jul 2002 10:21:48 +0200 [thread overview]
Message-ID: <20020717102148.L12824@cackle.proxima.alt.za> (raw)
In-Reply-To: <4597f71f211fce7a20ffe79ce0b55785@plan9.escet.urjc.es>; from Fco.J.Ballesteros on Wed, Jul 17, 2002 at 09:33:55AM +0200
On Wed, Jul 17, 2002 at 09:33:55AM +0200, Fco.J.Ballesteros wrote:
>
> > More seriously, I'm happy to work further on Alef, but I have long
> > ago accepted Bell Labs' view that maintaing the libraries is a
> > disaster.
>
> Is there any way to generate them automatically or to permit
> Alef to bind to C ones somehow? Does it use different conventions
> in the object files?
>
I assume that Bell Labs have looked at this, although not all their
decisions have been entirely flawless.
As I read it, it's a bitch because the procedure call interface is
different from "C". I haven't looked at the internal details, and
I'm less than confident that I would get very far. If forsyth
chose to get involved (or rog, perhaps) we'd have a strong chance.
But if things settle down, it may well be worth it. In addition,
Alef is still experimental, it can pick up quite a lot from Limbo,
if the interest exists (I didn't realise how many features of Alef
I had overlooked in my initial study of it - some of them are
probably obsolete, even, others may be extremely useful).
If the interest is there, I'm happy to put some effort towards
keeping Alef alive. I am not sufficiently up to date, in an academic
sense, to drive language-based changes, though.
++L
next prev parent reply other threads:[~2002-07-17 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 7:33 Fco.J.Ballesteros
2002-07-17 8:21 ` Lucio De Re [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 17:28 [9fans] more extensions Howard Trickey
2002-07-16 17:09 ` [9fans] New language? Sam
2002-07-17 5:45 ` GBA
2002-07-17 6:23 ` Lucio De Re
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020717102148.L12824@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).