[632] in Coldmud discussion meeting
Re: floating point
daemon@ATHENA.MIT.EDU (Mon Jan 16 17:23:02 1995
)
From: paul@solar.sky.net
To: zachary@pentagon.io.com (Zachary)
Date: Mon, 16 Jan 1995 16:19:32 -0600 (CST)
Cc: coldstuff@MIT.EDU
In-Reply-To: <199501161552.JAA17514@pentagon.io.com> from "Zachary" at Jan 16, 95 09:52:07 am
> >It'd be nice if cold supported floating point, even if only as a compile-time
> >option. As I understand, it has this capability, but it is unimplemented.
> Yes that would be nice... waitaminnit.. if it's unimplemented, how can it be considered a
> 'capability' ?
I mean, as I recall, when the driver was designed, the writer had this
ability in mind, which would mean that it wouldn't be extremely unhealthy
to implement.
>
> >It would be nice if we had someone who would take charge and make all the
> >changes we all agree upon. Someone who everyone agreed upon, who was
> >wel familiar with coldmud and C, and who had the time and energy. Any
> >volunteers?
>
> Heh. the two main problems seem to be 1) getting everyone to agree on what changes to be
> made and 2) getting someone to maintain and coordinate the entire effort.
>
> What do people think of some sort of option config file for cold? This would be a way
> to enable/disable 'features' that are 'nonstandard'. Features like floating point,
> suspend/resume, etc.. Setting these up in your config file would, perhaps, add some
> particular symbols to $sys or something so objects can check to see if these features are
> present - nice cores could even have some sort of library object that will do in-db
> emulation (if possible) of the requested function if it's not present...
>
Sounds good to me. That way, what is used by more systems will become
'standard'. But who'll do it?
wrt brandon's message: Crag has become disinvolved with muds (remind you
of anyone?). He might be back, but don't quote me on that.
and congratulations to you and Mrs Lynx-elect.
Paul