rewrite dynarr code -------------------- ChangeLog entries follow: -------------------- src/ChangeLog addition: 2010-02-03 Ben Wing <ben@xemacs.org> * device-x.c (x_get_resource_prefix): * device-x.c (Fx_get_resource): * device-x.c (Fx_get_resource_prefix): * device-x.c (Fx_put_resource): * dialog-msw.c: * dialog-msw.c (handle_question_dialog_box): * dired-msw.c (mswindows_sort_files): * dired-msw.c (mswindows_get_files): * extents.c (extent_fragment_sort_by_priority): * extents.c (Fset_extent_parent): * file-coding.c (coding_reader): * file-coding.c (coding_writer): * file-coding.c (gzip_convert): * frame.c (generate_title_string): * gutter.c (calculate_gutter_size_from_display_lines): * indent.c (vmotion_1): * lread.c (read_bit_vector): * mule-coding.c (iso2022_decode): * rangetab.c: * rangetab.c (Fcopy_range_table): * rangetab.c (Fget_range_table): * rangetab.c (unified_range_table_copy_data): * redisplay-msw.c (mswindows_output_string): * redisplay-output.c (output_display_line): * redisplay-output.c (redisplay_move_cursor): * redisplay-output.c (redisplay_clear_bottom_of_window): * redisplay-tty.c (tty_output_ichar_dynarr): * redisplay-tty.c (set_foreground_to): * redisplay-tty.c (set_background_to): * redisplay-xlike-inc.c (XLIKE_output_string): * redisplay.c (redisplay_window_text_width_string): * redisplay.c (redisplay_text_width_string): * redisplay.c (create_text_block): * redisplay.c (SET_CURRENT_MODE_CHARS_PIXSIZE): * redisplay.c (generate_fstring_runes): * redisplay.c (regenerate_modeline): * redisplay.c (ensure_modeline_generated): * redisplay.c (real_current_modeline_height): * redisplay.c (create_string_text_block): * redisplay.c (regenerate_window): * redisplay.c (REGEN_INC_FIND_START_END): * redisplay.c (point_visible): * redisplay.c (redisplay_window): * redisplay.c (mark_glyph_block_dynarr): * redisplay.c (line_start_cache_start): * redisplay.c (start_with_line_at_pixpos): * redisplay.c (update_line_start_cache): * redisplay.c (glyph_to_pixel_translation): * redisplay.c (pixel_to_glyph_translation): * sysdep.c (qxe_readdir): * text.c (dfc_convert_to_external_format): * text.c (dfc_convert_to_internal_format): * toolbar-common.c (common_output_toolbar_button): * window.c (window_modeline_height): * window.c (Fwindow_last_line_visible_height): * window.c (window_displayed_height): * window.c (window_scroll): * window.c (get_current_pixel_pos): Use Dynarr_begin() in place of Dynarr_atp (foo, 0). * dynarr.c (Dynarr_realloc): * dynarr.c (Dynarr_lisp_realloc): * dynarr.c (Dynarr_resize): * dynarr.c (Dynarr_insert_many): * dynarr.c (Dynarr_delete_many): * dynarr.c (Dynarr_memory_usage): * dynarr.c (stack_like_malloc): * dynarr.c (stack_like_free): * lisp.h: * lisp.h (DECLARE_DYNARR_LISP_IMP): * lisp.h (XD_DYNARR_DESC): * lisp.h (Dynarr_pop): * gutter.c (output_gutter): * redisplay-output.c (sync_rune_structs): * redisplay-output.c (redisplay_output_window): Redo the dynarr code, add greater checks. Rename the `len', `largest' and `max' members to `len_', `largest_' and `max_' to try and catch existing places that might directly modify these values. Make new accessors Dynarr_largest() and Dynarr_max() and make them and existing Dynarr_length() be non-lvalues by adding '+ 0' to them; fix a couple of places in the redisplay code that tried to modify the length directly by setting Dynarr_length(). Use the accessors whenever possible even in the dynarr code itself. The accessors also verify that 0 <= len <= largest <= max. Rename settor function Dynarr_set_size() to Dynarr_set_length() and use it more consistently; also create lower-level Dynarr_set_length_1(). This latter function should be the only function that directly modifies the `len_' member of a Dynarr, and in the process makes sure that the `largest' value is kept correct. Consistently use ERROR_CHECK_STRUCTURES instead of ERROR_CHECK_TYPES for error-checking code. Reintroduce the temporarily disabled verification code on the positions of Dynarr_at(), Dynarr_atp() and Dynarr_atp_past_end(). Also create Dynarr_resize_if() in place of a repeated code fragment. Clean up all the functions that modify Dynarrs to use the new macros and functions and verify the correctness of the Dynarr both before and after the change. Note that there are two kinds of verification -- one for accessing and one for modifying. The difference is that the modify verification additionally checks to make sure that the Dynarr isn't locked. (This is used in redisplay to check for problems with reentrancy.) * lrecord.h: Move XD_DYNARR_DESC to lisp.h, grouping with the dynarr code.

