diff options
| author | Thien-Thi Nguyen | 2002-06-03 03:15:34 +0000 |
|---|---|---|
| committer | Thien-Thi Nguyen | 2002-06-03 03:15:34 +0000 |
| commit | 4738677d0b75e48874d436022d32441684e2d6e6 (patch) | |
| tree | 83c38d8f1bba6a8681be71643d46152bf5757ac2 /admin | |
| parent | e2c0561ec51837dad43442727ac97279a7b346ca (diff) | |
| download | emacs-4738677d0b75e48874d436022d32441684e2d6e6.tar.gz emacs-4738677d0b75e48874d436022d32441684e2d6e6.zip | |
Initial revision
Diffstat (limited to 'admin')
| -rw-r--r-- | admin/notes/iftc | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/admin/notes/iftc b/admin/notes/iftc new file mode 100644 index 00000000000..294464a8605 --- /dev/null +++ b/admin/notes/iftc | |||
| @@ -0,0 +1,25 @@ | |||
| 1 | Iso-Functional Type Contour | ||
| 2 | |||
| 3 | |||
| 4 | This is a term coined to describe "column int->float" change approach, and can | ||
| 5 | be used whenever low-level types need to change (hopefully not often!) but the | ||
| 6 | meanings of the values (whose type has changed) do not. | ||
| 7 | |||
| 8 | The premise is that changing a low-level type potentially means lots of code | ||
| 9 | needs to be changed as well, and the question is how to do this incrementally, | ||
| 10 | which is the preferred way to change things. | ||
| 11 | |||
| 12 | Say LOW and HIGH are C functions: | ||
| 13 | |||
| 14 | int LOW (void) { return 1; } | ||
| 15 | void HIGH (void) { int value = LOW (); } | ||
| 16 | |||
| 17 | We want to convert LOW to return float, so we cast HIGH usage: | ||
| 18 | |||
| 19 | float LOW (void) { return 1.0; } | ||
| 20 | void HIGH (void) { int value = (int) LOW (); } /* iftc */ | ||
| 21 | |||
| 22 | The comment /* iftc */ is used to mark this type of casting to differentiate | ||
| 23 | it from other casting. We commit the changes and can now go about modifying | ||
| 24 | LOW and HIGH separately. When HIGH is ready to handle the type change, the | ||
| 25 | cast can be removed. | ||