Mercurial > emacs
annotate admin/notes/iftc @ 96067:e2c64ca546da
(cal-menu-holidays-menu): Use calendar-cursor-holidays rather than
cal-menu-today-holidays.
(cal-menu-today-holidays): Remove function.
(cal-menu-holiday-window-suffix): Simplify.
(cal-menu-list-holidays-year, cal-menu-list-holidays-following-year)
(cal-menu-list-holidays-previous-year, calendar-mouse-goto-date):
Remove unused functions.
(calendar-mouse-view-diary-entries): Use format rather than concat.
(cal-menu-x-popup-menu): Turn it into a macro.
(calendar-mouse-holidays, calendar-mouse-view-diary-entries)
(calendar-mouse-print-dates): Adapt for cal-menu-x-popup-menu change.
(cal-menu-event-to-date): Remove function.
(calendar-mouse-holidays, calendar-mouse-view-diary-entries)
(calendar-mouse-view-other-diary-entries, calendar-mouse-print-dates)
(cal-menu-set-date-title): Use calendar-cursor-to-date rather than
cal-menu-event-to-date.
(calendar-mouse-tex-day, calendar-mouse-tex-week, calendar-mouse-tex-week2)
(calendar-mouse-tex-week-iso, calendar-mouse-tex-week-monday)
(calendar-mouse-tex-filofax-daily, calendar-mouse-tex-filofax-2week)
(calendar-mouse-tex-filofax-week, calendar-mouse-tex-month)
(calendar-mouse-tex-month-landscape, calendar-mouse-tex-year)
(calendar-mouse-tex-filofax-year, calendar-mouse-tex-year-landscape):
Remove functions.
(cal-menu-context-mouse-menu): Replace the above functions with the
cal-tex versions. Add HTML submenu.
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Wed, 18 Jun 2008 02:56:17 +0000 |
parents | 695cf19ef79e |
children | 375f2633d815 ef719132ddfa |
rev | line source |
---|---|
45625 | 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. | |
52401 | 26 |
27 ;;; arch-tag: 3309cc41-5d59-421b-b7be-c94b04083bb5 |