Mercurial > hg > xemacs-beta
annotate lisp/fontl-hooks.el @ 5169:6c6d78781d59
cleanup of code related to xfree(), better KKCC backtrace capabilities, document XD_INLINE_LISP_OBJECT_BLOCK_PTR, fix some memory leaks, other code cleanup
-------------------- ChangeLog entries follow: --------------------
src/ChangeLog addition:
2010-03-24 Ben Wing <ben@xemacs.org>
* array.h:
* array.h (XD_LISP_DYNARR_DESC):
* dumper.c (pdump_register_sub):
* dumper.c (pdump_store_new_pointer_offsets):
* dumper.c (pdump_reloc_one_mc):
* elhash.c:
* gc.c (lispdesc_one_description_line_size):
* gc.c (kkcc_marking):
* lrecord.h:
* lrecord.h (IF_NEW_GC):
* lrecord.h (enum memory_description_type):
* lrecord.h (enum data_description_entry_flags):
* lrecord.h (struct opaque_convert_functions):
Rename XD_LISP_OBJECT_BLOCK_PTR to XD_INLINE_LISP_OBJECT_BLOCK_PTR
and document it in lrecord.h.
* data.c:
* data.c (finish_marking_weak_lists):
* data.c (continue_marking_ephemerons):
* data.c (finish_marking_ephemerons):
* elhash.c (MARK_OBJ):
* gc.c:
* gc.c (lispdesc_indirect_count_1):
* gc.c (struct):
* gc.c (kkcc_bt_push):
* gc.c (kkcc_gc_stack_push):
* gc.c (kkcc_gc_stack_push_lisp_object):
* gc.c (kkcc_gc_stack_repush_dirty_object):
* gc.c (KKCC_DO_CHECK_FREE):
* gc.c (mark_object_maybe_checking_free):
* gc.c (mark_struct_contents):
* gc.c (mark_lisp_object_block_contents):
* gc.c (register_for_finalization):
* gc.c (mark_object):
* gc.h:
* lisp.h:
* profile.c:
* profile.c (mark_profiling_info_maphash):
Clean up KKCC code related to DEBUG_XEMACS. Rename
kkcc_backtrace() to kkcc_backtrace_1() and add two params: a
`size' arg to control how many stack elements to print and a
`detailed' arg to control whether Lisp objects are printed using
`debug_print()'. Create front-ends to kkcc_backtrace_1() --
kkcc_detailed_backtrace(), kkcc_short_backtrace(),
kkcc_detailed_backtrace_full(), kkcc_short_backtrace_full(), as
well as shortened versions kbt(), kbts(), kbtf(), kbtsf() -- to
call it with various parameter values. Add an `is_lisp' field to
the stack and backtrace structures and use it to keep track of
whether an object pushed onto the stack is a Lisp object or a
non-Lisp structure; in kkcc_backtrace_1(), don't try to print a
non-Lisp structure as a Lisp object.
* elhash.c:
* extents.c:
* file-coding.c:
* lrecord.h:
* lrecord.h (IF_NEW_GC):
* marker.c:
* marker.c (Fmarker_buffer):
* mule-coding.c:
* number.c:
* rangetab.c:
* specifier.c:
New macros IF_OLD_GC(), IF_NEW_GC() to simplify declaration of
Lisp objects when a finalizer may exist in one but not the other.
Use them appropriately.
* extents.c (finalize_extent_info):
Don't zero out data->soe and data->extents before trying to free,
else we get memory leaks.
* lrecord.h (enum lrecord_type):
Make the first lrecord type have value 1 not 0 so that 0 remains
without implementation and attempts to interpret zeroed memory
as a Lisp object will be more obvious.
* array.c (Dynarr_free):
* device-msw.c (msprinter_delete_device):
* device-tty.c (free_tty_device_struct):
* device-tty.c (tty_delete_device):
* dialog-msw.c (handle_directory_dialog_box):
* dialog-x.c:
* emacs.c (free_argc_argv):
* emodules.c (attempt_module_delete):
* file-coding.c (chain_finalize_coding_stream_1):
* file-coding.c (chain_finalize_coding_stream):
* glyphs-eimage.c:
* glyphs-eimage.c (jpeg_instantiate_unwind):
* glyphs-eimage.c (gif_instantiate_unwind):
* glyphs-eimage.c (png_instantiate_unwind):
* glyphs-eimage.c (tiff_instantiate_unwind):
* imgproc.c:
* imgproc.c (build_EImage_quantable):
* insdel.c (uninit_buffer_text):
* mule-coding.c (iso2022_finalize_detection_state):
* objects-tty.c (tty_finalize_color_instance):
* objects-tty.c (tty_finalize_font_instance):
* objects-tty.c (tty_font_list):
* process.c:
* process.c (finalize_process):
* redisplay.c (add_propagation_runes):
* scrollbar-gtk.c:
* scrollbar-gtk.c (gtk_free_scrollbar_instance):
* scrollbar-gtk.c (gtk_release_scrollbar_instance):
* scrollbar-msw.c:
* scrollbar-msw.c (mswindows_free_scrollbar_instance):
* scrollbar-msw.c (unshow_that_mofo):
* scrollbar-x.c (x_free_scrollbar_instance):
* scrollbar-x.c (x_release_scrollbar_instance):
* select-x.c:
* select-x.c (x_handle_selection_request):
* syntax.c:
* syntax.c (uninit_buffer_syntax_cache):
* text.h (eifree):
If possible, whenever we call xfree() on a field in a structure,
set the field to 0 afterwards. A lot of code is written so that
it checks the value being freed to see if it is non-zero before
freeing it -- doing this and setting the value to 0 afterwards
ensures (a) we won't try to free twice if the cleanup code is
called twice; (b) if the object itself stays around, KKCC won't
crash when attempting to mark the freed field.
* rangetab.c:
Add a finalization method when not NEW_GC to avoid memory leaks.
(#### We still get memory leaks when NEW_GC; need to convert gap
array to Lisp object).
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Wed, 24 Mar 2010 01:22:51 -0500 |
| parents | d44af0c54775 |
| children | 308d34e9f07d |
| rev | line source |
|---|---|
| 217 | 1 ;;; fontl-hooks.el --- pre-loaded stuff for font-lock. |
| 2 | |
| 3 ;; Copyright (C) 1992, 1993, 1994, 1995 Free Software Foundation, Inc. | |
| 4 ;; Copyright (C) 1995 Amdahl Corporation. | |
| 5 ;; Copyright (C) 1996 Ben Wing. | |
| 6 | |
| 7 ;; This file is part of XEmacs. | |
| 8 | |
| 9 ;; XEmacs is free software; you can redistribute it and/or modify it | |
| 10 ;; under the terms of the GNU General Public License as published by | |
| 11 ;; the Free Software Foundation; either version 2, or (at your option) | |
| 12 ;; any later version. | |
| 13 | |
| 14 ;; XEmacs is distributed in the hope that it will be useful, but | |
| 15 ;; WITHOUT ANY WARRANTY; without even the implied warranty of | |
| 16 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU | |
| 17 ;; General Public License for more details. | |
| 18 | |
| 19 ;; You should have received a copy of the GNU General Public License | |
| 20 ;; along with XEmacs; see the file COPYING. If not, write to the | |
| 21 ;; Free Software Foundation, Inc., 59 Temple Place - Suite 330, | |
| 22 ;; Boston, MA 02111-1307, USA. | |
| 23 | |
| 24 ;;; Synched up with: FSF 19.30. (font-lock.el) | |
| 25 | |
| 26 ;;; Commentary: | |
| 27 | |
| 28 ;; The reason for the existence of this file is so that modes can | |
| 29 ;; call `font-lock-set-defaults' without worrying about whether | |
| 30 ;; font-lock is loaded. We don't autoload this from font-lock.el | |
| 31 ;; because loading font-lock.el automatically turns font-lock on. | |
| 32 | |
| 33 ;;; Code: | |
| 34 | |
| 35 (defun font-lock-set-defaults (&optional explicit-defaults) | |
| 36 "Set fontification defaults appropriately for this mode. | |
| 37 Sets `font-lock-keywords', `font-lock-keywords-only', `font-lock-syntax-table', | |
| 38 `font-lock-beginning-of-syntax-function' and | |
| 39 `font-lock-keywords-case-fold-search'. | |
| 40 | |
| 41 If `font-lock-defaults' is currently set, it is used. Otherwise, the | |
| 42 symbol naming the major mode is examined for a `font-lock-defaults' | |
| 43 property. If that is not present, but a variable `foo-mode-font-lock-keywords' | |
| 44 is, the value of that variable is used as the default for | |
| 45 `font-lock-keywords'. Various other backward-compatible behaviors also | |
| 46 exist -- if you're curious, look at the source. | |
| 47 | |
| 48 The value of `font-lock-maximum-decoration' is used to determine which | |
| 49 set of keywords applies, if more than one exists. | |
| 50 | |
| 51 This will also put the buffer into Font Lock mode if any keywords exist | |
| 52 and if auto-fontification is called for, as determined by | |
| 53 `font-lock-auto-fontify', `font-lock-mode-enable-list', and | |
| 54 `font-lock-mode-disable-list'. | |
| 55 | |
| 56 Calling this function multiple times in the same buffer is safe -- this | |
| 57 function keeps track of whether it has already been called in this | |
| 58 buffer, and does nothing if so. This allows for multiple ways of getting | |
| 59 Font Lock properly initialized in a buffer, to deal with existing major | |
| 60 modes that do not call this function. (For example, Font Lock adds this | |
| 61 function to `find-file-hooks'.) | |
| 62 | |
| 63 Major modes that have any font-lock defaults specified should call this | |
| 64 function during their initialization process, after they have set | |
| 65 the variable `major-mode'. | |
| 66 | |
| 67 If EXPLICIT-DEFAULTS is t, this function will not check whether it | |
| 68 has already been run in this buffer, and will always do the full | |
| 69 computation. | |
| 70 | |
| 71 If EXPLICIT-DEFAULTS is not nil and not t, it should be something | |
| 72 that is allowable as a value for `font-lock-defaults' and will be | |
| 73 used to initialize the Font Lock variables." | |
| 74 | |
| 75 (when | |
| 76 (and | |
| 77 (featurep 'font-lock) | |
| 78 (if font-lock-auto-fontify | |
| 79 (not (memq major-mode font-lock-mode-disable-list)) | |
| 80 (memq major-mode font-lock-mode-enable-list)) | |
| 81 (font-lock-set-defaults-1 explicit-defaults) | |
| 82 font-lock-keywords) | |
| 83 (turn-on-font-lock))) | |
| 84 | |
| 85 (provide 'fontl-hooks) | |
| 86 | |
| 87 ;;; fontl-hooks.el ends here |