in Coldmud discussion meeting
Re: floating point
daemon@ATHENA.MIT.EDU (Mon Jan 16 10:55:06 1995
Cc: coldstuff@MIT.EDU, email@example.com
In-Reply-To: Your message of "Sun, 15 Jan 1995 15:56:54 CST."
Date: Mon, 16 Jan 1995 09:52:07 -0600
From: Zachary <firstname.lastname@example.org>
>Subject: floating point
>Date: Sun, 15 Jan 1995 15:56:54 -0600 (CST)
>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
>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
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...