Talking Points Memo
This Modern World
Working for Change
Book review: Darwinia
Reviewed: Friday, August 11, 2006
Summer reading: Spin
Reviewed: Saturday, August 5, 2006
Reviewed: Tuesday, July 18, 2006
the Omnivoire's Delimma
Reviewed: Wednesday, July 12, 2006
the Golem's Eye
Reviewed: Wednesday, May 31, 2006
Making deprecate part of the language
Saturday, May 15, 2004
Adding the language element deprecate to Common Lisp is easy but adding a macro only goes part way to really changing the language. What else is there?
- The warning generated by deprecate needs to fit in with the rest of the Lisp implementation's warning and compile system,
- There should be ways to make language elements deprecated even if you do not have the original source,
- Any documentation system should be able to understand how deprecate fits into the Lisp implementation system.
- The IDE and tools of the implementation need to understand the new element and deal with it appropriately (coloring, filtering, and so forth). I think editors like Eclipse can do this but I'm not sure whether it really can or how easy it is do so).
These are the sort of things -- things usually thought of as beyond or outside the bounds of a programming language -- that really matter to developers as they work.