annotate README @ 4844:91b3d00e717f

Various cleanups for Dynarr code, from Unicode-internal ws dynarr.c: Add comment explaining Dynarr_largest() use. dynarr.c: In Dynarr_insert_many(), don't call Dynarr_resize() unless we actually need to resize, and note that an assert() that we are inserting at or below the current end could be wrong if code wants to access stuff between `len' and `largest'. dynarr.c: Don't just Dynarr_resize() to the right size; instead use Dynarr_reset() then Dynarr_add_many(), so that the 'len' and 'largest' and such get set properly. dynarr.c, faces.c, gutter.c, lisp.h, lread.c, lrecord.h, redisplay-output.c, redisplay.c: Rename Dynarr member 'cur' to 'len' since it's the length of the dynarr, not really a pointer to a "current insertion point". Use type_checking_assert() instead of just assert() in some places. Add additional assertions (Dynarr_verify*()) to check that we're being given positions within range. Use them in Dynarr_at, Dynarr_atp, etc. New Dynarr_atp_allow_end() for retrieving a pointer to a position that might be the element past the last one. New Dynarr_past_lastp() to retrieve a pointer to the position past the last one, using Dynarr_atp_allow_end(). Change code appropriately to use it. Rename Dynarr_end() to Dynarr_lastp() (pointer to the last element) for clarity, and change code appropriately to use it. Change code appropriately to use Dynarr_begin(). Rewrite Dynarr_add_many(). New version can accept a NULL pointer to mean "reserve space but don't put anything in it". Used by stack_like_malloc().
author Ben Wing <ben@xemacs.org>
date Wed, 13 Jan 2010 04:07:42 -0600
parents d96db265d893
children 0ef278ff2894
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
623
3e13cd716cff [xemacs-hg @ 2001-06-22 01:51:40 by ben]
ben
parents: 434
diff changeset
1 This directory tree holds version 21.5 of XEmacs.
3e13cd716cff [xemacs-hg @ 2001-06-22 01:51:40 by ben]
ben
parents: 434
diff changeset
2
2564
d96db265d893 [xemacs-hg @ 2005-02-04 03:04:04 by ben]
ben
parents: 968
diff changeset
3 The information in this file has been superseded by the XEmacs FAQ.
623
3e13cd716cff [xemacs-hg @ 2001-06-22 01:51:40 by ben]
ben
parents: 434
diff changeset
4
2564
d96db265d893 [xemacs-hg @ 2005-02-04 03:04:04 by ben]
ben
parents: 968
diff changeset
5 The easiest way to read the FAQ is to go to
623
3e13cd716cff [xemacs-hg @ 2001-06-22 01:51:40 by ben]
ben
parents: 434
diff changeset
6
2564
d96db265d893 [xemacs-hg @ 2005-02-04 03:04:04 by ben]
ben
parents: 968
diff changeset
7 http://www.xemacs.org/Documentation/21.5/html/xemacs-faq_1.html
623
3e13cd716cff [xemacs-hg @ 2001-06-22 01:51:40 by ben]
ben
parents: 434
diff changeset
8
2564
d96db265d893 [xemacs-hg @ 2005-02-04 03:04:04 by ben]
ben
parents: 968
diff changeset
9 You can also the local copy of the FAQ inside XEmacs by using
d96db265d893 [xemacs-hg @ 2005-02-04 03:04:04 by ben]
ben
parents: 968
diff changeset
10 use Help->XEmacs FAQ from the menu, or `C-h F'.
0
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
11
2564
d96db265d893 [xemacs-hg @ 2005-02-04 03:04:04 by ben]
ben
parents: 968
diff changeset
12 If you don't have XEmacs running and can't access the web,
d96db265d893 [xemacs-hg @ 2005-02-04 03:04:04 by ben]
ben
parents: 968
diff changeset
13 look directly at `man/xemacs-faq.texi' or `info/xemacs-faq.info'.
623
3e13cd716cff [xemacs-hg @ 2001-06-22 01:51:40 by ben]
ben
parents: 434
diff changeset
14
3e13cd716cff [xemacs-hg @ 2001-06-22 01:51:40 by ben]
ben
parents: 434
diff changeset
15