Mercurial > emacs
view nt/TODO @ 28406:451721e784a8
Stop assuming interval pointers and lisp objects can be distinguished by
inspection. Beginnings of support for expensive internal consistency checks.
* config.in (ENABLE_CHECKING): Undef.
* lisp.h (struct interval): Replace "parent" field with a union of interval
pointer and Lisp_Object; add new bitfield to use as discriminant. Change other
flag fields to bitfields.
(CHECK): New macro for consistency checking. If ENABLE_CHECKING is defined and
the supplied test fails, print a message and abort.
(eassert): New macro. Use CHECK to provide an assert-like facility.
* intervals.h (NULL_INTERVAL_P): Now applies only to real interval pointers;
abort if the value looks like a lisp object.
(NULL_INTERVAL_P, NULL_PARENT, HAS_PARENT, HAS_OBJECT, SET_PARENT, SET_OBJECT,
INTERVAL_PARENT, GET_INTERVAL_OBJECT, COPY_PARENT): Modify for new interval
parent definition.
* alloc.c (mark_interval_tree, MARK_INTERVAL_TREE, UNMARK_BALANCE_INTERVALS):
Update references that need an addressable lisp object in the interval
structure.
(die): New function.
(suppress_checking): New variable.
* intervals.c (interval_start_pos): Just return 0 if there's no parent object.
author | Ken Raeburn <raeburn@raeburn.org> |
---|---|
date | Wed, 29 Mar 2000 22:14:34 +0000 |
parents | 354e0c45cedf |
children |
line wrap: on
line source
This is a list of known problems to date with the Windows NT/95 port of GNU Emacs. * Handle wildcards in ls-lisp (e.g., C-x d *.c). * Interactive subprocess output is buffered in jerky * Presently, C:\foo\bar and C:/foo/bar bring up two buffers on the same file. Solve this by adding a switch that canonicalizes path separators (e.g., make them all / or all \)? * call-process-region: Another tricky situation with binary and text modes. An example by dsrosing@reston.ingr.com: use crypt++ to load compressed data into a buffer, edit the buffer, save the data back out. (Also need to propagate the "/C" switch change sent the shell in crypt++.el back to the author.) * Dired uses ls-lisp, which reports all files as being owned by the current user. Need to dig through the security descriptor to extract the owner of the file (and the group?) using LookupAccountSid. * Integrate the build for NT into the GNU config process once a decent shell becomes freely available * Integrate networking. * Fix Win95 subprocesses.