Mercurial > hg > xemacs-beta
view etc/bundled-packages/README @ 5307:c096d8051f89
Have NATNUMP give t for positive bignums; check limits appropriately.
src/ChangeLog addition:
2010-11-20 Aidan Kehoe <kehoea@parhasard.net>
* abbrev.c (Fexpand_abbrev):
* alloc.c:
* alloc.c (Fmake_list):
* alloc.c (Fmake_vector):
* alloc.c (Fmake_bit_vector):
* alloc.c (Fmake_byte_code):
* alloc.c (Fmake_string):
* alloc.c (vars_of_alloc):
* bytecode.c (UNUSED):
* bytecode.c (Fbyte_code):
* chartab.c (decode_char_table_range):
* cmds.c (Fself_insert_command):
* data.c (check_integer_range):
* data.c (Fnatnump):
* data.c (Fnonnegativep):
* data.c (Fstring_to_number):
* elhash.c (hash_table_size_validate):
* elhash.c (decode_hash_table_size):
* eval.c (Fbacktrace_frame):
* event-stream.c (lisp_number_to_milliseconds):
* event-stream.c (Faccept_process_output):
* event-stream.c (Frecent_keys):
* event-stream.c (Fdispatch_event):
* events.c (Fmake_event):
* events.c (Fevent_timestamp):
* events.c (Fevent_timestamp_lessp):
* events.h:
* events.h (struct command_builder):
* file-coding.c (gzip_putprop):
* fns.c:
* fns.c (check_sequence_range):
* fns.c (Frandom):
* fns.c (Fnthcdr):
* fns.c (Flast):
* fns.c (Fnbutlast):
* fns.c (Fbutlast):
* fns.c (Fmember):
* fns.c (Ffill):
* fns.c (Freduce):
* fns.c (replace_string_range_1):
* fns.c (Freplace):
* font-mgr.c (Ffc_pattern_get):
* frame-msw.c (msprinter_set_frame_properties):
* glyphs.c (check_valid_xbm_inline):
* indent.c (Fmove_to_column):
* intl-win32.c (mswindows_multibyte_to_unicode_putprop):
* lisp.h:
* lisp.h (ARRAY_DIMENSION_LIMIT):
* lread.c (decode_mode_1):
* mule-ccl.c (ccl_get_compiled_code):
* number.h:
* process-unix.c (unix_open_multicast_group):
* process.c (Fset_process_window_size):
* profile.c (Fstart_profiling):
* unicode.c (Funicode_to_char):
Change NATNUMP to return 1 for positive bignums; changes uses of
it and of CHECK_NATNUM appropriately, usually by checking for an
integer in an appropriate range.
Add array-dimension-limit and use it in #'make-vector,
#'make-string. Add array-total-size-limit, array-rank-limit while
we're at it, for the sake of any Common Lisp-oriented code that
uses these limits.
Rename check_int_range to check_integer_range, have it take
Lisp_Objects (and thus bignums) instead.
Remove bignum_butlast(), just set int_n to an appropriately large
integer if N is a bignum.
Accept bignums in check_sequence_range(), change the functions
that use check_sequence_range() appropriately.
Move the definition of NATNUMP() to number.h; document why it's a
reasonable name, contradicting an old comment.
tests/ChangeLog addition:
2010-11-20 Aidan Kehoe <kehoea@parhasard.net>
* automated/lisp-tests.el:
* automated/lisp-tests.el (featurep):
* automated/lisp-tests.el (wrong-type-argument):
* automated/mule-tests.el (featurep):
Check for args-out-of-range errors instead of wrong-type-argument
errors in various places when code is handed a large bignum
instead of a fixnum.
Also check for the wrong-type-argument errors when giving the same
code a non-integer value.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Sat, 20 Nov 2010 16:49:11 +0000 |
parents | 146742e30f05 |
children | fd714e8ba81e |
line wrap: on
line source
Package distributions may be placed in this directory. If present and a package-path is configured, packages can be installed using the top-level Makefile. To configure the package path, use the --with-late-packages option to configure, which specifies a single directory in which to install the xemacs-packages and mule-packages hierarchies provided. If this is null, or contains a Unix-style search path (i.e., a colon is present in the argument of the --with-late-packages option), you will have to install the packages by hand. To find out if a distribution includes bundled packages, type make check-available-packages There are three Make targets that may be available depending on the package sets supplied. make install-bootstrap-packages Install a selected set of packages sufficient to support downloading and installing packages via the M-x list-packages interface. Chose this if you want to be able to install the latest version of each package immediately. make install-nomule-packages Install the full distribution of packages that do not require a Mule-enabled XEmacs. Choose this package if you don't have a Mule-enabled XEmacs and want the convenience of a single-command installation. You can add or update packages via M-x list-packages at any time. make install-all-packages Install the full distribution of packages, including those requiring a Mule-enabled XEmacs. Choose this package if you have a Mule- enabled XEmacs and want the convenience of a single-command installation. You can add or update packages via M-x list-packages at any time. DISTRIBUTOR'S NOTE: you may choose what packages you wish to include in bootstrap.tar.gz, but to make list-packages work you need to include at least xemacs-base, dired, and efs. The tarball should unpack directly as an xemacs-packages tree (and optionaly, a mule-packages tree. Also, if either of xemacs-sumo.tar.gz or xemacs-mule-sumo.tar.gz is provided, the other should be as well. If packages are not available with the distribution, you can get them at ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo.tar.gz ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-mule-sumo.tar.gz http://turnbull.sk.tsukuba.ac.jp/Tools/XEmacs/bootstrap.tar.gz and place them in the same directory as this file. You can also make your own bootstrap.tar.gz by creating a directory xemacs-packages, then untarring the packages of your choice into that directory, and tarring the whole thing up with "tar czf bootstrap.tar.gz xemacs-packages". (If you wish to include mule-packages, you should place them in mule-packages as a sibling of xemacs-packages.) This facility currently does not support installations which configure the --with-early-packages, --with-late-packages, or --with-last-packages options. This facility currently will not overwrite an existing package installation, not even if a whole hierarchy (usually the mule-packages) is missing. In particular, you cannot use this feature to add the mule-packages to a package installation which lacks them, even if the hierarchy is missing, or the xemacs-packages hierarchy was installed this way. Nor can you "upgrade" a bootstrap installation to a full installation. If you wish to do any of these things you will need to remove the existing hierarchies.