Mercurial > emacs
annotate admin/notes/iftc @ 111232:a9904c1962db
SMIE: change indent rules format, improve smie-setup.
* lisp/emacs-lisp/smie.el (smie-precs-precedence-table)
(smie-merge-prec2s, smie-bnf-precedence-table, smie-prec2-levels):
Mark them pure so the tables gets built at compile time.
(smie-bnf-precedence-table): Store the closer-alist in the table.
(smie-prec2-levels): Preserve the closer-alist.
(smie-blink-matching-open): Be more forgiving in case of indentation.
(smie-hanging-p): Rename from smie-indent--hanging-p.
(smie-bolp): Rename from smie-indent--bolp.
(smie--parent, smie--after): New dynamic vars.
(smie-parent-p, smie-next-p, smie-prev-p): New funs.
(smie-indent-rules): Remove.
(smie-indent--offset-rule): Remove fun.
(smie-rules-function): New var.
(smie-indent--rule): New fun.
(smie-indent--offset, smie-indent-keyword, smie-indent-after-keyword)
(smie-indent-exps): Use it.
(smie-setup): Setup paren blinking; add keyword args for token
functions; extract closer-alist from op-levels.
(smie-indent-debug-log): Remove var.
(smie-indent-debug): Remove fun.
* lisp/progmodes/prolog.el (prolog-smie-indent-rules): Remove.
(prolog-smie-rules): New fun to replace it.
(prolog-mode-variables): Simplify.
* lisp/progmodes/octave-mod.el (octave-smie-closer-alist): Remove, now that
it's setup automatically.
(octave-smie-indent-rules): Remove.
(octave-smie-rules): New fun to replace it.
(octave-mode): Simplify.
| author | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| date | Fri, 29 Oct 2010 15:20:28 -0400 |
| 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 |
