view admin/notes/iftc @ 72468:5e47ca87ee3c

Rcirc update from Ryan Yeske 2006-08-20 Ryan Yeske <[e-mail]> * lisp/net/rcirc.el (rcirc-show-maximum-output): New var. (rcirc-buffer-process): If no buffer argument is supplied, use current-buffer. (rcirc-complete-nick): Complete to the last completed nick first. (rcirc-mode): Preserve the value of `rcirc-urls' across connections. Setup scroll function. (rcirc-scroll-to-bottom): New function. (rcirc-print): Use nick syntax around regexp work. Notice dim-nicks speaking only if they say our nick. (rcirc-update-activity-string): Do not show the modeline indicator if there are no live rcirc processes. (rcirc-cmd-ignore): Ignore case. (rcirc-browse-url-at-point): Fix off-by-one error. Revision: [e-mail]/emacs--devo--0--patch-403

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