view admin/notes/iftc @ 64780:4def766e2c3f

Revision: miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-515 Merge from gnus--rel--5.10 Patches applied: * gnus--rel--5.10 (patch 104) - Update from CVS 2005-08-05 Daiki Ueno <ueno@unixuser.org> * lisp/gnus/mml2015.el (mml2015-pgg-sign): Make sure micalg is correct. * lisp/gnus/pgg-parse.el (pgg-parse-hash-algorithm-alist): Add SHA-2. 2005-08-06 Romain Francoise <romain@orebokech.com> * lisp/gnus/message.el: Fix typo in docstring. 2005-07-16 Romain Francoise <romain@orebokech.com> * lisp/gnus/gnus-uu.el (gnus-uu-save-article): Use `message-make-date' instead of `current-time-string' as the latter creates a time string that is not RFC 2822 compliant (it lacks the zone).
author Miles Bader <miles@gnu.org>
date Sun, 07 Aug 2005 23:56:33 +0000
parents 695cf19ef79e
children 375f2633d815 ef719132ddfa
line wrap: on
line source

Iso-Functional Type Contour


This is a term coined to describe "column int->float" change approach, and can
be used whenever low-level types need to change (hopefully not often!) but the
meanings of the values (whose type has changed) do not.

The premise is that changing a low-level type potentially means lots of code
needs to be changed as well, and the question is how to do this incrementally,
which is the preferred way to change things.

Say LOW and HIGH are C functions:

  int LOW (void) { return 1; }
  void HIGH (void) { int value = LOW (); }

We want to convert LOW to return float, so we cast HIGH usage:

  float LOW (void) { return 1.0; }
  void HIGH (void) { int value = (int) LOW (); }  /* iftc */

The comment /* iftc */ is used to mark this type of casting to differentiate
it from other casting.  We commit the changes and can now go about modifying
LOW and HIGH separately.  When HIGH is ready to handle the type change, the
cast can be removed.

;;; arch-tag: 3309cc41-5d59-421b-b7be-c94b04083bb5