Mercurial > hg > xemacs-beta

view src/vdb.h @ 5566:4654c01af32b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Improve the implementation, documentation of #'labels, #'flet. lisp/ChangeLog addition: 2011-09-07 Aidan Kehoe <kehoea@parhasard.net> * bytecomp.el: * bytecomp.el (for-effect): Move this earlier in the file, it's referenced in byte-compile-initial-macro-environment. * bytecomp.el (byte-compile-initial-macro-environment): In the byte-compile-macro-environment definition for #'labels, put off the compiling the lambda bodies until the point where the rest of the form is being compiled, allowing the lambda bodies to access appropriate values for byte-compile-bound-variables, and reducing excessive warning about free variables. Add a byte-compile-macro-environment definition for #'flet. This modifies byte-compile-function-environment appropriately, and warns about bindings of functions that have macro definitions in the current environment, about functions that have byte codes, and about functions that have byte-compile methods (which may not do what the user wants at runtime). * bytecomp.el (byte-compile-funcall): If FUNCTION is constant, call #'byte-compile-callargs-warn if that's appropriate, giving warnings about problems with calling functions bound with #'labels. * cl-macs.el: * cl-macs.el (flet): Mention the main difference from Common Lisp, that the bindings are dynamic, not lexical. Counsel the use of #'labels, not #'flet, for this and other reasons. Explain the limited single use case for #'flet. Cross-reference to bytecomp.el in a comment. * cl-macs.el (labels): Go into detail on which functions may be called from where. Explain how to access the function definition of a label within FORM. Add a comment cross-referencing to bytecomp.el. man/ChangeLog addition: 2011-09-07 Aidan Kehoe <kehoea@parhasard.net> * cl.texi (Function Bindings): Move #'labels first, describe it in more detail, explaining that it is to be preferred over #'flet, and explaining why. Explain that dynamic bindings with #'flet will also not work when functions are accessed through their bytecodes.
author Aidan Kehoe <kehoea@parhasard.net>
date Wed, 07 Sep 2011 16:26:45 +0100
parents 308d34e9f07d
children
line wrap: on
line source

/* Virtual diry bit implementation for XEmacs.
   Copyright (C) 2005 Marcus Crestani.

This file is part of XEmacs.

XEmacs is free software: you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation, either version 3 of the License, or (at your
option) any later version.

XEmacs is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
for more details.

You should have received a copy of the GNU General Public License
along with XEmacs.  If not, see <http://www.gnu.org/licenses/>. */

/* Synched up with: Not in FSF. */

#include "lisp.h"

#ifndef INCLUDED_vdb_h_
#define INCLUDED_vdb_h_


/*--- prototypes -------------------------------------------------------*/

BEGIN_C_DECLS

/* Platform dependent signal handling: */

/* Install the platform-dependent signal handler. */
void vdb_install_signal_handler (void);

/* Platform dependent memory protection. */
void vdb_protect (void *ptr, EMACS_INT len);
void vdb_unprotect (void *ptr, EMACS_INT len);



/* Common (platform independent) virtual diry bit stuff: */

/* Start the write barrier.  This function is called when a garbage
   collection is suspendend and the client is resumed. */
void vdb_start_dirty_bits_recording (void);
/* Stop the write barrier.  This function is called when the client is
   suspendend and garbage collection is resumed. */
void vdb_stop_dirty_bits_recording (void);

/* Record page faults: Add the object pointed to by addr to the write
   barrer's internal data structure that stores modified objects.
   This function is called by the write barrier's fault handler. */
void vdb_designate_modified (void *addr);

/* Propagate page faults to garbage collector: Read out the write
   barrier's internal data structure that stores modified objects and
   pass the information to the garbage collector.  This function is
   called by vdb_stop_dirty_bits_recording().  Return how many objects
   have to be re-examined by the garbage collector. */
int vdb_read_dirty_bits (void);

/* Provides Lisp functions for testing vdb implementation. */
void syms_of_vdb (void);

END_C_DECLS

#endif /* INCLUDED_vdb_h_ */