[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: dynamic loading of native code modules]

From: Thien-Thi Nguyen
Subject: Re: address@hidden: dynamic loading of native code modules]
Date: Tue, 14 May 2002 01:53:45 -0700

   From: Rob Browning <address@hidden>
   Date: Sun, 21 Apr 2002 10:20:58 -0500

   Thien-Thi Nguyen <address@hidden> writes:

   > we can make incompatibilities non-gratuituous by reflecting them in the
   > version numbering (more "descriptive" thinking here).  by this method,
   > the next official guile should be "2.x" -- what do people think of that?

   Not sure I follow what you mean by "by this method".

   IMO we should bump the major version to 2.0 whenever we made changes
   that we feel warrant it.  Things I would consider warranting such a

     - Restructuring of the evaluation system and macros so that we can
       add compilation (and by compilation I mean anything like VM, JIT,
       offline->c, whatever).

     - Support for elisp that's ready for public use.

     - Performance improvement of large factors due to overhaul of XYZ.

     - Full numeric tower.

"by this method" means considering major incompatiblities as another
thing that warrants a major version change (in addition to new features,
as you've suggested).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]