diff options
author | Glenn Morris <rgm@gnu.org> | 2014-10-15 00:07:29 -0700 |
---|---|---|
committer | Glenn Morris <rgm@gnu.org> | 2014-10-15 00:07:29 -0700 |
commit | 12e8ede75cc09a665455609bbb3006f0896c52af (patch) | |
tree | 79a59d62ffcc40aad1b9cf15ba0a64ea91674f8e /admin/notes/iftc | |
parent | 0b298692909debe108be77e9d357b49816bafb16 (diff) |
Remove some admin/notes files
* admin/notes/lel-TODO: Remove. This has not turned out to be a
useful way to get things documented.
* admin/notes/exit-value, admin/notes/iftc: Remove.
These don't seem to have any particular relationship to Emacs development.
Diffstat (limited to 'admin/notes/iftc')
-rw-r--r-- | admin/notes/iftc | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/admin/notes/iftc b/admin/notes/iftc deleted file mode 100644 index 983b148668..0000000000 --- a/admin/notes/iftc +++ /dev/null @@ -1,26 +0,0 @@ -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. - |