aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThien-Thi Nguyen <[email protected]>2002-06-03 03:15:34 +0000
committerThien-Thi Nguyen <[email protected]>2002-06-03 03:15:34 +0000
commit4738677d0b75e48874d436022d32441684e2d6e6 (patch)
tree83c38d8f1bba6a8681be71643d46152bf5757ac2
parente2c0561ec51837dad43442727ac97279a7b346ca (diff)
Initial revision
-rw-r--r--admin/notes/iftc25
1 files changed, 25 insertions, 0 deletions
diff --git a/admin/notes/iftc b/admin/notes/iftc
new file mode 100644
index 0000000000..294464a860
--- /dev/null
+++ b/admin/notes/iftc
@@ -0,0 +1,25 @@
+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.