1
0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2024-12-12 09:28:24 +00:00
emacs/src/intervals.c

2629 lines
72 KiB
C
Raw Normal View History

1992-09-17 02:26:53 +00:00
/* Code for doing intervals.
Copyright (C) 1993, 1994, 1995, 1997, 1998, 2001, 2002, 2003, 2004,
2009-01-08 03:15:17 +00:00
2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
1992-09-17 02:26:53 +00:00
This file is part of GNU Emacs.
GNU Emacs is free software: you can redistribute it and/or modify
1992-09-17 02:26:53 +00:00
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.
1992-09-17 02:26:53 +00:00
GNU Emacs 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 GNU Emacs. If not, see <http://www.gnu.org/licenses/>. */
1992-09-17 02:26:53 +00:00
/* NOTES:
Have to ensure that we can't put symbol nil on a plist, or some
functions may work incorrectly.
An idea: Have the owner of the tree keep count of splits and/or
insertion lengths (in intervals), and balance after every N.
Need to call *_left_hook when buffer is killed.
Scan for zero-length, or 0-length to see notes about handling
zero length interval-markers.
There are comments around about freeing intervals. It might be
faster to explicitly free them (put them on the free list) than
to GC them.
*/
#include <config.h>
1992-09-17 02:26:53 +00:00
#include "lisp.h"
#include "intervals.h"
#include "buffer.h"
#include "puresize.h"
1994-09-19 00:12:39 +00:00
#include "keyboard.h"
2001-10-08 11:39:52 +00:00
#include "keymap.h"
1992-09-17 02:26:53 +00:00
/* Test for membership, allowing for t (actually any non-cons) to mean the
universal set. */
#define TMEM(sym, set) (CONSP (set) ? ! NILP (Fmemq (sym, set)) : ! NILP (set))
1993-11-25 07:47:14 +00:00
Lisp_Object merge_properties_sticky ();
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
static INTERVAL reproduce_tree P_ ((INTERVAL, INTERVAL));
static INTERVAL reproduce_tree_obj P_ ((INTERVAL, Lisp_Object));
1992-09-17 02:26:53 +00:00
/* Utility functions for intervals. */
1992-09-17 02:26:53 +00:00
/* Create the root interval of some object, a buffer or string. */
1992-09-17 02:26:53 +00:00
INTERVAL
create_root_interval (parent)
Lisp_Object parent;
{
INTERVAL new;
CHECK_IMPURE (parent);
new = make_interval ();
1992-09-17 02:26:53 +00:00
if (BUFFERP (parent))
1992-09-17 02:26:53 +00:00
{
new->total_length = (BUF_Z (XBUFFER (parent))
- BUF_BEG (XBUFFER (parent)));
CHECK_TOTAL_LENGTH (new);
BUF_INTERVALS (XBUFFER (parent)) = new;
new->position = BEG;
1992-09-17 02:26:53 +00:00
}
else if (STRINGP (parent))
1992-09-17 02:26:53 +00:00
{
new->total_length = SCHARS (parent);
CHECK_TOTAL_LENGTH (new);
STRING_SET_INTERVALS (parent, new);
new->position = 0;
1992-09-17 02:26:53 +00:00
}
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_OBJECT (new, parent);
1992-09-17 02:26:53 +00:00
return new;
}
/* Make the interval TARGET have exactly the properties of SOURCE */
void
copy_properties (source, target)
register INTERVAL source, target;
{
if (DEFAULT_INTERVAL_P (source) && DEFAULT_INTERVAL_P (target))
return;
COPY_INTERVAL_CACHE (source, target);
target->plist = Fcopy_sequence (source->plist);
}
/* Merge the properties of interval SOURCE into the properties
of interval TARGET. That is to say, each property in SOURCE
is added to TARGET if TARGET has no such property as yet. */
1992-09-17 02:26:53 +00:00
static void
merge_properties (source, target)
register INTERVAL source, target;
{
register Lisp_Object o, sym, val;
if (DEFAULT_INTERVAL_P (source) && DEFAULT_INTERVAL_P (target))
return;
MERGE_INTERVAL_CACHE (source, target);
o = source->plist;
while (CONSP (o))
1992-09-17 02:26:53 +00:00
{
sym = XCAR (o);
o = XCDR (o);
CHECK_CONS (o);
val = target->plist;
while (CONSP (val) && !EQ (XCAR (val), sym))
{
val = XCDR (val);
if (!CONSP (val))
break;
val = XCDR (val);
}
1992-09-17 02:26:53 +00:00
if (NILP (val))
{
val = XCAR (o);
1992-09-17 02:26:53 +00:00
target->plist = Fcons (sym, Fcons (val, target->plist));
}
o = XCDR (o);
1992-09-17 02:26:53 +00:00
}
}
/* Return 1 if the two intervals have the same properties,
0 otherwise. */
1992-09-17 02:26:53 +00:00
int
intervals_equal (i0, i1)
INTERVAL i0, i1;
{
register Lisp_Object i0_cdr, i0_sym;
register Lisp_Object i1_cdr, i1_val;
1992-09-17 02:26:53 +00:00
if (DEFAULT_INTERVAL_P (i0) && DEFAULT_INTERVAL_P (i1))
return 1;
if (DEFAULT_INTERVAL_P (i0) || DEFAULT_INTERVAL_P (i1))
return 0;
1992-09-17 02:26:53 +00:00
i0_cdr = i0->plist;
i1_cdr = i1->plist;
while (CONSP (i0_cdr) && CONSP (i1_cdr))
1992-09-17 02:26:53 +00:00
{
i0_sym = XCAR (i0_cdr);
i0_cdr = XCDR (i0_cdr);
if (!CONSP (i0_cdr))
return 0; /* abort (); */
i1_val = i1->plist;
while (CONSP (i1_val) && !EQ (XCAR (i1_val), i0_sym))
{
i1_val = XCDR (i1_val);
if (!CONSP (i1_val))
return 0; /* abort (); */
i1_val = XCDR (i1_val);
}
1992-09-17 02:26:53 +00:00
/* i0 has something i1 doesn't. */
1992-09-17 02:26:53 +00:00
if (EQ (i1_val, Qnil))
return 0;
/* i0 and i1 both have sym, but it has different values in each. */
if (!CONSP (i1_val)
|| (i1_val = XCDR (i1_val), !CONSP (i1_val))
|| !EQ (XCAR (i1_val), XCAR (i0_cdr)))
1992-09-17 02:26:53 +00:00
return 0;
i0_cdr = XCDR (i0_cdr);
1992-09-17 02:26:53 +00:00
i1_cdr = XCDR (i1_cdr);
if (!CONSP (i1_cdr))
return 0; /* abort (); */
i1_cdr = XCDR (i1_cdr);
}
1992-09-17 02:26:53 +00:00
/* Lengths of the two plists were equal. */
return (NILP (i0_cdr) && NILP (i1_cdr));
1992-09-17 02:26:53 +00:00
}
/* Traverse an interval tree TREE, performing FUNCTION on each node.
No guarantee is made about the order of traversal.
Pass FUNCTION two args: an interval, and ARG. */
void
traverse_intervals_noorder (tree, function, arg)
INTERVAL tree;
void (* function) P_ ((INTERVAL, Lisp_Object));
Lisp_Object arg;
{
/* Minimize stack usage. */
while (!NULL_INTERVAL_P (tree))
{
(*function) (tree, arg);
if (NULL_INTERVAL_P (tree->right))
tree = tree->left;
else
{
traverse_intervals_noorder (tree->left, function, arg);
tree = tree->right;
}
}
}
1992-09-17 02:26:53 +00:00
/* Traverse an interval tree TREE, performing FUNCTION on each node.
1993-02-25 20:24:43 +00:00
Pass FUNCTION two args: an interval, and ARG. */
1992-09-17 02:26:53 +00:00
void
traverse_intervals (tree, position, function, arg)
1992-09-17 02:26:53 +00:00
INTERVAL tree;
int position;
void (* function) P_ ((INTERVAL, Lisp_Object));
1993-02-25 20:24:43 +00:00
Lisp_Object arg;
1992-09-17 02:26:53 +00:00
{
while (!NULL_INTERVAL_P (tree))
{
traverse_intervals (tree->left, position, function, arg);
position += LEFT_TOTAL_LENGTH (tree);
tree->position = position;
(*function) (tree, arg);
position += LENGTH (tree); tree = tree->right;
}
1992-09-17 02:26:53 +00:00
}
#if 0
static int icount;
static int idepth;
static int zero_length;
/* These functions are temporary, for debugging purposes only. */
1992-09-17 02:26:53 +00:00
INTERVAL search_interval, found_interval;
void
check_for_interval (i)
register INTERVAL i;
{
if (i == search_interval)
{
found_interval = i;
icount++;
}
}
INTERVAL
search_for_interval (i, tree)
register INTERVAL i, tree;
{
icount = 0;
search_interval = i;
found_interval = NULL_INTERVAL;
traverse_intervals_noorder (tree, &check_for_interval, Qnil);
1992-09-17 02:26:53 +00:00
return found_interval;
}
static void
inc_interval_count (i)
INTERVAL i;
{
icount++;
if (LENGTH (i) == 0)
zero_length++;
if (depth > idepth)
idepth = depth;
}
int
count_intervals (i)
register INTERVAL i;
{
icount = 0;
idepth = 0;
zero_length = 0;
traverse_intervals_noorder (i, &inc_interval_count, Qnil);
1992-09-17 02:26:53 +00:00
return icount;
}
static INTERVAL
root_interval (interval)
INTERVAL interval;
{
register INTERVAL i = interval;
while (! ROOT_INTERVAL_P (i))
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
i = INTERVAL_PARENT (i);
1992-09-17 02:26:53 +00:00
return i;
}
#endif
/* Assuming that a left child exists, perform the following operation:
A B
/ \ / \
B => A
/ \ / \
c c
*/
static INLINE INTERVAL
1992-09-17 02:26:53 +00:00
rotate_right (interval)
INTERVAL interval;
{
INTERVAL i;
INTERVAL B = interval->left;
int old_total = interval->total_length;
1992-09-17 02:26:53 +00:00
/* Deal with any Parent of A; make it point to B. */
1992-09-17 02:26:53 +00:00
if (! ROOT_INTERVAL_P (interval))
{
if (AM_LEFT_CHILD (interval))
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
INTERVAL_PARENT (interval)->left = B;
else
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
INTERVAL_PARENT (interval)->right = B;
}
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
COPY_INTERVAL_PARENT (B, interval);
1992-09-17 02:26:53 +00:00
/* Make B the parent of A */
i = B->right;
B->right = interval;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (interval, B);
1992-09-17 02:26:53 +00:00
/* Make A point to c */
1992-09-17 02:26:53 +00:00
interval->left = i;
if (! NULL_INTERVAL_P (i))
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (i, interval);
/* A's total length is decreased by the length of B and its left child. */
interval->total_length -= B->total_length - LEFT_TOTAL_LENGTH (interval);
CHECK_TOTAL_LENGTH (interval);
/* B must have the same total length of A. */
B->total_length = old_total;
CHECK_TOTAL_LENGTH (B);
1992-09-17 02:26:53 +00:00
return B;
}
1992-09-17 02:26:53 +00:00
/* Assuming that a right child exists, perform the following operation:
2002-10-18 10:09:43 +00:00
A B
/ \ / \
1992-09-17 02:26:53 +00:00
B => A
2002-10-18 10:09:43 +00:00
/ \ / \
1992-09-17 02:26:53 +00:00
c c
*/
static INLINE INTERVAL
1992-09-17 02:26:53 +00:00
rotate_left (interval)
INTERVAL interval;
{
INTERVAL i;
INTERVAL B = interval->right;
int old_total = interval->total_length;
1992-09-17 02:26:53 +00:00
/* Deal with any parent of A; make it point to B. */
1992-09-17 02:26:53 +00:00
if (! ROOT_INTERVAL_P (interval))
{
if (AM_LEFT_CHILD (interval))
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
INTERVAL_PARENT (interval)->left = B;
else
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
INTERVAL_PARENT (interval)->right = B;
}
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
COPY_INTERVAL_PARENT (B, interval);
1992-09-17 02:26:53 +00:00
/* Make B the parent of A */
i = B->left;
B->left = interval;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (interval, B);
1992-09-17 02:26:53 +00:00
/* Make A point to c */
interval->right = i;
if (! NULL_INTERVAL_P (i))
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (i, interval);
/* A's total length is decreased by the length of B and its right child. */
interval->total_length -= B->total_length - RIGHT_TOTAL_LENGTH (interval);
CHECK_TOTAL_LENGTH (interval);
/* B must have the same total length of A. */
B->total_length = old_total;
CHECK_TOTAL_LENGTH (B);
1992-09-17 02:26:53 +00:00
return B;
}
/* Balance an interval tree with the assumption that the subtrees
themselves are already balanced. */
static INTERVAL
balance_an_interval (i)
INTERVAL i;
{
register int old_diff, new_diff;
while (1)
{
old_diff = LEFT_TOTAL_LENGTH (i) - RIGHT_TOTAL_LENGTH (i);
if (old_diff > 0)
{
/* Since the left child is longer, there must be one. */
new_diff = i->total_length - i->left->total_length
+ RIGHT_TOTAL_LENGTH (i->left) - LEFT_TOTAL_LENGTH (i->left);
2007-10-13 12:48:57 +00:00
if (eabs (new_diff) >= old_diff)
break;
i = rotate_right (i);
balance_an_interval (i->right);
}
else if (old_diff < 0)
{
/* Since the right child is longer, there must be one. */
new_diff = i->total_length - i->right->total_length
+ LEFT_TOTAL_LENGTH (i->right) - RIGHT_TOTAL_LENGTH (i->right);
2007-10-13 12:48:57 +00:00
if (eabs (new_diff) >= -old_diff)
break;
i = rotate_left (i);
balance_an_interval (i->left);
}
else
break;
}
return i;
}
/* Balance INTERVAL, potentially stuffing it back into its parent
Lisp Object. */
static INLINE INTERVAL
balance_possible_root_interval (interval)
register INTERVAL interval;
{
Lisp_Object parent;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
int have_parent = 0;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
if (!INTERVAL_HAS_OBJECT (interval) && !INTERVAL_HAS_PARENT (interval))
return interval;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
if (INTERVAL_HAS_OBJECT (interval))
{
have_parent = 1;
GET_INTERVAL_OBJECT (parent, interval);
}
interval = balance_an_interval (interval);
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
if (have_parent)
{
if (BUFFERP (parent))
BUF_INTERVALS (XBUFFER (parent)) = interval;
else if (STRINGP (parent))
STRING_SET_INTERVALS (parent, interval);
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
}
return interval;
}
/* Balance the interval tree TREE. Balancing is by weight
(the amount of text). */
static INTERVAL
balance_intervals_internal (tree)
register INTERVAL tree;
{
/* Balance within each side. */
if (tree->left)
balance_intervals_internal (tree->left);
if (tree->right)
balance_intervals_internal (tree->right);
return balance_an_interval (tree);
}
/* Advertised interface to balance intervals. */
INTERVAL
balance_intervals (tree)
INTERVAL tree;
{
if (tree == NULL_INTERVAL)
return NULL_INTERVAL;
return balance_intervals_internal (tree);
}
/* Split INTERVAL into two pieces, starting the second piece at
character position OFFSET (counting from 0), relative to INTERVAL.
INTERVAL becomes the left-hand piece, and the right-hand piece
(second, lexicographically) is returned.
1992-09-19 01:11:21 +00:00
The size and position fields of the two intervals are set based upon
those of the original interval. The property list of the new interval
is reset, thus it is up to the caller to do the right thing with the
result.
1992-09-17 02:26:53 +00:00
Note that this does not change the position of INTERVAL; if it is a root,
it is still a root after this operation. */
1992-09-17 02:26:53 +00:00
INTERVAL
1992-09-19 01:11:21 +00:00
split_interval_right (interval, offset)
1992-09-17 02:26:53 +00:00
INTERVAL interval;
1992-09-19 01:11:21 +00:00
int offset;
1992-09-17 02:26:53 +00:00
{
INTERVAL new = make_interval ();
int position = interval->position;
int new_length = LENGTH (interval) - offset;
1992-09-17 02:26:53 +00:00
new->position = position + offset;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (new, interval);
1992-09-17 02:26:53 +00:00
if (NULL_RIGHT_CHILD (interval))
1992-09-17 02:26:53 +00:00
{
interval->right = new;
new->total_length = new_length;
CHECK_TOTAL_LENGTH (new);
1992-09-17 02:26:53 +00:00
}
else
{
/* Insert the new node between INTERVAL and its right child. */
new->right = interval->right;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (interval->right, new);
interval->right = new;
new->total_length = new_length + new->right->total_length;
CHECK_TOTAL_LENGTH (new);
balance_an_interval (new);
}
2002-10-18 10:09:43 +00:00
balance_possible_root_interval (interval);
1992-09-17 02:26:53 +00:00
return new;
}
/* Split INTERVAL into two pieces, starting the second piece at
character position OFFSET (counting from 0), relative to INTERVAL.
INTERVAL becomes the right-hand piece, and the left-hand piece
(first, lexicographically) is returned.
1992-09-17 02:26:53 +00:00
1992-09-19 01:11:21 +00:00
The size and position fields of the two intervals are set based upon
those of the original interval. The property list of the new interval
is reset, thus it is up to the caller to do the right thing with the
result.
Note that this does not change the position of INTERVAL; if it is a root,
it is still a root after this operation. */
1992-09-17 02:26:53 +00:00
INTERVAL
1992-09-19 01:11:21 +00:00
split_interval_left (interval, offset)
1992-09-17 02:26:53 +00:00
INTERVAL interval;
1992-09-19 01:11:21 +00:00
int offset;
1992-09-17 02:26:53 +00:00
{
INTERVAL new = make_interval ();
int new_length = offset;
1992-09-17 02:26:53 +00:00
new->position = interval->position;
interval->position = interval->position + offset;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (new, interval);
1992-09-17 02:26:53 +00:00
if (NULL_LEFT_CHILD (interval))
{
interval->left = new;
new->total_length = new_length;
CHECK_TOTAL_LENGTH (new);
1992-09-17 02:26:53 +00:00
}
else
{
/* Insert the new node between INTERVAL and its left child. */
new->left = interval->left;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (new->left, new);
interval->left = new;
new->total_length = new_length + new->left->total_length;
CHECK_TOTAL_LENGTH (new);
balance_an_interval (new);
}
2002-10-18 10:09:43 +00:00
balance_possible_root_interval (interval);
1992-09-17 02:26:53 +00:00
return new;
}
/* Return the proper position for the first character
described by the interval tree SOURCE.
This is 1 if the parent is a buffer,
0 if the parent is a string or if there is no parent.
Don't use this function on an interval which is the child
of another interval! */
int
interval_start_pos (source)
INTERVAL source;
{
Lisp_Object parent;
if (NULL_INTERVAL_P (source))
return 0;
if (! INTERVAL_HAS_OBJECT (source))
return 0;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
GET_INTERVAL_OBJECT (parent, source);
if (BUFFERP (parent))
return BUF_BEG (XBUFFER (parent));
return 0;
}
1992-09-19 01:11:21 +00:00
/* Find the interval containing text position POSITION in the text
represented by the interval tree TREE. POSITION is a buffer
position (starting from 1) or a string index (starting from 0).
If POSITION is at the end of the buffer or string,
return the interval containing the last character.
1992-09-17 02:26:53 +00:00
1992-09-19 01:11:21 +00:00
The `position' field, which is a cache of an interval's position,
is updated in the interval found. Other functions (e.g., next_interval)
will update this cache based on the result of find_interval. */
1992-09-19 01:11:21 +00:00
1997-06-02 18:30:21 +00:00
INTERVAL
1992-09-17 02:26:53 +00:00
find_interval (tree, position)
register INTERVAL tree;
register int position;
{
/* The distance from the left edge of the subtree at TREE
to POSITION. */
register int relative_position;
1992-09-17 02:26:53 +00:00
if (NULL_INTERVAL_P (tree))
return NULL_INTERVAL;
relative_position = position;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
if (INTERVAL_HAS_OBJECT (tree))
{
Lisp_Object parent;
GET_INTERVAL_OBJECT (parent, tree);
if (BUFFERP (parent))
relative_position -= BUF_BEG (XBUFFER (parent));
}
if (relative_position > TOTAL_LENGTH (tree))
1992-09-17 02:26:53 +00:00
abort (); /* Paranoia */
if (!handling_signal)
tree = balance_possible_root_interval (tree);
1992-09-17 02:26:53 +00:00
while (1)
{
if (relative_position < LEFT_TOTAL_LENGTH (tree))
1992-09-17 02:26:53 +00:00
{
tree = tree->left;
}
else if (! NULL_RIGHT_CHILD (tree)
&& relative_position >= (TOTAL_LENGTH (tree)
- RIGHT_TOTAL_LENGTH (tree)))
1992-09-17 02:26:53 +00:00
{
relative_position -= (TOTAL_LENGTH (tree)
- RIGHT_TOTAL_LENGTH (tree));
tree = tree->right;
}
else
{
tree->position
= (position - relative_position /* left edge of *tree. */
+ LEFT_TOTAL_LENGTH (tree)); /* left edge of this interval. */
1992-09-17 02:26:53 +00:00
return tree;
}
}
}
/* Find the succeeding interval (lexicographically) to INTERVAL.
1992-09-19 01:11:21 +00:00
Sets the `position' field based on that of INTERVAL (see
find_interval). */
1992-09-17 02:26:53 +00:00
INTERVAL
next_interval (interval)
register INTERVAL interval;
{
register INTERVAL i = interval;
register int next_position;
if (NULL_INTERVAL_P (i))
return NULL_INTERVAL;
next_position = interval->position + LENGTH (interval);
if (! NULL_RIGHT_CHILD (i))
{
i = i->right;
while (! NULL_LEFT_CHILD (i))
i = i->left;
i->position = next_position;
return i;
}
while (! NULL_PARENT (i))
{
if (AM_LEFT_CHILD (i))
{
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
i = INTERVAL_PARENT (i);
1992-09-17 02:26:53 +00:00
i->position = next_position;
return i;
}
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
i = INTERVAL_PARENT (i);
1992-09-17 02:26:53 +00:00
}
return NULL_INTERVAL;
}
/* Find the preceding interval (lexicographically) to INTERVAL.
1992-09-19 01:11:21 +00:00
Sets the `position' field based on that of INTERVAL (see
find_interval). */
1992-09-17 02:26:53 +00:00
INTERVAL
previous_interval (interval)
register INTERVAL interval;
{
register INTERVAL i;
if (NULL_INTERVAL_P (interval))
return NULL_INTERVAL;
if (! NULL_LEFT_CHILD (interval))
{
i = interval->left;
while (! NULL_RIGHT_CHILD (i))
i = i->right;
i->position = interval->position - LENGTH (i);
return i;
}
i = interval;
while (! NULL_PARENT (i))
{
if (AM_RIGHT_CHILD (i))
{
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
i = INTERVAL_PARENT (i);
1992-09-17 02:26:53 +00:00
i->position = interval->position - LENGTH (i);
return i;
}
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
i = INTERVAL_PARENT (i);
1992-09-17 02:26:53 +00:00
}
return NULL_INTERVAL;
}
1997-04-15 04:45:26 +00:00
/* Find the interval containing POS given some non-NULL INTERVAL
in the same tree. Note that we need to update interval->position
if we go down the tree.
To speed up the process, we assume that the ->position of
I and all its parents is already uptodate. */
1997-04-15 04:45:26 +00:00
INTERVAL
update_interval (i, pos)
register INTERVAL i;
int pos;
{
if (NULL_INTERVAL_P (i))
return NULL_INTERVAL;
2002-10-18 10:09:43 +00:00
while (1)
1997-04-15 04:45:26 +00:00
{
2002-10-18 10:09:43 +00:00
if (pos < i->position)
1997-04-15 04:45:26 +00:00
{
/* Move left. */
2002-10-18 10:09:43 +00:00
if (pos >= i->position - TOTAL_LENGTH (i->left))
{
i->left->position = i->position - TOTAL_LENGTH (i->left)
+ LEFT_TOTAL_LENGTH (i->left);
i = i->left; /* Move to the left child */
}
2002-10-18 10:09:43 +00:00
else if (NULL_PARENT (i))
1997-04-15 04:45:26 +00:00
error ("Point before start of properties");
2002-10-18 10:09:43 +00:00
else
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
i = INTERVAL_PARENT (i);
1997-04-15 04:45:26 +00:00
continue;
}
else if (pos >= INTERVAL_LAST_POS (i))
{
/* Move right. */
2002-10-18 10:09:43 +00:00
if (pos < INTERVAL_LAST_POS (i) + TOTAL_LENGTH (i->right))
{
i->right->position = INTERVAL_LAST_POS (i)
+ LEFT_TOTAL_LENGTH (i->right);
i = i->right; /* Move to the right child */
}
2002-10-18 10:09:43 +00:00
else if (NULL_PARENT (i))
error ("Point %d after end of properties", pos);
2002-10-18 10:09:43 +00:00
else
i = INTERVAL_PARENT (i);
1997-04-15 04:45:26 +00:00
continue;
}
2002-10-18 10:09:43 +00:00
else
1997-04-15 04:45:26 +00:00
return i;
}
}
1992-09-17 02:26:53 +00:00
1992-09-19 01:11:21 +00:00
#if 0
1992-09-17 02:26:53 +00:00
/* Traverse a path down the interval tree TREE to the interval
containing POSITION, adjusting all nodes on the path for
an addition of LENGTH characters. Insertion between two intervals
(i.e., point == i->position, where i is second interval) means
text goes into second interval.
Modifications are needed to handle the hungry bits -- after simply
finding the interval at position (don't add length going down),
if it's the beginning of the interval, get the previous interval
1996-01-05 10:03:17 +00:00
and check the hungry bits of both. Then add the length going back up
to the root. */
1992-09-17 02:26:53 +00:00
static INTERVAL
adjust_intervals_for_insertion (tree, position, length)
INTERVAL tree;
int position, length;
{
register int relative_position;
register INTERVAL this;
if (TOTAL_LENGTH (tree) == 0) /* Paranoia */
abort ();
/* If inserting at point-max of a buffer, that position
will be out of range */
if (position > TOTAL_LENGTH (tree))
position = TOTAL_LENGTH (tree);
relative_position = position;
this = tree;
while (1)
{
if (relative_position <= LEFT_TOTAL_LENGTH (this))
{
this->total_length += length;
CHECK_TOTAL_LENGTH (this);
1992-09-17 02:26:53 +00:00
this = this->left;
}
else if (relative_position > (TOTAL_LENGTH (this)
- RIGHT_TOTAL_LENGTH (this)))
{
relative_position -= (TOTAL_LENGTH (this)
- RIGHT_TOTAL_LENGTH (this));
this->total_length += length;
CHECK_TOTAL_LENGTH (this);
1992-09-17 02:26:53 +00:00
this = this->right;
}
else
{
/* If we are to use zero-length intervals as buffer pointers,
then this code will have to change. */
1992-09-17 02:26:53 +00:00
this->total_length += length;
CHECK_TOTAL_LENGTH (this);
1992-09-17 02:26:53 +00:00
this->position = LEFT_TOTAL_LENGTH (this)
+ position - relative_position + 1;
return tree;
}
}
}
1992-09-19 01:11:21 +00:00
#endif
/* Effect an adjustment corresponding to the addition of LENGTH characters
of text. Do this by finding the interval containing POSITION in the
interval tree TREE, and then adjusting all of its ancestors by adding
1992-09-19 01:11:21 +00:00
LENGTH to them.
If POSITION is the first character of an interval, meaning that point
is actually between the two intervals, make the new text belong to
the interval which is "sticky".
1992-09-21 23:57:58 +00:00
If both intervals are "sticky", then make them belong to the left-most
1992-09-19 01:11:21 +00:00
interval. Another possibility would be to create a new interval for
this text, and make it have the merged properties of both ends. */
1992-09-19 01:11:21 +00:00
static INTERVAL
adjust_intervals_for_insertion (tree, position, length)
INTERVAL tree;
int position, length;
{
register INTERVAL i;
register INTERVAL temp;
int eobp = 0;
Lisp_Object parent;
int offset;
2002-10-18 10:09:43 +00:00
1992-09-19 01:11:21 +00:00
if (TOTAL_LENGTH (tree) == 0) /* Paranoia */
abort ();
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
GET_INTERVAL_OBJECT (parent, tree);
offset = (BUFFERP (parent) ? BUF_BEG (XBUFFER (parent)) : 0);
/* If inserting at point-max of a buffer, that position will be out
of range. Remember that buffer positions are 1-based. */
if (position >= TOTAL_LENGTH (tree) + offset)
{
position = TOTAL_LENGTH (tree) + offset;
eobp = 1;
}
1992-09-19 01:11:21 +00:00
i = find_interval (tree, position);
/* If in middle of an interval which is not sticky either way,
we must not just give its properties to the insertion.
So split this interval at the insertion point.
Originally, the if condition here was this:
(! (position == i->position || eobp)
&& END_NONSTICKY_P (i)
&& FRONT_NONSTICKY_P (i))
But, these macros are now unreliable because of introduction of
Vtext_property_default_nonsticky. So, we always check properties
one by one if POSITION is in middle of an interval. */
if (! (position == i->position || eobp))
{
Lisp_Object tail;
Lisp_Object front, rear;
tail = i->plist;
/* Properties font-sticky and rear-nonsticky override
Vtext_property_default_nonsticky. So, if they are t, we can
skip one by one checking of properties. */
rear = textget (i->plist, Qrear_nonsticky);
if (! CONSP (rear) && ! NILP (rear))
{
/* All properties are nonsticky. We split the interval. */
goto check_done;
}
front = textget (i->plist, Qfront_sticky);
if (! CONSP (front) && ! NILP (front))
{
/* All properties are sticky. We don't split the interval. */
tail = Qnil;
goto check_done;
}
/* Does any actual property pose an actual problem? We break
the loop if we find a nonsticky property. */
for (; CONSP (tail); tail = Fcdr (XCDR (tail)))
{
Lisp_Object prop, tmp;
prop = XCAR (tail);
/* Is this particular property front-sticky? */
if (CONSP (front) && ! NILP (Fmemq (prop, front)))
continue;
/* Is this particular property rear-nonsticky? */
if (CONSP (rear) && ! NILP (Fmemq (prop, rear)))
break;
/* Is this particular property recorded as sticky or
nonsticky in Vtext_property_default_nonsticky? */
tmp = Fassq (prop, Vtext_property_default_nonsticky);
if (CONSP (tmp))
{
if (NILP (tmp))
continue;
break;
}
/* By default, a text property is rear-sticky, thus we
continue the loop. */
}
check_done:
/* If any property is a real problem, split the interval. */
if (! NILP (tail))
{
temp = split_interval_right (i, position - i->position);
copy_properties (i, temp);
i = temp;
}
}
1992-09-19 01:11:21 +00:00
/* If we are positioned between intervals, check the stickiness of
both of them. We have to do this too, if we are at BEG or Z. */
if (position == i->position || eobp)
1992-09-19 01:11:21 +00:00
{
register INTERVAL prev;
if (position == BEG)
prev = 0;
else if (eobp)
{
prev = i;
i = 0;
}
else
prev = previous_interval (i);
1992-09-19 01:11:21 +00:00
/* Even if we are positioned between intervals, we default
to the left one if it exists. We extend it now and split
1996-01-05 10:03:17 +00:00
off a part later, if stickiness demands it. */
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
for (temp = prev ? prev : i; temp; temp = INTERVAL_PARENT_OR_NULL (temp))
{
temp->total_length += length;
CHECK_TOTAL_LENGTH (temp);
temp = balance_possible_root_interval (temp);
}
2002-10-18 10:09:43 +00:00
/* If at least one interval has sticky properties,
we check the stickiness property by property.
Originally, the if condition here was this:
(END_NONSTICKY_P (prev) || FRONT_STICKY_P (i))
But, these macros are now unreliable because of introduction
of Vtext_property_default_nonsticky. So, we always have to
check stickiness of properties one by one. If cache of
stickiness is implemented in the future, we may be able to
use those macros again. */
if (1)
{
Lisp_Object pleft, pright;
struct interval newi;
pleft = NULL_INTERVAL_P (prev) ? Qnil : prev->plist;
pright = NULL_INTERVAL_P (i) ? Qnil : i->plist;
newi.plist = merge_properties_sticky (pleft, pright);
if (! prev) /* i.e. position == BEG */
{
if (! intervals_equal (i, &newi))
{
i = split_interval_left (i, length);
i->plist = newi.plist;
}
}
else if (! intervals_equal (prev, &newi))
{
prev = split_interval_right (prev,
position - prev->position);
prev->plist = newi.plist;
if (! NULL_INTERVAL_P (i)
&& intervals_equal (prev, i))
merge_interval_right (prev);
}
/* We will need to update the cache here later. */
}
else if (! prev && ! NILP (i->plist))
{
/* Just split off a new interval at the left.
Since I wasn't front-sticky, the empty plist is ok. */
i = split_interval_left (i, length);
}
1992-09-19 01:11:21 +00:00
}
/* Otherwise just extend the interval. */
else
1992-09-19 01:11:21 +00:00
{
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
for (temp = i; temp; temp = INTERVAL_PARENT_OR_NULL (temp))
{
temp->total_length += length;
CHECK_TOTAL_LENGTH (temp);
temp = balance_possible_root_interval (temp);
}
1992-09-19 01:11:21 +00:00
}
2002-10-18 10:09:43 +00:00
1992-09-19 01:11:21 +00:00
return tree;
}
/* Any property might be front-sticky on the left, rear-sticky on the left,
front-sticky on the right, or rear-sticky on the right; the 16 combinations
can be arranged in a matrix with rows denoting the left conditions and
columns denoting the right conditions:
_ __ _
_ FR FR FR FR
FR__ 0 1 2 3
_FR 4 5 6 7
FR 8 9 A B
FR C D E F
left-props = '(front-sticky (p8 p9 pa pb pc pd pe pf)
rear-nonsticky (p4 p5 p6 p7 p8 p9 pa pb)
p0 L p1 L p2 L p3 L p4 L p5 L p6 L p7 L
p8 L p9 L pa L pb L pc L pd L pe L pf L)
right-props = '(front-sticky (p2 p3 p6 p7 pa pb pe pf)
rear-nonsticky (p1 p2 p5 p6 p9 pa pd pe)
p0 R p1 R p2 R p3 R p4 R p5 R p6 R p7 R
p8 R p9 R pa R pb R pc R pd R pe R pf R)
We inherit from whoever has a sticky side facing us. If both sides
do (cases 2, 3, E, and F), then we inherit from whichever side has a
non-nil value for the current property. If both sides do, then we take
from the left.
When we inherit a property, we get its stickiness as well as its value.
So, when we merge the above two lists, we expect to get this:
result = '(front-sticky (p6 p7 pa pb pc pd pe pf)
rear-nonsticky (p6 pa)
p0 L p1 L p2 L p3 L p6 R p7 R
pa R pb R pc L pd L pe L pf L)
The optimizable special cases are:
left rear-nonsticky = nil, right front-sticky = nil (inherit left)
left rear-nonsticky = t, right front-sticky = t (inherit right)
left rear-nonsticky = t, right front-sticky = nil (inherit none)
*/
Lisp_Object
merge_properties_sticky (pleft, pright)
Lisp_Object pleft, pright;
{
register Lisp_Object props, front, rear;
Lisp_Object lfront, lrear, rfront, rrear;
register Lisp_Object tail1, tail2, sym, lval, rval, cat;
int use_left, use_right;
int lpresent;
props = Qnil;
front = Qnil;
rear = Qnil;
lfront = textget (pleft, Qfront_sticky);
lrear = textget (pleft, Qrear_nonsticky);
rfront = textget (pright, Qfront_sticky);
rrear = textget (pright, Qrear_nonsticky);
/* Go through each element of PRIGHT. */
for (tail1 = pright; CONSP (tail1); tail1 = Fcdr (XCDR (tail1)))
{
Lisp_Object tmp;
sym = XCAR (tail1);
/* Sticky properties get special treatment. */
if (EQ (sym, Qrear_nonsticky) || EQ (sym, Qfront_sticky))
continue;
rval = Fcar (XCDR (tail1));
for (tail2 = pleft; CONSP (tail2); tail2 = Fcdr (XCDR (tail2)))
if (EQ (sym, XCAR (tail2)))
break;
/* Indicate whether the property is explicitly defined on the left.
(We know it is defined explicitly on the right
because otherwise we don't get here.) */
lpresent = ! NILP (tail2);
lval = (NILP (tail2) ? Qnil : Fcar (Fcdr (tail2)));
/* Even if lrear or rfront say nothing about the stickiness of
SYM, Vtext_property_default_nonsticky may give default
stickiness to SYM. */
tmp = Fassq (sym, Vtext_property_default_nonsticky);
use_left = (lpresent
&& ! (TMEM (sym, lrear)
2001-12-09 01:03:22 +00:00
|| (CONSP (tmp) && ! NILP (XCDR (tmp)))));
use_right = (TMEM (sym, rfront)
|| (CONSP (tmp) && NILP (XCDR (tmp))));
if (use_left && use_right)
{
if (NILP (lval))
use_left = 0;
else if (NILP (rval))
use_right = 0;
}
if (use_left)
{
/* We build props as (value sym ...) rather than (sym value ...)
because we plan to nreverse it when we're done. */
props = Fcons (lval, Fcons (sym, props));
if (TMEM (sym, lfront))
front = Fcons (sym, front);
if (TMEM (sym, lrear))
rear = Fcons (sym, rear);
}
else if (use_right)
{
props = Fcons (rval, Fcons (sym, props));
if (TMEM (sym, rfront))
front = Fcons (sym, front);
if (TMEM (sym, rrear))
rear = Fcons (sym, rear);
}
}
/* Now go through each element of PLEFT. */
for (tail2 = pleft; CONSP (tail2); tail2 = Fcdr (XCDR (tail2)))
{
Lisp_Object tmp;
sym = XCAR (tail2);
/* Sticky properties get special treatment. */
if (EQ (sym, Qrear_nonsticky) || EQ (sym, Qfront_sticky))
continue;
/* If sym is in PRIGHT, we've already considered it. */
for (tail1 = pright; CONSP (tail1); tail1 = Fcdr (XCDR (tail1)))
if (EQ (sym, XCAR (tail1)))
break;
if (! NILP (tail1))
continue;
lval = Fcar (XCDR (tail2));
/* Even if lrear or rfront say nothing about the stickiness of
SYM, Vtext_property_default_nonsticky may give default
stickiness to SYM. */
tmp = Fassq (sym, Vtext_property_default_nonsticky);
/* Since rval is known to be nil in this loop, the test simplifies. */
if (! (TMEM (sym, lrear) || (CONSP (tmp) && ! NILP (XCDR (tmp)))))
{
props = Fcons (lval, Fcons (sym, props));
if (TMEM (sym, lfront))
front = Fcons (sym, front);
}
else if (TMEM (sym, rfront) || (CONSP (tmp) && NILP (XCDR (tmp))))
{
/* The value is nil, but we still inherit the stickiness
from the right. */
front = Fcons (sym, front);
if (TMEM (sym, rrear))
rear = Fcons (sym, rear);
}
}
props = Fnreverse (props);
if (! NILP (rear))
props = Fcons (Qrear_nonsticky, Fcons (Fnreverse (rear), props));
cat = textget (props, Qcategory);
if (! NILP (front)
2002-10-18 10:09:43 +00:00
&&
/* If we have inherited a front-stick category property that is t,
we don't need to set up a detailed one. */
! (! NILP (cat) && SYMBOLP (cat)
&& EQ (Fget (cat, Qfront_sticky), Qt)))
props = Fcons (Qfront_sticky, Fcons (Fnreverse (front), props));
return props;
}
1992-09-17 02:26:53 +00:00
2002-10-18 10:09:43 +00:00
/* Delete a node I from its interval tree by merging its subtrees
1992-09-19 01:11:21 +00:00
into one subtree which is then returned. Caller is responsible for
storing the resulting subtree into its parent. */
1992-09-17 02:26:53 +00:00
static INTERVAL
delete_node (i)
register INTERVAL i;
{
register INTERVAL migrate, this;
register int migrate_amt;
if (NULL_INTERVAL_P (i->left))
return i->right;
if (NULL_INTERVAL_P (i->right))
return i->left;
migrate = i->left;
migrate_amt = i->left->total_length;
this = i->right;
this->total_length += migrate_amt;
while (! NULL_INTERVAL_P (this->left))
{
this = this->left;
this->total_length += migrate_amt;
}
CHECK_TOTAL_LENGTH (this);
1992-09-17 02:26:53 +00:00
this->left = migrate;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (migrate, this);
1992-09-17 02:26:53 +00:00
return i->right;
}
/* Delete interval I from its tree by calling `delete_node'
and properly connecting the resultant subtree.
I is presumed to be empty; that is, no adjustments are made
for the length of I. */
1992-09-17 02:26:53 +00:00
void
delete_interval (i)
register INTERVAL i;
{
register INTERVAL parent;
int amt = LENGTH (i);
if (amt > 0) /* Only used on zero-length intervals now. */
1992-09-17 02:26:53 +00:00
abort ();
if (ROOT_INTERVAL_P (i))
{
Lisp_Object owner;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
GET_INTERVAL_OBJECT (owner, i);
1992-09-17 02:26:53 +00:00
parent = delete_node (i);
if (! NULL_INTERVAL_P (parent))
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_OBJECT (parent, owner);
1992-09-17 02:26:53 +00:00
if (BUFFERP (owner))
BUF_INTERVALS (XBUFFER (owner)) = parent;
else if (STRINGP (owner))
STRING_SET_INTERVALS (owner, parent);
1992-09-17 02:26:53 +00:00
else
abort ();
return;
}
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
parent = INTERVAL_PARENT (i);
1992-09-17 02:26:53 +00:00
if (AM_LEFT_CHILD (i))
{
parent->left = delete_node (i);
if (! NULL_INTERVAL_P (parent->left))
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (parent->left, parent);
1992-09-17 02:26:53 +00:00
}
else
{
parent->right = delete_node (i);
if (! NULL_INTERVAL_P (parent->right))
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (parent->right, parent);
1992-09-17 02:26:53 +00:00
}
}
/* Find the interval in TREE corresponding to the relative position
FROM and delete as much as possible of AMOUNT from that interval.
Return the amount actually deleted, and if the interval was
zeroed-out, delete that interval node from the tree.
Note that FROM is actually origin zero, aka relative to the
leftmost edge of tree. This is appropriate since we call ourselves
recursively on subtrees.
1992-09-17 02:26:53 +00:00
1992-09-21 23:57:58 +00:00
Do this by recursing down TREE to the interval in question, and
deleting the appropriate amount of text. */
1992-09-17 02:26:53 +00:00
static int
interval_deletion_adjustment (tree, from, amount)
register INTERVAL tree;
register int from, amount;
{
register int relative_position = from;
if (NULL_INTERVAL_P (tree))
return 0;
/* Left branch */
if (relative_position < LEFT_TOTAL_LENGTH (tree))
1992-09-17 02:26:53 +00:00
{
int subtract = interval_deletion_adjustment (tree->left,
relative_position,
amount);
tree->total_length -= subtract;
CHECK_TOTAL_LENGTH (tree);
1992-09-17 02:26:53 +00:00
return subtract;
}
/* Right branch */
else if (relative_position >= (TOTAL_LENGTH (tree)
- RIGHT_TOTAL_LENGTH (tree)))
1992-09-17 02:26:53 +00:00
{
int subtract;
relative_position -= (tree->total_length
- RIGHT_TOTAL_LENGTH (tree));
subtract = interval_deletion_adjustment (tree->right,
relative_position,
amount);
tree->total_length -= subtract;
CHECK_TOTAL_LENGTH (tree);
1992-09-17 02:26:53 +00:00
return subtract;
}
/* Here -- this node. */
1992-09-17 02:26:53 +00:00
else
{
/* How much can we delete from this interval? */
2002-10-18 10:09:43 +00:00
int my_amount = ((tree->total_length
- RIGHT_TOTAL_LENGTH (tree))
- relative_position);
if (amount > my_amount)
amount = my_amount;
tree->total_length -= amount;
CHECK_TOTAL_LENGTH (tree);
if (LENGTH (tree) == 0)
delete_interval (tree);
2002-10-18 10:09:43 +00:00
return amount;
1992-09-17 02:26:53 +00:00
}
/* Never reach here. */
1992-09-17 02:26:53 +00:00
}
/* Effect the adjustments necessary to the interval tree of BUFFER to
correspond to the deletion of LENGTH characters from that buffer
text. The deletion is effected at position START (which is a
buffer position, i.e. origin 1). */
1992-09-21 23:57:58 +00:00
1992-09-17 02:26:53 +00:00
static void
adjust_intervals_for_deletion (buffer, start, length)
struct buffer *buffer;
int start, length;
{
register int left_to_delete = length;
register INTERVAL tree = BUF_INTERVALS (buffer);
Lisp_Object parent;
int offset;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
GET_INTERVAL_OBJECT (parent, tree);
offset = (BUFFERP (parent) ? BUF_BEG (XBUFFER (parent)) : 0);
1992-09-17 02:26:53 +00:00
if (NULL_INTERVAL_P (tree))
return;
if (start > offset + TOTAL_LENGTH (tree)
|| start + length > offset + TOTAL_LENGTH (tree))
abort ();
1992-09-17 02:26:53 +00:00
if (length == TOTAL_LENGTH (tree))
{
BUF_INTERVALS (buffer) = NULL_INTERVAL;
1992-09-17 02:26:53 +00:00
return;
}
if (ONLY_INTERVAL_P (tree))
{
tree->total_length -= length;
CHECK_TOTAL_LENGTH (tree);
1992-09-17 02:26:53 +00:00
return;
}
if (start > offset + TOTAL_LENGTH (tree))
start = offset + TOTAL_LENGTH (tree);
1992-09-17 02:26:53 +00:00
while (left_to_delete > 0)
{
left_to_delete -= interval_deletion_adjustment (tree, start - offset,
1992-09-17 02:26:53 +00:00
left_to_delete);
tree = BUF_INTERVALS (buffer);
1992-09-17 02:26:53 +00:00
if (left_to_delete == tree->total_length)
{
BUF_INTERVALS (buffer) = NULL_INTERVAL;
1992-09-17 02:26:53 +00:00
return;
}
}
}
1993-06-09 11:59:12 +00:00
/* Make the adjustments necessary to the interval tree of BUFFER to
1992-09-21 23:57:58 +00:00
represent an addition or deletion of LENGTH characters starting
at position START. Addition or deletion is indicated by the sign
of LENGTH. */
1992-09-17 02:26:53 +00:00
INLINE void
offset_intervals (buffer, start, length)
struct buffer *buffer;
int start, length;
{
if (NULL_INTERVAL_P (BUF_INTERVALS (buffer)) || length == 0)
1992-09-17 02:26:53 +00:00
return;
if (length > 0)
adjust_intervals_for_insertion (BUF_INTERVALS (buffer), start, length);
1992-09-17 02:26:53 +00:00
else
adjust_intervals_for_deletion (buffer, start, -length);
}
1992-09-24 01:29:22 +00:00
/* Merge interval I with its lexicographic successor. The resulting
interval is returned, and has the properties of the original
successor. The properties of I are lost. I is removed from the
interval tree.
IMPORTANT:
The caller must verify that this is not the last (rightmost)
interval. */
1992-09-24 01:29:22 +00:00
INTERVAL
merge_interval_right (i)
register INTERVAL i;
{
register int absorb = LENGTH (i);
register INTERVAL successor;
/* Zero out this interval. */
1992-09-24 01:29:22 +00:00
i->total_length -= absorb;
CHECK_TOTAL_LENGTH (i);
1992-09-24 01:29:22 +00:00
/* Find the succeeding interval. */
1992-09-24 01:29:22 +00:00
if (! NULL_RIGHT_CHILD (i)) /* It's below us. Add absorb
as we descend. */
1992-09-24 01:29:22 +00:00
{
successor = i->right;
while (! NULL_LEFT_CHILD (successor))
{
successor->total_length += absorb;
CHECK_TOTAL_LENGTH (successor);
1992-09-24 01:29:22 +00:00
successor = successor->left;
}
successor->total_length += absorb;
CHECK_TOTAL_LENGTH (successor);
1992-09-24 01:29:22 +00:00
delete_interval (i);
return successor;
}
successor = i;
while (! NULL_PARENT (successor)) /* It's above us. Subtract as
we ascend. */
1992-09-24 01:29:22 +00:00
{
if (AM_LEFT_CHILD (successor))
{
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
successor = INTERVAL_PARENT (successor);
1992-09-24 01:29:22 +00:00
delete_interval (i);
return successor;
}
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
successor = INTERVAL_PARENT (successor);
1992-09-24 01:29:22 +00:00
successor->total_length -= absorb;
CHECK_TOTAL_LENGTH (successor);
1992-09-24 01:29:22 +00:00
}
/* This must be the rightmost or last interval and cannot
be merged right. The caller should have known. */
1992-09-24 01:29:22 +00:00
abort ();
}
/* Merge interval I with its lexicographic predecessor. The resulting
interval is returned, and has the properties of the original predecessor.
The properties of I are lost. Interval node I is removed from the tree.
IMPORTANT:
The caller must verify that this is not the first (leftmost) interval. */
1992-09-24 01:29:22 +00:00
INTERVAL
merge_interval_left (i)
register INTERVAL i;
{
register int absorb = LENGTH (i);
register INTERVAL predecessor;
/* Zero out this interval. */
1992-09-24 01:29:22 +00:00
i->total_length -= absorb;
CHECK_TOTAL_LENGTH (i);
1992-09-24 01:29:22 +00:00
/* Find the preceding interval. */
1992-09-24 01:29:22 +00:00
if (! NULL_LEFT_CHILD (i)) /* It's below us. Go down,
adding ABSORB as we go. */
1992-09-24 01:29:22 +00:00
{
predecessor = i->left;
while (! NULL_RIGHT_CHILD (predecessor))
{
predecessor->total_length += absorb;
CHECK_TOTAL_LENGTH (predecessor);
1992-09-24 01:29:22 +00:00
predecessor = predecessor->right;
}
predecessor->total_length += absorb;
CHECK_TOTAL_LENGTH (predecessor);
1992-09-24 01:29:22 +00:00
delete_interval (i);
return predecessor;
}
predecessor = i;
while (! NULL_PARENT (predecessor)) /* It's above us. Go up,
subtracting ABSORB. */
1992-09-24 01:29:22 +00:00
{
if (AM_RIGHT_CHILD (predecessor))
{
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
predecessor = INTERVAL_PARENT (predecessor);
1992-09-24 01:29:22 +00:00
delete_interval (i);
return predecessor;
}
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
predecessor = INTERVAL_PARENT (predecessor);
1992-09-24 01:29:22 +00:00
predecessor->total_length -= absorb;
CHECK_TOTAL_LENGTH (predecessor);
1992-09-24 01:29:22 +00:00
}
1992-09-17 02:26:53 +00:00
1992-09-24 01:29:22 +00:00
/* This must be the leftmost or first interval and cannot
be merged left. The caller should have known. */
1992-09-24 01:29:22 +00:00
abort ();
}
1992-09-21 23:57:58 +00:00
/* Make an exact copy of interval tree SOURCE which descends from
PARENT. This is done by recursing through SOURCE, copying
the current interval and its properties, and then adjusting
the pointers of the copy. */
1992-09-21 23:57:58 +00:00
1992-09-17 02:26:53 +00:00
static INTERVAL
reproduce_tree (source, parent)
INTERVAL source, parent;
{
register INTERVAL t = make_interval ();
bcopy (source, t, INTERVAL_SIZE);
copy_properties (source, t);
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_PARENT (t, parent);
if (! NULL_LEFT_CHILD (source))
t->left = reproduce_tree (source->left, t);
if (! NULL_RIGHT_CHILD (source))
t->right = reproduce_tree (source->right, t);
return t;
}
static INTERVAL
reproduce_tree_obj (source, parent)
INTERVAL source;
Lisp_Object parent;
{
register INTERVAL t = make_interval ();
bcopy (source, t, INTERVAL_SIZE);
copy_properties (source, t);
SET_INTERVAL_OBJECT (t, parent);
1992-09-17 02:26:53 +00:00
if (! NULL_LEFT_CHILD (source))
t->left = reproduce_tree (source->left, t);
if (! NULL_RIGHT_CHILD (source))
t->right = reproduce_tree (source->right, t);
return t;
}
#if 0
/* Nobody calls this. Perhaps it's a vestige of an earlier design. */
1992-09-21 23:57:58 +00:00
/* Make a new interval of length LENGTH starting at START in the
group of intervals INTERVALS, which is actually an interval tree.
Returns the new interval.
Generate an error if the new positions would overlap an existing
interval. */
1992-09-21 23:57:58 +00:00
1992-09-17 02:26:53 +00:00
static INTERVAL
make_new_interval (intervals, start, length)
INTERVAL intervals;
int start, length;
{
INTERVAL slot;
slot = find_interval (intervals, start);
if (start + length > slot->position + LENGTH (slot))
error ("Interval would overlap");
if (start == slot->position && length == LENGTH (slot))
return slot;
if (slot->position == start)
{
/* New right node. */
split_interval_right (slot, length);
1992-09-17 02:26:53 +00:00
return slot;
}
if (slot->position + LENGTH (slot) == start + length)
{
/* New left node. */
split_interval_left (slot, LENGTH (slot) - length);
1992-09-17 02:26:53 +00:00
return slot;
}
/* Convert interval SLOT into three intervals. */
split_interval_left (slot, start - slot->position);
split_interval_right (slot, length);
1992-09-17 02:26:53 +00:00
return slot;
}
#endif
1992-09-24 01:29:22 +00:00
/* Insert the intervals of SOURCE into BUFFER at POSITION.
LENGTH is the length of the text in SOURCE.
1992-09-17 02:26:53 +00:00
The `position' field of the SOURCE intervals is assumed to be
consistent with its parent; therefore, SOURCE must be an
interval tree made with copy_interval or must be the whole
tree of a buffer or a string.
This is used in insdel.c when inserting Lisp_Strings into the
buffer. The text corresponding to SOURCE is already in the buffer
when this is called. The intervals of new tree are a copy of those
belonging to the string being inserted; intervals are never
shared.
1992-09-17 02:26:53 +00:00
If the inserted text had no intervals associated, and we don't
want to inherit the surrounding text's properties, this function
1992-09-17 02:26:53 +00:00
simply returns -- offset_intervals should handle placing the
1992-09-19 01:11:21 +00:00
text in the correct interval, depending on the sticky bits.
1992-09-17 02:26:53 +00:00
If the inserted text had properties (intervals), then there are two
cases -- either insertion happened in the middle of some interval,
or between two intervals.
If the text goes into the middle of an interval, then new
intervals are created in the middle with only the properties of
the new text, *unless* the macro MERGE_INSERTIONS is true, in
which case the new text has the union of its properties and those
of the text into which it was inserted.
If the text goes between two intervals, then if neither interval
1992-09-19 01:11:21 +00:00
had its appropriate sticky property set (front_sticky, rear_sticky),
the new text has only its properties. If one of the sticky properties
1992-09-17 02:26:53 +00:00
is set, then the new text "sticks" to that region and its properties
1993-06-09 11:59:12 +00:00
depend on merging as above. If both the preceding and succeeding
1992-09-19 01:11:21 +00:00
intervals to the new text are "sticky", then the new text retains
only its properties, as if neither sticky property were set. Perhaps
1992-09-17 02:26:53 +00:00
we should consider merging all three sets of properties onto the new
text... */
1992-09-17 02:26:53 +00:00
void
graft_intervals_into_buffer (source, position, length, buffer, inherit)
1992-09-24 01:29:22 +00:00
INTERVAL source;
int position, length;
1992-09-24 01:29:22 +00:00
struct buffer *buffer;
int inherit;
1992-09-17 02:26:53 +00:00
{
register INTERVAL under, over, this, prev;
register INTERVAL tree;
2004-04-16 12:51:06 +00:00
int over_used;
1992-09-17 02:26:53 +00:00
tree = BUF_INTERVALS (buffer);
/* If the new text has no properties, then with inheritance it
becomes part of whatever interval it was inserted into.
To prevent inheritance, we must clear out the properties
of the newly inserted text. */
1992-09-24 01:29:22 +00:00
if (NULL_INTERVAL_P (source))
{
Lisp_Object buf;
if (!inherit && !NULL_INTERVAL_P (tree) && length > 0)
{
XSETBUFFER (buf, buffer);
set_text_properties_1 (make_number (position),
make_number (position + length),
Qnil, buf, 0);
}
if (! NULL_INTERVAL_P (BUF_INTERVALS (buffer)))
/* Shouldn't be necessary. -stef */
BUF_INTERVALS (buffer) = balance_an_interval (BUF_INTERVALS (buffer));
return;
}
1992-09-17 02:26:53 +00:00
if (NULL_INTERVAL_P (tree))
{
/* The inserted text constitutes the whole buffer, so
simply copy over the interval structure. */
if ((BUF_Z (buffer) - BUF_BEG (buffer)) == TOTAL_LENGTH (source))
1992-09-17 02:26:53 +00:00
{
Lisp_Object buf;
XSETBUFFER (buf, buffer);
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
BUF_INTERVALS (buffer) = reproduce_tree_obj (source, buf);
BUF_INTERVALS (buffer)->position = BEG;
2004-04-16 12:51:06 +00:00
BUF_INTERVALS (buffer)->up_obj = 1;
/* Explicitly free the old tree here? */
1992-09-17 02:26:53 +00:00
return;
}
/* Create an interval tree in which to place a copy
of the intervals of the inserted string. */
1992-09-17 02:26:53 +00:00
{
1992-10-02 22:33:18 +00:00
Lisp_Object buf;
XSETBUFFER (buf, buffer);
tree = create_root_interval (buf);
1992-09-17 02:26:53 +00:00
}
}
else if (TOTAL_LENGTH (tree) == TOTAL_LENGTH (source))
/* If the buffer contains only the new string, but
there was already some interval tree there, then it may be
some zero length intervals. Eventually, do something clever
about inserting properly. For now, just waste the old intervals. */
{
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
BUF_INTERVALS (buffer) = reproduce_tree (source, INTERVAL_PARENT (tree));
BUF_INTERVALS (buffer)->position = BEG;
2004-04-16 12:51:06 +00:00
BUF_INTERVALS (buffer)->up_obj = 1;
/* Explicitly free the old tree here. */
1992-09-17 02:26:53 +00:00
return;
}
/* Paranoia -- the text has already been added, so this buffer
should be of non-zero length. */
else if (TOTAL_LENGTH (tree) == 0)
abort ();
1992-09-17 02:26:53 +00:00
this = under = find_interval (tree, position);
if (NULL_INTERVAL_P (under)) /* Paranoia */
abort ();
over = find_interval (source, interval_start_pos (source));
1992-09-17 02:26:53 +00:00
/* Here for insertion in the middle of an interval.
Split off an equivalent interval to the right,
then don't bother with it any more. */
1992-09-17 02:26:53 +00:00
if (position > under->position)
1992-09-17 02:26:53 +00:00
{
INTERVAL end_unchanged
= split_interval_left (this, position - under->position);
1992-09-17 02:26:53 +00:00
copy_properties (under, end_unchanged);
under->position = position;
1992-09-17 02:26:53 +00:00
}
else
{
/* This call may have some effect because previous_interval may
update `position' fields of intervals. Thus, don't ignore it
for the moment. Someone please tell me the truth (K.Handa). */
prev = previous_interval (under);
#if 0
/* But, this code surely has no effect. And, anyway,
END_NONSTICKY_P is unreliable now. */
if (prev && !END_NONSTICKY_P (prev))
prev = 0;
#endif /* 0 */
}
/* Insertion is now at beginning of UNDER. */
1992-09-17 02:26:53 +00:00
/* The inserted text "sticks" to the interval `under',
which means it gets those properties.
The properties of under are the result of
1996-01-05 10:03:17 +00:00
adjust_intervals_for_insertion, so stickiness has
already been taken care of. */
2002-10-18 10:09:43 +00:00
2004-04-16 12:51:06 +00:00
/* OVER is the interval we are copying from next.
OVER_USED says how many characters' worth of OVER
have already been copied into target intervals.
UNDER is the next interval in the target. */
over_used = 0;
1992-09-17 02:26:53 +00:00
while (! NULL_INTERVAL_P (over))
{
2004-04-16 12:51:06 +00:00
/* If UNDER is longer than OVER, split it. */
if (LENGTH (over) - over_used < LENGTH (under))
{
2004-04-16 12:51:06 +00:00
this = split_interval_left (under, LENGTH (over) - over_used);
copy_properties (under, this);
}
else
this = under;
2004-04-16 12:51:06 +00:00
/* THIS is now the interval to copy or merge into.
OVER covers all of it. */
if (inherit)
merge_properties (over, this);
else
copy_properties (over, this);
2004-04-16 12:51:06 +00:00
/* If THIS and OVER end at the same place,
advance OVER to a new source interval. */
if (LENGTH (this) == LENGTH (over) - over_used)
{
over = next_interval (over);
over_used = 0;
}
else
/* Otherwise just record that more of OVER has been used. */
over_used += LENGTH (this);
/* Always advance to a new target interval. */
under = next_interval (this);
1992-09-17 02:26:53 +00:00
}
if (! NULL_INTERVAL_P (BUF_INTERVALS (buffer)))
BUF_INTERVALS (buffer) = balance_an_interval (BUF_INTERVALS (buffer));
1992-09-17 02:26:53 +00:00
return;
}
/* Get the value of property PROP from PLIST,
which is the plist of an interval.
2002-10-18 10:09:43 +00:00
We check for direct properties, for categories with property PROP,
and for PROP appearing on the default-text-properties list. */
Lisp_Object
textget (plist, prop)
Lisp_Object plist;
register Lisp_Object prop;
{
return lookup_char_property (plist, prop, 1);
}
Lisp_Object
lookup_char_property (plist, prop, textprop)
Lisp_Object plist;
register Lisp_Object prop;
int textprop;
{
register Lisp_Object tail, fallback = Qnil;
for (tail = plist; CONSP (tail); tail = Fcdr (XCDR (tail)))
{
register Lisp_Object tem;
tem = XCAR (tail);
if (EQ (prop, tem))
return Fcar (XCDR (tail));
if (EQ (tem, Qcategory))
{
tem = Fcar (XCDR (tail));
if (SYMBOLP (tem))
fallback = Fget (tem, prop);
}
}
if (! NILP (fallback))
return fallback;
/* Check for alternative properties */
tail = Fassq (prop, Vchar_property_alias_alist);
if (! NILP (tail))
{
tail = XCDR (tail);
for (; NILP (fallback) && CONSP (tail); tail = XCDR (tail))
fallback = Fplist_get (plist, XCAR (tail));
}
if (textprop && NILP (fallback) && CONSP (Vdefault_text_properties))
fallback = Fplist_get (Vdefault_text_properties, prop);
return fallback;
}
/* Set point "temporarily", without checking any text properties. */
INLINE void
temp_set_point (struct buffer *buffer, EMACS_INT charpos)
{
temp_set_point_both (buffer, charpos,
buf_charpos_to_bytepos (buffer, charpos));
}
/* Set point in BUFFER "temporarily" to CHARPOS, which corresponds to
byte position BYTEPOS. */
INLINE void
temp_set_point_both (struct buffer *buffer,
EMACS_INT charpos, EMACS_INT bytepos)
{
/* In a single-byte buffer, the two positions must be equal. */
if (BUF_ZV (buffer) == BUF_ZV_BYTE (buffer)
&& charpos != bytepos)
abort ();
if (charpos > bytepos)
abort ();
if (charpos > BUF_ZV (buffer) || charpos < BUF_BEGV (buffer))
abort ();
BUF_PT_BYTE (buffer) = bytepos;
BUF_PT (buffer) = charpos;
}
2002-10-18 10:09:43 +00:00
/* Set point in BUFFER to CHARPOS. If the target position is
1994-04-26 01:18:38 +00:00
before an intangible character, move to an ok place. */
1992-09-17 02:26:53 +00:00
void
set_point (EMACS_INT charpos)
{
set_point_both (charpos, buf_charpos_to_bytepos (current_buffer, charpos));
}
/* If there's an invisible character at position POS + TEST_OFFS in the
current buffer, and the invisible property has a `stickiness' such that
inserting a character at position POS would inherit the property it,
return POS + ADJ, otherwise return POS. If TEST_INTANG is non-zero,
then intangibility is required as well as invisibleness.
TEST_OFFS should be either 0 or -1, and ADJ should be either 1 or -1.
Note that `stickiness' is determined by overlay marker insertion types,
2002-10-18 10:09:43 +00:00
if the invisible property comes from an overlay. */
static int
adjust_for_invis_intang (pos, test_offs, adj, test_intang)
int pos, test_offs, adj, test_intang;
{
Lisp_Object invis_propval, invis_overlay;
Lisp_Object test_pos;
if ((adj < 0 && pos + adj < BEGV) || (adj > 0 && pos + adj > ZV))
/* POS + ADJ would be beyond the buffer bounds, so do no adjustment. */
return pos;
test_pos = make_number (pos + test_offs);
invis_propval
= get_char_property_and_overlay (test_pos, Qinvisible, Qnil,
&invis_overlay);
if ((!test_intang
|| ! NILP (Fget_char_property (test_pos, Qintangible, Qnil)))
&& TEXT_PROP_MEANS_INVISIBLE (invis_propval)
/* This next test is true if the invisible property has a stickiness
such that an insertion at POS would inherit it. */
&& (NILP (invis_overlay)
/* Invisible property is from a text-property. */
? (text_property_stickiness (Qinvisible, make_number (pos), Qnil)
== (test_offs == 0 ? 1 : -1))
/* Invisible property is from an overlay. */
: (test_offs == 0
? XMARKER (OVERLAY_START (invis_overlay))->insertion_type == 0
: XMARKER (OVERLAY_END (invis_overlay))->insertion_type == 1)))
pos += adj;
return pos;
}
/* Set point in BUFFER to CHARPOS, which corresponds to byte
2002-10-18 10:09:43 +00:00
position BYTEPOS. If the target position is
before an intangible character, move to an ok place. */
void
set_point_both (EMACS_INT charpos, EMACS_INT bytepos)
1992-09-17 02:26:53 +00:00
{
register INTERVAL to, from, toprev, fromprev;
EMACS_INT buffer_point;
EMACS_INT old_position = PT;
2006-05-23 00:49:55 +00:00
/* This ensures that we move forward past intangible text when the
initial position is the same as the destination, in the rare
instances where this is important, e.g. in line-move-finish
(simple.el). */
int backwards = (charpos < old_position ? 1 : 0);
int have_overlays;
EMACS_INT original_position;
1992-09-17 02:26:53 +00:00
current_buffer->point_before_scroll = Qnil;
if (charpos == PT)
1992-09-17 02:26:53 +00:00
return;
/* In a single-byte buffer, the two positions must be equal. */
eassert (ZV != ZV_BYTE || charpos == bytepos);
/* Check this now, before checking if the buffer has any intervals.
That way, we can catch conditions which break this sanity check
whether or not there are intervals in the buffer. */
eassert (charpos <= ZV && charpos >= BEGV);
have_overlays = (current_buffer->overlays_before
|| current_buffer->overlays_after);
/* If we have no text properties and overlays,
then we can do it quickly. */
if (NULL_INTERVAL_P (BUF_INTERVALS (current_buffer)) && ! have_overlays)
1992-09-17 02:26:53 +00:00
{
temp_set_point_both (current_buffer, charpos, bytepos);
1992-09-17 02:26:53 +00:00
return;
}
/* Set TO to the interval containing the char after CHARPOS,
and TOPREV to the interval containing the char before CHARPOS.
Either one may be null. They may be equal. */
to = find_interval (BUF_INTERVALS (current_buffer), charpos);
if (charpos == BEGV)
toprev = 0;
else if (to && to->position == charpos)
toprev = previous_interval (to);
else
toprev = to;
buffer_point = (PT == ZV ? ZV - 1 : PT);
1992-09-24 01:29:22 +00:00
/* Set FROM to the interval containing the char after PT,
and FROMPREV to the interval containing the char before PT.
Either one may be null. They may be equal. */
/* We could cache this and save time. */
from = find_interval (BUF_INTERVALS (current_buffer), buffer_point);
if (buffer_point == BEGV)
fromprev = 0;
else if (from && from->position == PT)
fromprev = previous_interval (from);
else if (buffer_point != PT)
fromprev = from, from = 0;
else
fromprev = from;
1992-09-17 02:26:53 +00:00
/* Moving within an interval. */
if (to == from && toprev == fromprev && INTERVAL_VISIBLE_P (to)
&& ! have_overlays)
1992-09-17 02:26:53 +00:00
{
temp_set_point_both (current_buffer, charpos, bytepos);
1992-09-17 02:26:53 +00:00
return;
}
original_position = charpos;
/* If the new position is between two intangible characters
with the same intangible property value,
move forward or backward until a change in that property. */
if (NILP (Vinhibit_point_motion_hooks)
&& ((! NULL_INTERVAL_P (to) && ! NULL_INTERVAL_P (toprev))
|| have_overlays)
/* Intangibility never stops us from positioning at the beginning
or end of the buffer, so don't bother checking in that case. */
&& charpos != BEGV && charpos != ZV)
1992-09-17 02:26:53 +00:00
{
Lisp_Object pos;
Lisp_Object intangible_propval;
if (backwards)
{
2003-04-21 01:39:06 +00:00
/* If the preceding character is both intangible and invisible,
and the invisible property is `rear-sticky', perturb it so
that the search starts one character earlier -- this ensures
that point can never move to the end of an invisible/
intangible/rear-sticky region. */
charpos = adjust_for_invis_intang (charpos, -1, -1, 1);
XSETINT (pos, charpos);
/* If following char is intangible,
skip back over all chars with matching intangible property. */
intangible_propval = Fget_char_property (pos, Qintangible, Qnil);
if (! NILP (intangible_propval))
{
while (XINT (pos) > BEGV
&& EQ (Fget_char_property (make_number (XINT (pos) - 1),
Qintangible, Qnil),
intangible_propval))
pos = Fprevious_char_property_change (pos, Qnil);
/* Set CHARPOS from POS, and if the final intangible character
that we skipped over is also invisible, and the invisible
property is `front-sticky', perturb it to be one character
earlier -- this ensures that point can never move to the
beginning of an invisible/intangible/front-sticky region. */
charpos = adjust_for_invis_intang (XINT (pos), 0, -1, 0);
}
}
else
{
/* If the following character is both intangible and invisible,
and the invisible property is `front-sticky', perturb it so
that the search starts one character later -- this ensures
that point can never move to the beginning of an
invisible/intangible/front-sticky region. */
charpos = adjust_for_invis_intang (charpos, 0, 1, 1);
XSETINT (pos, charpos);
/* If preceding char is intangible,
skip forward over all chars with matching intangible property. */
intangible_propval = Fget_char_property (make_number (charpos - 1),
Qintangible, Qnil);
if (! NILP (intangible_propval))
{
while (XINT (pos) < ZV
&& EQ (Fget_char_property (pos, Qintangible, Qnil),
intangible_propval))
pos = Fnext_char_property_change (pos, Qnil);
/* Set CHARPOS from POS, and if the final intangible character
that we skipped over is also invisible, and the invisible
property is `rear-sticky', perturb it to be one character
later -- this ensures that point can never move to the
end of an invisible/intangible/rear-sticky region. */
charpos = adjust_for_invis_intang (XINT (pos), -1, 1, 0);
}
}
bytepos = buf_charpos_to_bytepos (current_buffer, charpos);
}
if (charpos != original_position)
{
/* Set TO to the interval containing the char after CHARPOS,
and TOPREV to the interval containing the char before CHARPOS.
Either one may be null. They may be equal. */
to = find_interval (BUF_INTERVALS (current_buffer), charpos);
if (charpos == BEGV)
toprev = 0;
else if (to && to->position == charpos)
toprev = previous_interval (to);
else
toprev = to;
1992-09-17 02:26:53 +00:00
}
/* Here TO is the interval after the stopping point
and TOPREV is the interval before the stopping point.
One or the other may be null. */
temp_set_point_both (current_buffer, charpos, bytepos);
1992-09-17 02:26:53 +00:00
2007-08-08 07:49:21 +00:00
/* We run point-left and point-entered hooks here, if the
1992-10-01 00:56:11 +00:00
two intervals are not equivalent. These hooks take
(old_point, new_point) as arguments. */
if (NILP (Vinhibit_point_motion_hooks)
&& (! intervals_equal (from, to)
|| ! intervals_equal (fromprev, toprev)))
1992-09-24 01:29:22 +00:00
{
Lisp_Object leave_after, leave_before, enter_after, enter_before;
if (fromprev)
leave_before = textget (fromprev->plist, Qpoint_left);
else
leave_before = Qnil;
if (from)
leave_after = textget (from->plist, Qpoint_left);
else
leave_after = Qnil;
if (toprev)
enter_before = textget (toprev->plist, Qpoint_entered);
else
enter_before = Qnil;
if (to)
enter_after = textget (to->plist, Qpoint_entered);
else
enter_after = Qnil;
1992-09-24 01:29:22 +00:00
if (! EQ (leave_before, enter_before) && !NILP (leave_before))
call2 (leave_before, make_number (old_position),
make_number (charpos));
if (! EQ (leave_after, enter_after) && !NILP (leave_after))
call2 (leave_after, make_number (old_position),
make_number (charpos));
1992-09-24 01:29:22 +00:00
if (! EQ (enter_before, leave_before) && !NILP (enter_before))
call2 (enter_before, make_number (old_position),
make_number (charpos));
if (! EQ (enter_after, leave_after) && !NILP (enter_after))
call2 (enter_after, make_number (old_position),
make_number (charpos));
1992-09-24 01:29:22 +00:00
}
1992-09-17 02:26:53 +00:00
}
/* Move point to POSITION, unless POSITION is inside an intangible
segment that reaches all the way to point. */
void
move_if_not_intangible (position)
int position;
{
Lisp_Object pos;
Lisp_Object intangible_propval;
XSETINT (pos, position);
if (! NILP (Vinhibit_point_motion_hooks))
/* If intangible is inhibited, always move point to POSITION. */
;
else if (PT < position && XINT (pos) < ZV)
{
/* We want to move forward, so check the text before POSITION. */
intangible_propval = Fget_char_property (pos,
Qintangible, Qnil);
/* If following char is intangible,
skip back over all chars with matching intangible property. */
if (! NILP (intangible_propval))
while (XINT (pos) > BEGV
&& EQ (Fget_char_property (make_number (XINT (pos) - 1),
Qintangible, Qnil),
intangible_propval))
pos = Fprevious_char_property_change (pos, Qnil);
}
else if (XINT (pos) > BEGV)
{
/* We want to move backward, so check the text after POSITION. */
intangible_propval = Fget_char_property (make_number (XINT (pos) - 1),
Qintangible, Qnil);
/* If following char is intangible,
1999-07-01 14:16:44 +00:00
skip forward over all chars with matching intangible property. */
if (! NILP (intangible_propval))
while (XINT (pos) < ZV
&& EQ (Fget_char_property (pos, Qintangible, Qnil),
intangible_propval))
pos = Fnext_char_property_change (pos, Qnil);
}
else if (position < BEGV)
position = BEGV;
else if (position > ZV)
position = ZV;
2002-10-18 10:09:43 +00:00
/* If the whole stretch between PT and POSITION isn't intangible,
try moving to POSITION (which means we actually move farther
if POSITION is inside of intangible text). */
if (XINT (pos) != PT)
SET_PT (position);
}
/* If text at position POS has property PROP, set *VAL to the property
value, *START and *END to the beginning and end of a region that
has the same property, and return 1. Otherwise return 0.
OBJECT is the string or buffer to look for the property in;
nil means the current buffer. */
int
get_property_and_range (pos, prop, val, start, end, object)
int pos;
Lisp_Object prop, *val;
EMACS_INT *start, *end;
Lisp_Object object;
{
INTERVAL i, prev, next;
if (NILP (object))
i = find_interval (BUF_INTERVALS (current_buffer), pos);
else if (BUFFERP (object))
i = find_interval (BUF_INTERVALS (XBUFFER (object)), pos);
else if (STRINGP (object))
i = find_interval (STRING_INTERVALS (object), pos);
else
abort ();
if (NULL_INTERVAL_P (i) || (i->position + LENGTH (i) <= pos))
return 0;
*val = textget (i->plist, prop);
if (NILP (*val))
return 0;
next = i; /* remember it in advance */
prev = previous_interval (i);
while (! NULL_INTERVAL_P (prev)
&& EQ (*val, textget (prev->plist, prop)))
i = prev, prev = previous_interval (prev);
*start = i->position;
next = next_interval (i);
2002-10-18 10:09:43 +00:00
while (! NULL_INTERVAL_P (next)
&& EQ (*val, textget (next->plist, prop)))
i = next, next = next_interval (next);
*end = i->position + LENGTH (i);
return 1;
}
/* Return the proper local keymap TYPE for position POSITION in
BUFFER; TYPE should be one of `keymap' or `local-map'. Use the map
specified by the PROP property, if any. Otherwise, if TYPE is
`local-map' use BUFFER's local map.
POSITION must be in the accessible part of BUFFER. */
Lisp_Object
get_local_map (position, buffer, type)
register int position;
register struct buffer *buffer;
Lisp_Object type;
{
Lisp_Object prop, lispy_position, lispy_buffer;
int old_begv, old_zv, old_begv_byte, old_zv_byte;
/* Perhaps we should just change `position' to the limit. */
if (position > BUF_ZV (buffer) || position < BUF_BEGV (buffer))
abort ();
/* Ignore narrowing, so that a local map continues to be valid even if
the visible region contains no characters and hence no properties. */
old_begv = BUF_BEGV (buffer);
old_zv = BUF_ZV (buffer);
old_begv_byte = BUF_BEGV_BYTE (buffer);
old_zv_byte = BUF_ZV_BYTE (buffer);
BUF_BEGV (buffer) = BUF_BEG (buffer);
BUF_ZV (buffer) = BUF_Z (buffer);
BUF_BEGV_BYTE (buffer) = BUF_BEG_BYTE (buffer);
BUF_ZV_BYTE (buffer) = BUF_Z_BYTE (buffer);
XSETFASTINT (lispy_position, position);
XSETBUFFER (lispy_buffer, buffer);
/* First check if the CHAR has any property. This is because when
we click with the mouse, the mouse pointer is really pointing
to the CHAR after POS. */
prop = Fget_char_property (lispy_position, type, lispy_buffer);
/* If not, look at the POS's properties. This is necessary because when
editing a field with a `local-map' property, we want insertion at the end
to obey the `local-map' property. */
if (NILP (prop))
prop = get_pos_property (lispy_position, type, lispy_buffer);
BUF_BEGV (buffer) = old_begv;
BUF_ZV (buffer) = old_zv;
BUF_BEGV_BYTE (buffer) = old_begv_byte;
BUF_ZV_BYTE (buffer) = old_zv_byte;
/* Use the local map only if it is valid. */
* lisp.h (KEYMAPP): New macro. (get_keymap): Remove. (get_keymap_1): Rename get_keymap. * keyboard.h (get_keymap_1, Fkeymapp): Remove prototype. * xterm.c (note_mode_line_highlight): Use KEYMAPP. * xmenu.c (single_submenu): Use KEYMAPP. (Fx_popup_menu): Fetch keymaps rather than checking Fkeymapp. Use KEYMAPP rather than Fkeymapp. * w32term.c (note_mode_line_highlight): Use KEYMAPP. * w32menu.c (True, False): Remove (use TRUE and FALSE instead). (Fx_popup_menu): Fetch keymaps rather than checking Fkeymapp. Use KEYMAPP rather than Fkeymapp. (single_submenu): Use KEYMAPP. (w32_menu_show, w32_dialog_show): Use TRUE. * minibuf.c (Fread_from_minibuffer): Update call to get_keymap. * keymap.c (KEYMAPP): Remove (moved to lisp.h). (Fkeymapp): Use KEYMAPP. (get_keymap): Rename from get_keymap_1. Remove old def. Return t when autoload=0 and error=0 and the keymap needs autoloading. (Fcopy_keymap): Check (eq (car x) 'keymap) rather than using Fkeymapp. (Fminor_mode_key_binding): Don't raise an error if the binding is not a keymap. (Fuse_global_map, Fuse_local_map): Allow autoloading. (Faccessible_keymaps): Fetch keymaps rather than checking Fkeymapp. * keyboard.c (read_char): get_keymap_1 -> get_keymap. Allow Vspecial_event_map to be autoloaded. (menu_bar_items): Fetch the keymap rather than using keymapp. (menu_bar_one_keymap): No need to follow func-indirect any more. (parse_menu_item): get_keymap_1 -> get_keymap. (tool_bar_items): Fetch the keymap rather than using keymapp. (read_key_sequence): Use KEYMAPP. * intervals.c (get_local_map): Use get_keymap rather than following function-indirections explicitly. * doc.c (Fsubstitute_command_keys): get_keymap_1 -> get_keymap.
2000-10-27 22:20:19 +00:00
prop = get_keymap (prop, 0, 0);
if (CONSP (prop))
return prop;
if (EQ (type, Qkeymap))
return Qnil;
else
return buffer->keymap;
}
1992-09-24 01:29:22 +00:00
/* Produce an interval tree reflecting the intervals in
TREE from START to START + LENGTH.
The new interval tree has no parent and has a starting-position of 0. */
1992-09-17 02:26:53 +00:00
INTERVAL
1992-09-17 02:26:53 +00:00
copy_intervals (tree, start, length)
INTERVAL tree;
int start, length;
{
register INTERVAL i, new, t;
register int got, prevlen;
1992-09-17 02:26:53 +00:00
if (NULL_INTERVAL_P (tree) || length <= 0)
return NULL_INTERVAL;
i = find_interval (tree, start);
if (NULL_INTERVAL_P (i) || LENGTH (i) == 0)
abort ();
/* If there is only one interval and it's the default, return nil. */
1992-09-17 02:26:53 +00:00
if ((start - i->position + 1 + length) < LENGTH (i)
&& DEFAULT_INTERVAL_P (i))
return NULL_INTERVAL;
new = make_interval ();
new->position = 0;
1992-09-17 02:26:53 +00:00
got = (LENGTH (i) - (start - i->position));
1992-09-24 01:29:22 +00:00
new->total_length = length;
CHECK_TOTAL_LENGTH (new);
1992-09-17 02:26:53 +00:00
copy_properties (i, new);
t = new;
prevlen = got;
1992-09-17 02:26:53 +00:00
while (got < length)
{
i = next_interval (i);
t = split_interval_right (t, prevlen);
1992-09-17 02:26:53 +00:00
copy_properties (i, t);
prevlen = LENGTH (i);
got += prevlen;
1992-09-17 02:26:53 +00:00
}
return balance_an_interval (new);
1992-09-17 02:26:53 +00:00
}
/* Give STRING the properties of BUFFER from POSITION to LENGTH. */
1992-09-17 02:26:53 +00:00
1992-10-01 00:56:11 +00:00
INLINE void
1992-09-17 02:26:53 +00:00
copy_intervals_to_string (string, buffer, position, length)
Lisp_Object string;
struct buffer *buffer;
1992-09-17 02:26:53 +00:00
int position, length;
{
INTERVAL interval_copy = copy_intervals (BUF_INTERVALS (buffer),
1992-09-17 02:26:53 +00:00
position, length);
if (NULL_INTERVAL_P (interval_copy))
return;
Changes towards better type safety regarding intervals, primarily regarding the "parent" handle. These just separate out the different usages based on the type of parent (interval vs lisp object); later changes will do type checking and enforcement. * intervals.h (NULL_INTERVAL): Cast to INTERVAL type. (INT_LISPLIKE): New macro. (NULL_INTERVAL_P): Use it. (INTERVAL_HAS_PARENT, INTERVAL_HAS_OBJECT, SET_INTERVAL_PARENT, SET_INTERVAL_OBJECT, INTERVAL_PARENT, COPY_INTERVAL_PARENT, GET_INTERVAL_OBJECT, INTERVAL_PARENT_OR_NULL): New macros. * alloc.c (make_interval, gc_sweep): Use new macros; eliminate all explicit references to "parent" field of struct interval and associated unclean type conversions. * intervals.c (create_root_interval, root_interval, rotate_right, rotate_left, balance_possible_root_interval, split_interval_right, split_interval_left, interval_start_pos, find_interval, next_interval, previous_interval, update_interval, adjust_intervals_for_insertion, delete_node, delete_interval, adjust_intervals_for_deletion, merge_interval_right, merge_interval_left, reproduce_tree, graft_intervals_into_buffer, copy_intervals_to_string): Likewise. * intervals.h (AM_LEFT_CHILD, AM_RIGHT_CHILD, RESET_INTERVAL): Likewise. * syntax.c (update_syntax_table): Likewise. * intervals.c (reproduce_tree_obj): New function, like reproduce_tree but takes a Lisp_Object for the parent. Declare with prototype. (graft_intervals_into_buffer): Use it when appropriate. (reproduce_tree): Declare with prototype. (balance_possible_root_interval): Check that the parent is a lisp object before trying to examine its type.
2000-03-22 21:44:05 +00:00
SET_INTERVAL_OBJECT (interval_copy, string);
STRING_SET_INTERVALS (string, interval_copy);
1992-09-17 02:26:53 +00:00
}
/* Return 1 if strings S1 and S2 have identical properties; 0 otherwise.
Assume they have identical characters. */
int
compare_string_intervals (s1, s2)
Lisp_Object s1, s2;
{
INTERVAL i1, i2;
int pos = 0;
int end = SCHARS (s1);
i1 = find_interval (STRING_INTERVALS (s1), 0);
i2 = find_interval (STRING_INTERVALS (s2), 0);
while (pos < end)
{
/* Determine how far we can go before we reach the end of I1 or I2. */
int len1 = (i1 != 0 ? INTERVAL_LAST_POS (i1) : end) - pos;
int len2 = (i2 != 0 ? INTERVAL_LAST_POS (i2) : end) - pos;
int distance = min (len1, len2);
/* If we ever find a mismatch between the strings,
they differ. */
if (! intervals_equal (i1, i2))
return 0;
/* Advance POS till the end of the shorter interval,
and advance one or both interval pointers for the new position. */
pos += distance;
if (len1 == distance)
i1 = next_interval (i1);
if (len2 == distance)
i2 = next_interval (i2);
}
return 1;
}
/* Recursively adjust interval I in the current buffer
for setting enable_multibyte_characters to MULTI_FLAG.
The range of interval I is START ... END in characters,
START_BYTE ... END_BYTE in bytes. */
static void
set_intervals_multibyte_1 (i, multi_flag, start, start_byte, end, end_byte)
INTERVAL i;
int multi_flag;
int start, start_byte, end, end_byte;
{
/* Fix the length of this interval. */
if (multi_flag)
i->total_length = end - start;
else
i->total_length = end_byte - start_byte;
CHECK_TOTAL_LENGTH (i);
if (TOTAL_LENGTH (i) == 0)
{
delete_interval (i);
return;
}
/* Recursively fix the length of the subintervals. */
if (i->left)
{
int left_end, left_end_byte;
if (multi_flag)
{
int temp;
left_end_byte = start_byte + LEFT_TOTAL_LENGTH (i);
left_end = BYTE_TO_CHAR (left_end_byte);
temp = CHAR_TO_BYTE (left_end);
/* If LEFT_END_BYTE is in the middle of a character,
adjust it and LEFT_END to a char boundary. */
if (left_end_byte > temp)
{
left_end_byte = temp;
}
if (left_end_byte < temp)
{
left_end--;
left_end_byte = CHAR_TO_BYTE (left_end);
}
}
else
{
left_end = start + LEFT_TOTAL_LENGTH (i);
left_end_byte = CHAR_TO_BYTE (left_end);
}
set_intervals_multibyte_1 (i->left, multi_flag, start, start_byte,
left_end, left_end_byte);
}
if (i->right)
{
int right_start_byte, right_start;
if (multi_flag)
{
int temp;
right_start_byte = end_byte - RIGHT_TOTAL_LENGTH (i);
right_start = BYTE_TO_CHAR (right_start_byte);
/* If RIGHT_START_BYTE is in the middle of a character,
adjust it and RIGHT_START to a char boundary. */
temp = CHAR_TO_BYTE (right_start);
if (right_start_byte < temp)
{
right_start_byte = temp;
}
if (right_start_byte > temp)
{
right_start++;
right_start_byte = CHAR_TO_BYTE (right_start);
}
}
else
{
right_start = end - RIGHT_TOTAL_LENGTH (i);
right_start_byte = CHAR_TO_BYTE (right_start);
}
set_intervals_multibyte_1 (i->right, multi_flag,
right_start, right_start_byte,
end, end_byte);
}
/* Rounding to char boundaries can theoretically ake this interval
spurious. If so, delete one child, and copy its property list
to this interval. */
if (LEFT_TOTAL_LENGTH (i) + RIGHT_TOTAL_LENGTH (i) >= TOTAL_LENGTH (i))
{
if ((i)->left)
{
(i)->plist = (i)->left->plist;
(i)->left->total_length = 0;
delete_interval ((i)->left);
}
else
{
(i)->plist = (i)->right->plist;
(i)->right->total_length = 0;
delete_interval ((i)->right);
}
}
}
/* Update the intervals of the current buffer
to fit the contents as multibyte (if MULTI_FLAG is 1)
or to fit them as non-multibyte (if MULTI_FLAG is 0). */
void
set_intervals_multibyte (multi_flag)
int multi_flag;
{
if (BUF_INTERVALS (current_buffer))
set_intervals_multibyte_1 (BUF_INTERVALS (current_buffer), multi_flag,
BEG, BEG_BYTE, Z, Z_BYTE);
}
2004-04-16 12:51:06 +00:00
/* arch-tag: 3d402b60-083c-4271-b4a3-ebd9a74bfe27
(do not change this comment) */