Introduction

Thank you for downloading XEmacs.  We of the XEmacs development team
believe user satisfaction is our number one priority, and we hope that
you will be pleased with the power of our editor.  Please follow all
of the instructions in order to enjoy a quick and easy installation.


Getting Started

In this guide, information which you will need to supply will be enclosed in
angle brackets, <like this>.  Commands which you will have to enter will be
indented,

	like this.

You will need to provide a loading directory, in which to load the
material from tape (/tmp/xemacs is recommended), and a permanent
installation directory (/usr/local/xemacs is recommended).


Loading From Tape

First create and change directory to the loading directory:

	mkdir <working directory>
	cd <working directory>

Now you are ready to load the software from tape.

The specific device name needed to load the tape varies with hardware vendors,
and may be found in Appendix A, "Vendors and Device Names".

Load the software from tape:

	tar xvf /dev/<device name>

You have now loaded all of the software from tape, and are ready to compile and
install the XEmacs Text Editor.


Compiling and Installing the XEmacs Editor

Compiling and installing the libraries is handled by a user-friendly shell
script.  You will need to provide some information to the script, such as your
organization name and registration number.  To run the script, type

	/bin/sh xemacs/xemacs.install -d <installation directory>

Follow the script's directions, and provide the information which it prompts
for.

When the script prompts you for the directory in which the distribution files
are located, you will find that you are unable to provide it with any directory
which the script will deem satisfactory.  That is because it is necessary to
order the following additional parts which are necessary to continue with the
installation:

	Part Number	Qty	Name				Price

	GM-96-3026	1	Goat, male			 1000.00
	CB-13-2395	1	Candle, black			   50.00
	CG-63-6376	1	Chalk dust container		   10.00
	IB-89-3335	5	Incense sticks			    5.00
	DE-44-8846	1	Dagger, ebon, curved		  500.00
	AS-87-2319	1	Altar, silver			10000.00

Wait until the additional parts arrive; you will be ready to continue the
installation the next Friday the 13th at midnight.


Ritual for Successfully Completing Installation

Stand in front of the computer.  Pour out the chalk dust in an inscribed
pentagram around you; be sure that it is without breaks.  Set an incense stick
at each of the five corners, the altar in front of the computer, and the candle
in front of the altar.

Light each of the incense sticks and the candles, chanting in a low voice:

	Daemons and spirits of the netherworld
	Forces of all that is chaotic and mysterious
	Essence of Netscape and MicroSoft

	I am coming here to appease you
	I offer you this goat
	That my software may work

	I bind you here
	Do not make my system crash
	Let the software install as advertised

Place the goat on the altar, and slaughter it with the dagger.

	May this goat feed you
	Sate your lust for blood
	Into it may your mischief fly
	Not my computer
	Make the software work
	For this is the only way

Then spit into the computer's ventilation slots.  This will complete different
circuits inside the computer, causing its motherboard and cards to function in
ways that the engineers never intended, thereby making your system compatible
with our libraries.

Reboot your computer.  The installation is now complete.

[This has undergone a minor rewrite for XEmacs.  It originally
appeared on rec.humor.funny courtesy of jonathan seth hayward
<jhayward@students.uiuc.edu>, and is included by permission of the
author].