Reading through the dpANS source, I find all text relating to *evalhook*,
*applyhook*, evalhook and applyhook commented out. Are they to be
permanently taken away?
I can't say I miss them. I did test the hack presented in CLtL2, page 493,
and quickly noticed that I couldn't set *evalhook* back to nil when I
had set it to 'eval-hook-function...
--
!+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++!
! Richard Levitte, VMS GNU Emacs hacker ! tel: int+46-8-18 30 99 !
! Sulv"agen 57, II ! fax: none for the moment !
! S-126 40 H"agersten ! Internet: ·······@e.kth.se !
! SWEDEN ! !
!-----------------------------------------------------------------------------!
In article <·····················@elin.e.kth.se> ·······@e.kth.se (Richard Levitte) writes:
>Reading through the dpANS source, I find all text relating to *evalhook*,
>*applyhook*, evalhook and applyhook commented out. Are they to be
>permanently taken away?
Yes, they've been removed from the language. X3J13's justification was:
(3) The eval hook mechanism is a relic of a particular interpreter
implementation technique and really has no place in a language
standard, especially since one of the stated goals of the language is
consistency between compiled and interpreted code. Since there is no
guarantee that these functions will ever be invoked, portable programs
should not rely on them.
--
Barry Margolin
System Manager, Thinking Machines Corp.
······@think.com {uunet,harvard}!think!barmar