CVS update by ben xemacs/src ...
18 years, 7 months
CVS Monitor
CVS Monitor
User: ben
Date: 05/09/27 07:32:26
Modified: xemacs/src ChangeLog sysdep.c nt.c
Log:
[21.4] Fix bugs in nt.c, sysdep.c
sysdep.c: Fix bit-rotted dup2 code. Also new -> new_.
nt.c: Fix possible use of uninitialized var. Also new -> new_.
Revision Changes Path
1.861 +12 -0 XEmacs/xemacs/src/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v
retrieving revision 1.860
retrieving revision 1.861
diff -u -p -r1.860 -r1.861
--- ChangeLog 2005/09/27 05:29:41 1.860
+++ ChangeLog 2005/09/27 05:32:19 1.861
＠＠ -1,5 +1,17 ＠＠
2005-09-27 Ben Wing <ben(a)xemacs.org>
+ * sysdep.c (emacs_set_tty):
+ * sysdep.c (qxe_link):
+ * sysdep.c (qxe_rename):
+ * sysdep.c (dup2):
+ Fix bit-rotted dup2 code. Also new -> new_.
+ * nt.c:
+ * nt.c (mswindows_closedir):
+ * nt.c (mswindows_link):
+ Fix possible use of uninitialized var. Also new -> new_.
+
+2005-09-27 Ben Wing <ben(a)xemacs.org>
+
* text.c (wcscmp_ascii):
* text.c (COPY_TEXT_BETWEEN_FORMATS):
* event-Xt.c (x_event_to_emacs_event):
1.83 +17 -17 XEmacs/xemacs/src/sysdep.c
Index: sysdep.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/sysdep.c,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -p -r1.82 -r1.83
--- sysdep.c 2005/06/26 18:05:05 1.82
+++ sysdep.c 2005/09/27 05:32:21 1.83
＠＠ -1458,19 +1458,19 ＠＠ emacs_set_tty (int fd, struct emacs_tty
}
else
{
- struct termios new;
+ struct termios new_;
/* Get the current settings, and see if they're what we asked for. */
- tcgetattr (fd, &new);
+ tcgetattr (fd, &new_);
/* We cannot use memcmp on the whole structure here because under
* aix386 the termios structure has some reserved field that may
* not be filled in.
*/
- if ( new.c_iflag == settings->main.c_iflag
- && new.c_oflag == settings->main.c_oflag
- && new.c_cflag == settings->main.c_cflag
- && new.c_lflag == settings->main.c_lflag
- && memcmp(new.c_cc, settings->main.c_cc, NCCS) == 0)
+ if ( new_.c_iflag == settings->main.c_iflag
+ && new_.c_oflag == settings->main.c_oflag
+ && new_.c_cflag == settings->main.c_cflag
+ && new_.c_lflag == settings->main.c_lflag
+ && memcmp(new_.c_cc, settings->main.c_cc, NCCS) == 0)
break;
else
continue;
＠＠ -3293,28 +3293,28 ＠＠ qxe_chmod (const Ibyte *path, mode_t mod
#if defined (HAVE_LINK)
int
-qxe_link (const Ibyte *existing, const Ibyte *new)
+qxe_link (const Ibyte *existing, const Ibyte *new_)
{
#ifdef WIN32_NATIVE
- return mswindows_link (existing, new);
+ return mswindows_link (existing, new_);
#else /* not WIN32_NATIVE */
Extbyte *existingout, *newout;
PATHNAME_CONVERT_OUT (existing, existingout);
- PATHNAME_CONVERT_OUT (new, newout);
+ PATHNAME_CONVERT_OUT (new_, newout);
return link (existingout, newout);
#endif /* WIN32_NATIVE */
}
#endif /* defined (HAVE_LINK) */
int
-qxe_rename (const Ibyte *old, const Ibyte *new)
+qxe_rename (const Ibyte *old, const Ibyte *new_)
{
#ifdef WIN32_NATIVE
- return mswindows_rename (old, new);
+ return mswindows_rename (old, new_);
#else /* not WIN32_NATIVE */
Extbyte *oldout, *newout;
PATHNAME_CONVERT_OUT (old, oldout);
- PATHNAME_CONVERT_OUT (new, newout);
+ PATHNAME_CONVERT_OUT (new_, newout);
return rename (oldout, newout);
#endif /* WIN32_NATIVE */
}
＠＠ -3594,12 +3594,12 ＠＠ dup2 (int oldd, int newd)
signal_ferror_with_frob (Qfile_error, lisp_strerror (errno),
"can't dup2 (%i, %i)", oldd, newd);
#else
- fd = dup (old);
+ fd = dup (oldd);
if (fd == -1)
return -1;
- if (fd == new)
- return new;
- ret = dup2 (old, new);
+ if (fd == newd)
+ return newd;
+ ret = dup2 (oldd, newd);
retry_close (fd);
return ret;
#endif /* F_DUPFD */
1.47 +5 -5 XEmacs/xemacs/src/nt.c
Index: nt.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/nt.c,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -p -r1.46 -r1.47
--- nt.c 2005/01/28 02:36:25 1.46
+++ nt.c 2005/09/27 05:32:22 1.47
＠＠ -1,6 +1,6 ＠＠
/* Utility and Unix shadow routines under MS Windows (WIN32_NATIVE defined).
Copyright (C) 1994, 1995 Free Software Foundation, Inc.
- Copyright (C) 2000, 2001, 2002, 2004 Ben Wing.
+ Copyright (C) 2000, 2001, 2002, 2004, 2005 Ben Wing.
This file is part of XEmacs.
＠＠ -834,7 +834,7 ＠＠ mswindows_opendir (const Ibyte *filename
int
mswindows_closedir (DIR *dirp)
{
- int retval;
+ int retval = -1;
/* If we have a find-handle open, close it. */
if (dir_find_handle != INVALID_HANDLE_VALUE)
＠＠ -1081,13 +1081,13 ＠＠ mswindows_access (const Ibyte *path, int
/* #### NT 5.0 has a function CreateHardLink to do this directly,
and it may do more things. */
int
-mswindows_link (const Ibyte *old, const Ibyte *new)
+mswindows_link (const Ibyte *old, const Ibyte *new_)
{
HANDLE fileh;
int result = -1;
Extbyte *oldext;
- if (old == NULL || new == NULL)
+ if (old == NULL || new_ == NULL)
{
errno = ENOENT;
return -1;
＠＠ -1114,7 +1114,7 ＠＠ mswindows_link (const Ibyte *old, const
WCHAR wbuffer[_MAX_PATH]; /* extra space for link name */
} data;
- TO_EXTERNAL_FORMAT (C_STRING, new,
+ TO_EXTERNAL_FORMAT (C_STRING, new_,
ALLOCA, (newuni, wlen), Qmswindows_unicode);
if (wlen / sizeof (WCHAR) < _MAX_PATH)
{
- 1 participants
- 0 comments
CVS update by ben xemacs/src, number-gmp.h ...
18 years, 7 months
CVS Monitor
CVS Monitor
User: ben
Date: 05/09/27 07:29:51
Modified: xemacs/src ChangeLog text.c event-Xt.c lisp.h number-gmp.c
number-gmp.h
Log:
fix compilation warnings
text.c, event-Xt.c, lisp.h, number-gmp.c, number-gmp.h: Fix compilation warnings. A couple of changes of new -> new_,
'foo -> `foo'.
Revision Changes Path
1.860 +13 -0 XEmacs/xemacs/src/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v
retrieving revision 1.859
retrieving revision 1.860
diff -u -p -r1.859 -r1.860
--- ChangeLog 2005/09/26 08:41:49 1.859
+++ ChangeLog 2005/09/27 05:29:41 1.860
＠＠ -1,3 +1,16 ＠＠
+2005-09-27 Ben Wing <ben(a)xemacs.org>
+
+ * text.c (wcscmp_ascii):
+ * text.c (COPY_TEXT_BETWEEN_FORMATS):
+ * event-Xt.c (x_event_to_emacs_event):
+ * event-Xt.c (ShellVisualPatch):
+ * lisp.h:
+ * lisp.h (assert_with_message):
+ * number-gmp.c (bigfloat_to_string):
+ * number-gmp.h:
+ Fix compilation warnings. A couple of changes of new -> new_,
+ 'foo -> `foo'.
+
2005-09-26 Ben Wing <ben(a)xemacs.org>
* specifier.c:
1.26 +2 -2 XEmacs/xemacs/src/text.c
Index: text.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/text.c,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -p -r1.25 -r1.26
--- text.c 2005/04/09 10:02:12 1.25
+++ text.c 2005/09/27 05:29:44 1.26
＠＠ -1686,7 +1686,7 ＠＠ wcscmp_ascii (const wchar_t *s1, const A
{
while (*s1 && *s2)
{
- if (*s1 != *s2)
+ if (*s1 != (wchar_t) *s2)
break;
s1++, s2++;
}
＠＠ -1809,7 +1809,7 ＠＠ do \
\
if (dstp + len <= dstend) \
{ \
- set_itext_ichar_fmt (dstp, ch, dstfmt, dstobj); \
+ (void) set_itext_ichar_fmt (dstp, ch, dstfmt, dstobj); \
dstp += len; \
} \
else \
1.87 +5 -4 XEmacs/xemacs/src/event-Xt.c
Index: event-Xt.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/event-Xt.c,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -p -r1.86 -r1.87
--- event-Xt.c 2005/07/03 21:48:00 1.86
+++ event-Xt.c 2005/09/27 05:29:44 1.87
＠＠ -1314,7 +1314,8 ＠＠ x_event_to_emacs_event (XEvent *x_event,
Ibyte *dataint;
len = strlen (data);
EXTERNAL_TO_C_STRING (data, dataint, Qfile_name);
- hurl = dnd_url_hexify_string (dataint, "file:");
+ hurl = dnd_url_hexify_string (dataint,
+ (const Ibyte *) "file:");
l_item = build_intstring (hurl);
l_dndlist = Fcons (l_item, l_dndlist);
data += len + 1;
＠＠ -3144,14 +3145,14 ＠＠ Information is displayed on stderr. Cur
static XtInitProc orig_shell_init_proc;
-static void ShellVisualPatch(Widget wanted, Widget new,
+static void ShellVisualPatch(Widget wanted, Widget new_,
ArgList args, Cardinal *num_args)
{
Widget p;
- ShellWidget w = (ShellWidget) new;
+ ShellWidget w = (ShellWidget) new_;
/* first, call the original setup */
- (*orig_shell_init_proc)(wanted, new, args, num_args);
+ (*orig_shell_init_proc)(wanted, new_, args, num_args);
/* if the visual isn't explicitly set, grab it from the nearest shell ancestor */
if (w->shell.visual == CopyFromParent) {
1.131 +8 -4 XEmacs/xemacs/src/lisp.h
Index: lisp.h
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/lisp.h,v
retrieving revision 1.130
retrieving revision 1.131
diff -u -p -r1.130 -r1.131
--- lisp.h 2005/07/17 20:08:48 1.130
+++ lisp.h 2005/09/27 05:29:45 1.131
＠＠ -506,7 +506,7 ＠＠ typedef EMACS_INT Memxpos;
them to be classes and using operator overloading. Unfortunately this
is a huge pain in the ass because C++ doesn't strongly distinguish
"bool" and "size_t" from int. The problem is especially bad with "bool"
- -- if you want to be able to say 'if (len--)' where len is e.g. a
+ -- if you want to be able to say `if (len--)' where len is e.g. a
Bytecount, you need to declare a conversion operator to bool(); and
since bool is just an alias for int, you suddenly get tons and tons of
ambiguities, which need to be resolved by lots of laborious declarations
＠＠ -1049,11 +1049,15 ＠＠ MODULE_API void assert_failed (const Asc
((x) ? (void) 0 : assert_failed (file, line, #x))
#elif defined (DEBUG_XEMACS)
# define assert(x) ((x) ? (void) 0 : (void) ABORT ())
-# define assert_with_message(x, msg) ((x) ? (void) 0 : (void) ABORT ())
+# define assert_with_message(x, msg) assert (x)
# define assert_at_line(x, file, line) assert (x)
#else
-# define assert(x) ((void) 0)
-# define assert_with_message(x, msg)
+/* This used to be ((void) (0)) but that triggers lots of unused variable
+ warnings. It's pointless to force all that code to be rewritten, with
+ added ifdefs. Any reasonable compiler will eliminate an expression with
+ no effects. */
+# define assert(x) ((void) (x))
+# define assert_with_message(x, msg) assert (x)
# define assert_at_line(x, file, line) assert (x)
#endif
1.5 +2 -2 XEmacs/xemacs/src/number-gmp.c
Index: number-gmp.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/number-gmp.c,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -p -r1.4 -r1.5
--- number-gmp.c 2004/11/04 23:06:45 1.4
+++ number-gmp.c 2005/09/27 05:29:45 1.5
＠＠ -66,8 +66,8 ＠＠ bigfloat_to_string(mpf_t f, int base)
/* Computerized scientific notation */
/* We need room for a radix point, format identifier, and exponent */
const int space = (expt < 0)
- ? (int)(log (-expt) / log (base)) + 3
- : (int)(log (expt) / log (base)) + 2;
+ ? (int)(log ((double) (-expt)) / log ((double) base)) + 3
+ : (int)(log ((double) expt) / log ((double) base)) + 2;
XREALLOC_ARRAY (str, CIbyte, len + space);
memmove (&str[neg + 2], &str[neg + 1], len - neg);
str[len + 1] = 'l';
1.4 +8 -0 XEmacs/xemacs/src/number-gmp.h
Index: number-gmp.h
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/number-gmp.h,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -p -r1.3 -r1.4
--- number-gmp.h 2005/02/03 16:14:07 1.3
+++ number-gmp.h 2005/09/27 05:29:45 1.4
＠＠ -35,7 +35,15 ＠＠ Boston, MA 02111-1307, USA. */
#undef __GNUC__
#endif
+#ifdef _MSC_VER
+/* "unary minus operator applied to unsigned type, result still unsigned":
+ Occurs on line 1596 of gmp.h in version 4.1.4. */
+#pragma warning ( disable : 4146 )
+#endif
#include <gmp.h>
+#ifdef _MSC_VER
+#pragma warning ( default : 4146 )
+#endif
typedef mpz_t bignum;
typedef mpq_t ratio;
- 1 participants
- 0 comments
CVS update by adrian xemacs/man/lispref ...
18 years, 7 months
CVS Monitor
CVS Monitor
User: adrian
Date: 05/09/27 00:19:06
Modified: xemacs/man/lispref packaging.texi
Log:
xemacs-21.5-clean: Getting texinfmt.el to compile core .texi again
-------------------- ChangeLog entries follow: --------------------
man/ChangeLog addition:
2005-09-27 Adrian Aichner <adrian(a)xemacs.org>
* lispref/packaging.texi: Get file to compile with teinfmt.el.
* lispref/packaging.texi (Packaging): Ditto.
* lispref/packaging.texi (Package Overview): Ditto.
* lispref/packaging.texi (The User View): Ditto.
* lispref/packaging.texi (The Library Maintainer View): Ditto.
* lispref/packaging.texi (Infrastructure): Ditto.
* lispref/packaging.texi (Obtaining): Ditto.
* lispref/packaging.texi (Local.rules File): Ditto.
* lispref/packaging.texi (package-info.in): Ditto.
* lispref/packaging.texi (Makefile): Ditto.
* lispref/packaging.texi (Documenting Packages): Ditto.
2005-09-27 Adrian Aichner <adrian(a)xemacs.org>
* internals/internals.texi (A Summary of the Various XEmacs
Modules): Get file to compile with texinfmt.el.
* internals/internals.texi (Windows Build Flags): Ditto.
Revision Changes Path
1.313 +20 -0 XEmacs/xemacs/man/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/ChangeLog,v
retrieving revision 1.312
retrieving revision 1.313
diff -u -p -r1.312 -r1.313
--- ChangeLog 2005/09/26 08:41:45 1.312
+++ ChangeLog 2005/09/26 22:18:59 1.313
＠＠ -1,3 +1,23 ＠＠
+2005-09-27 Adrian Aichner <adrian(a)xemacs.org>
+
+ * lispref/packaging.texi: Get file to compile with teinfmt.el.
+ * lispref/packaging.texi (Packaging): Ditto.
+ * lispref/packaging.texi (Package Overview): Ditto.
+ * lispref/packaging.texi (The User View): Ditto.
+ * lispref/packaging.texi (The Library Maintainer View): Ditto.
+ * lispref/packaging.texi (Infrastructure): Ditto.
+ * lispref/packaging.texi (Obtaining): Ditto.
+ * lispref/packaging.texi (Local.rules File): Ditto.
+ * lispref/packaging.texi (package-info.in): Ditto.
+ * lispref/packaging.texi (Makefile): Ditto.
+ * lispref/packaging.texi (Documenting Packages): Ditto.
+
+2005-09-27 Adrian Aichner <adrian(a)xemacs.org>
+
+ * internals/internals.texi (A Summary of the Various XEmacs
+ Modules): Get file to compile with texinfmt.el.
+ * internals/internals.texi (Windows Build Flags): Ditto.
+
2005-09-26 Ben Wing <ben(a)xemacs.org>
* lispref/glyphs.texi (Images):
1.68 +3 -2 XEmacs/xemacs/man/internals/internals.texi
Index: internals.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/internals/internals.texi,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -p -r1.67 -r1.68
--- internals.texi 2005/06/26 18:04:56 1.67
+++ internals.texi 2005/09/26 22:19:02 1.68
＠＠ -2774,7 +2774,8 ＠＠ question.
The following table contains cross-references from each module in XEmacs
21.5 to the section (if any) describing it.
-＠multitable {(a)file{intl-auto-encap-win32.c}} {＠ref{Modules for Other Aspects of the Lisp Interpreter and Object System}}
+＠multitable ＠columnfractions .25 .75
+＠item ＠file{intl-auto-encap-win32.c} ＠tab ＠ref{Modules for Other Aspects of the Lisp Interpreter and Object System}.
＠item ＠file{Emacs.ad.h} ＠tab ＠ref{Modules for Interfacing with X Windows}.
＠item ＠file{EmacsFrame.c} ＠tab ＠ref{Modules for Interfacing with X Windows}.
＠item ＠file{EmacsFrame.h} ＠tab ＠ref{Modules for Interfacing with X Windows}.
＠＠ -17504,7 +17505,7 ＠＠ code from GNU Emacs and such:
＠c ＠multitable {Old Constant} {determine whether this code is really specific to MS-DOS (and not Windows -- e.g. DJGPP code}
＠multitable ＠columnfractions .25 .75
＠item Old Constant ＠tab New Constant
-＠item ----------------------------------------------------------------
+＠item ---------------------------------------------------------------- ＠tab
＠item ＠code{WINDOWSNT}
＠tab ＠code{WIN32_NATIVE}
＠item ＠code{WIN32}
1.12 +33 -37 XEmacs/xemacs/man/lispref/packaging.texi
Index: packaging.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/packaging.texi,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -p -r1.11 -r1.12
--- packaging.texi 2003/10/10 12:39:34 1.11
+++ packaging.texi 2005/09/26 22:19:05 1.12
＠＠ -8,18 +8,14 ＠＠
＠c Macro to make formatting of the XEmacs pms name consistent.
＠c Maybe ＠sc looks OK in HTML? If so, condition on Info.
＠iftex
-＠macro xpms
-XE＠sc{macs} Packaging System
-＠end macro
+＠set xpms XE＠sc{macs} Packaging System
＠end iftex
＠ifnottex
-＠macro xpms
-XEmacs Packaging System
-＠end macro
+＠set xpms XEmacs Packaging System
＠end ifnottex
＠node Packaging, Lisp Data Types, Introduction, Top
-＠chapter The ＠xpms{}
+＠chapter The ＠value{xpms}
＠cindex package
＠cindex packaging
＠＠ -32,7 +28,7 ＠＠ easy. This gives an installer the abili
installation for local needs with safe removal of unnecessary code.
This chapter describes how to package Lisp libraries for use with the
-＠xpms{}.
+＠value{xpms}.
＠emph{Please note carefully} that the term ＠dfn{package} as used in
XEmacs refers to an aggregation of Lisp code and/or data distributed as
＠＠ -50,13 +46,13 ＠＠ Packaging Lisp Libraries:
* Package Terminology:: Basic stuff.
* Building Packages:: Turn packaged source into a tarball.
* Makefile Targets:: Package ＠file{Makefile} targets
-* Local.rules File:: Tell the ＠xpms{} about your host.
-* Creating Packages:: Tell the ＠xpms{} about your package.
+* Local.rules File:: Tell the ＠value{xpms} about your host.
+* Creating Packages:: Tell the ＠value{xpms} about your package.
* Documenting Packages:: Explain your package to users and hackers.
-＠c * History:: History of the ＠xpms{}
-＠c * Installation:: Installing the ＠xpms{} with your (X)Emacs.
-＠c * Configuration:: Configuring the ＠xpms{} for use.
-＠c * Usage:: An overview of the operation of the ＠xpms{}.
+＠c * History:: History of the ＠value{xpms}
+＠c * Installation:: Installing the ＠value{xpms} with your (X)Emacs.
+＠c * Configuration:: Configuring the ＠value{xpms} for use.
+＠c * Usage:: An overview of the operation of the ＠value{xpms}.
＠c * Bug Reports:: Reporting Bugs and Problems
＠c * Frequently Asked Questions:: Questions and answers from the mailing list.
＠＠ -65,9 +61,9 ＠＠ Internals and Package Release Engineerin
＠end menu
＠node Package Overview, Package Terminology, , Packaging
-＠chapter An overview of the ＠xpms{}
+＠chapter An overview of the ＠value{xpms}
-The ＠xpms{} is a system for administering the installation, upgrade, and
+The ＠value{xpms} is a system for administering the installation, upgrade, and
removal of Lisp libraries. For the end user, it provides facilities for
determining availability of packages and which versions at remote
sites. It will download and automatically install a package, ensuring
＠＠ -92,10 +88,10 ＠＠ the structure of an installed package.
Meeting these requirements, as well as simply providing the
auto-autoloads and the information about availability and so on does
-impose some costs on the library maintainer. The ＠xpms{} also provides
+impose some costs on the library maintainer. The ＠value{xpms} also provides
structure and utilities to the library maintainer to make these tasks
easier. This manual documents the requirements and the tools that the
-＠xpms{} provides to ensure that a package satisfies them.
+＠value{xpms} provides to ensure that a package satisfies them.
＠menu
* The User View::
＠＠ -122,7 +118,7 ＠＠ unpacked from the top of a package hiera
is basically an image of a classic Emacs ``run-in-place'' tree, with
＠file{lisp}, ＠file{etc}, ＠file{info}, ＠file{man}, ＠file{lib-src}, and
＠file{pkginfo} subdirectories of the top. The ＠file{pkginfo}
-subdirectory is for use by the ＠xpms{} administration tools, and
+subdirectory is for use by the ＠value{xpms} administration tools, and
currently contains a ＠file{MANIFEST.＠var{package-name}} file for each
package to ensure that no cruft remains when a package is removed or
updated. The ＠file{lisp}, ＠file{etc}, and ＠file{lib-src} subdirectories
＠＠ -242,7 +238,7 ＠＠ receiving a ＠code{load-path} initialized
＠node The Library Maintainer View, The Package Release Engineer View, The User View, Package Overview
＠section The Library Maintainer View
-From the library maintainer's viewpoint, the advantages to the ＠xpms{}
+From the library maintainer's viewpoint, the advantages to the ＠value{xpms}
stem from the convenience to the user of installation and upgrade.
Since an installed package automatically registers its entry points via
autoload and its configuration variables with the Customize system,
＠＠ -252,14 +248,14 ＠＠ posting a FAQ whose answer is ``long sin
This comes at some cost, as the library maintainer needs to arrange that
the package be installed in a directory structure that satisfies the
-requirements of the ＠xpms{}. Autoload cookies and defcustoms must also
-be added to existing libraries. The ＠xpms{} provides infrastructure to
+requirements of the ＠value{xpms}. Autoload cookies and defcustoms must also
+be added to existing libraries. The ＠value{xpms} provides infrastructure to
assure that all of these annoyances need only be dealt with once. The
autoload cookies and defcustoms are beyond the scope of this chapter, but
most maintainers of modern packages are already familiar with these
mechanisms.
-The ＠xpms{} may be divided into the ＠dfn{infrastructure} common to all
+The ＠value{xpms} may be divided into the ＠dfn{infrastructure} common to all
packages, and the package-specific ＠dfn{control files}. The
infrastructure supports global builds, installation, and generation of
the ``sumo'' bundles of packages, as well as generation of individual
＠＠ -269,13 +265,13 ＠＠ package's source tree and provide admini
＠menu
* Infrastructure:: Global Makefiles and common rules.
* Control Files:: Package-specific Makefiles and administrative files.
-* Obtaining:: Obtaining the ＠xpms{} and required utilities.
+* Obtaining:: Obtaining the ＠value{xpms} and required utilities.
＠end menu
＠node Infrastructure, Control Files, , The Library Maintainer View
＠subsection Infrastructure
-In order to get the greatest benefit from the ＠xpms{}, a library
+In order to get the greatest benefit from the ＠value{xpms}, a library
maintainer should place the package sources in an appropriate place in
the XEmacs source package hierarchy, and arrange to have the source
package imported into the XEmacs CVS repository.
＠＠ -412,14 +408,14 ＠＠ forms for the usre configuration variabl
＠node Obtaining, , Control Files, The Library Maintainer View
-＠subsection Obtaining the ＠xpms{} and Required Utilities
+＠subsection Obtaining the ＠value{xpms} and Required Utilities
Currently both the infrastructure for creating XEmacs packages and the
package sources themselves are available only by CVS. See
＠uref{http://www.xemacs.org/Develop/cvsaccess.html} for more
intformation.
-The ＠xpms{} currently requires GNU ＠file{make}, and XEmacs, to build
+The ＠value{xpms} currently requires GNU ＠file{make}, and XEmacs, to build
packages.
＠＠ -617,7 +613,7 ＠＠ Does most of the work. Builds the elcs,
＠comment node-name, next, previous, up
＠cindex local.rules
＠heading The Local.rules File:
-This file in ＠file{packages} provides the ＠xpms{} with information about
+This file in ＠file{packages} provides the ＠value{xpms} with information about
the local configuration and environment. To create ＠file{Local.rules},
simply copy ＠file{Local.rules.template} from that directory to
＠file{Local.rules} and edit it to suit your needs.
＠＠ -905,7 +901,7 ＠＠ The ＠samp{category} of the package. It
packages. The is also provision for ＠samp{unsupported} in this field
which would be for packages that XEmacs.org do not distribute.
-(a)strong{N.B.} As yet, the ＠xpms{} does ＠emph{not} support this type of
+(a)strong{N.B.} As yet, the ＠value{xpms} does ＠emph{not} support this type of
package. It will in the future.
＠item dump
＠＠ -983,7 +979,7 ＠＠ specified in the ＠samp{REQUIRES} variabl
some cases the ＠samp{PRELOADS} (autoloads used in libraries mentioned
in ＠samp{PRELOADS}).
-There isn't much to an ＠xpms{} ＠file{Makefile}, basically it just
+There isn't much to an ＠value{xpms} ＠file{Makefile}, basically it just
contains a few ＠file{Makefile} variables and that's it. See the
example.
＠＠ -1040,11 +1036,11 ＠＠ be the first to need such hackery and it
for.
＠subheading ＠file{Makefile} Variables Explained:
-A number of ＠file{make} variables are defined by the ＠xpms{}. Some are
+A number of ＠file{make} variables are defined by the ＠value{xpms}. Some are
required, others are optional. Of course your ＠file{Makefile} may
define other variables for private use, but you should be careful not to
choose names that conflict with variables defined and used by the
-＠xpms{}.
+＠value{xpms}.
The required variables are described in the table below.
The corresponding field names for ＠file{package-info.in}, where
＠＠ -1280,7 +1276,7 ＠＠ rules to build these files.
＠section ＠file{package-compile.el}
＠cindex package-compile.el
＠cindex compiling packages
-The ＠xpms{} does not automatically become aware of your package simply
+The ＠value{xpms} does not automatically become aware of your package simply
because there is a new subtree. If any package, including your own,
requires any of your files, it must be explicitly added to the compile
environment or loads/requires that search load-path will fail. The
＠＠ -1288,7 +1284,7 ＠＠ changes that need to be made are
＠table ＠strong
＠item an entry in ＠code{package-directory-map}
-This tells the ＠xpms{} which distribution (currently
+This tells the ＠value{xpms} which distribution (currently
＠samp{xemacs-packages} or ＠samp{mule-packages}) your package is found
in. It then looks in the distribution subdirectory whose name is the
same as the package's.
＠＠ -1300,13 +1296,13 ＠＠ tree, eg, in ＠file{packages/xemacs-packa
＠end table
This only needs to be done once, when the package is first added to the
-＠xpms{}. (Well, when you randomly change the subdirectory layout, too.)
+＠value{xpms}. (Well, when you randomly change the subdirectory layout, too.)
Your changes to ＠file{package-compile.el} must be cleared and checked in
by the XEmacs Package Release Engineer before your package will build
correctly from a fresh checkout.
This is unfortunate; it works pretty well once set up, but can cause
-confusion when first building a package in the ＠xpms{} context. In
+confusion when first building a package in the ＠value{xpms} context. In
particular, if the ＠code{package-directory-map} entry for a required
package, including the package itself, is not found, the necessary
requires will not be executed by ＠file{package-compile.el}. If
＠＠ -1333,7 +1329,7 ＠＠ Some random notes on documenting your pa
Do write a Texinfo file. It's not that hard to do basically, and even
using the more advanced features of Texinfo soon become natural. For a
start, just grab the template ＠file{Samples/package.texi} from the
-＠xpms{} source tree, and drop your current README into the Top node. At
+＠value{xpms} source tree, and drop your current README into the Top node. At
least this way your documentation will be accessible from the standard
Info readers. Next, try to add lots of cross-referencing and logical
markup, and then node structure.
- 1 participants
- 0 comments
CVS update by viteno xemacs ...
18 years, 7 months
CVS Monitor
CVS Monitor
User: viteno
Date: 05/09/26 23:51:29
Modified: xemacs version.sh
Log:
Update xemacs_extra_name.
Revision Changes Path
1.1295 +1 -1 XEmacs/xemacs/version.sh
Index: version.sh
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/version.sh,v
retrieving revision 1.1294
retrieving revision 1.1295
diff -u -p -r1.1294 -r1.1295
--- version.sh 2005/09/25 21:51:12 1.1294
+++ version.sh 2005/09/26 21:51:28 1.1295
＠＠ -8,5 +8,5 ＠＠ emacs_kit_version=
infodock_major_version=4
infodock_minor_version=0
infodock_build_version=8
-xemacs_extra_name="(+CVS-20050925)"
+xemacs_extra_name="(+CVS-20050926)"
xemacs_release_date="2005-02-18"
- 1 participants
- 0 comments
CVS update by ben xemacs/man/lispref ...
18 years, 7 months
CVS Monitor
CVS Monitor
User: ben
Date: 05/09/26 10:41:58
Modified: xemacs/man/lispref glyphs.texi lispref.texi specifiers.texi
Log:
add specifier-instantiator and friends
specifier.c: Add `specifier-instantiator' and related primitives.
lispref/glyphs.texi, lispref/lispref.texi, lispref/specifiers.texi: Use "instantiation" not "instancing". Fix some places where
"specifier" is used to mean "instantiator".
Revision Changes Path
1.312 +23 -0 XEmacs/xemacs/man/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/ChangeLog,v
retrieving revision 1.311
retrieving revision 1.312
diff -u -p -r1.311 -r1.312
--- ChangeLog 2005/09/25 21:40:17 1.311
+++ ChangeLog 2005/09/26 08:41:45 1.312
＠＠ -1,3 +1,26 ＠＠
+2005-09-26 Ben Wing <ben(a)xemacs.org>
+
+ * lispref/glyphs.texi (Images):
+ * lispref/glyphs.texi (Image Instantiators):
+ * lispref/glyphs.texi (Image Instantiator Formats):
+ * lispref/glyphs.texi (Image Instances):
+ * lispref/glyphs.texi (Image Instance Functions):
+ * lispref/glyphs.texi (Creating Glyphs):
+ * lispref/glyphs.texi (Lisp API to Native Widgets):
+ * lispref/glyphs.texi (Glyph Properties):
+ * lispref/glyphs.texi (Glyph Examples):
+ * lispref/lispref.texi (Top):
+ * lispref/specifiers.texi (Specifiers):
+ * lispref/specifiers.texi (Introduction to Specifiers):
+ * lispref/specifiers.texi (Simple Specifier Usage):
+ * lispref/specifiers.texi (Specifiers In-Depth):
+ * lispref/specifiers.texi (Specifier Instantiation):
+ * lispref/specifiers.texi (Retrieving Specifications):
+ * lispref/specifiers.texi (Specifier Tag Functions):
+ * lispref/specifiers.texi (Specifier Validation Functions):
+ Use "instantiation" not "instancing". Fix some places where
+ "specifier" is used to mean "instantiator".
+
2005-09-25 Adrian Aichner <adrian(a)xemacs.org>
* lispref/compile.texi (Compilation Options): Supply missing
1.859 +23 -0 XEmacs/xemacs/src/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v
retrieving revision 1.858
retrieving revision 1.859
diff -u -p -r1.858 -r1.859
--- ChangeLog 2005/09/26 08:29:27 1.858
+++ ChangeLog 2005/09/26 08:41:49 1.859
＠＠ -1,5 +1,28 ＠＠
2005-09-26 Ben Wing <ben(a)xemacs.org>
+ * specifier.c:
+ * specifier.c (Fvalid_specifier_type_p):
+ * specifier.c (Fvalid_specifier_locale_p):
+ * specifier.c (Fvalid_specifier_domain_p):
+ * specifier.c (Fvalid_specifier_locale_type_p):
+ * specifier.c (Fdefine_specifier_tag):
+ * specifier.c (specifier_get_external_inst_list):
+ * specifier.c (Fspecifier_specs):
+ * specifier.c (Fspecifier_fallback):
+ * specifier.c (specifier_instance_from_inst_list):
+ * specifier.c (CHECK_INSTANCE_ENTRY):
+ * specifier.c (specifier_instance_1):
+ * specifier.c (specifier_instance):
+ * specifier.c (specifier_matching_foo):
+ * specifier.c (Fspecifier_instance):
+ * specifier.c (Fspecifier_instantiator):
+ * specifier.c (Fspecifier_matching_instance):
+ * specifier.c (specifier_matching_foo_from_inst_list):
+ * specifier.c (syms_of_specifier):
+ Add `specifier-instantiator' and related primitives.
+
+2005-09-26 Ben Wing <ben(a)xemacs.org>
+
* rangetab.c:
* rangetab.c (Fmap_range_table):
Fix bug in handling of range endpoints when not start-closed, end-open.
1.41 +245 -113 XEmacs/xemacs/src/specifier.c
Index: specifier.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/specifier.c,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -p -r1.40 -r1.41
--- specifier.c 2005/04/08 23:11:32 1.40
+++ specifier.c 2005/09/26 08:41:51 1.41
＠＠ -1,6 +1,6 ＠＠
/* Specifier implementation
Copyright (C) 1994, 1995 Board of Trustees, University of Illinois.
- Copyright (C) 1995, 1996, 2002 Ben Wing.
+ Copyright (C) 1995, 1996, 2002, 2005 Ben Wing.
Copyright (C) 1995 Sun Microsystems, Inc.
This file is part of XEmacs.
＠＠ -23,9 +23,8 ＠＠ Boston, MA 02111-1307, USA. */
/* Synched up with: Not in FSF. */
/* Design by Ben Wing;
- Original version by Chuck Thompson;
- rewritten by Ben Wing;
- Magic specifiers by Kirill Katsnelson;
+ Written by Ben Wing based on prototype for 19.12 by Chuck Thompson.
+ Magic specifiers by Kirill Katsnelson.
*/
#include <config.h>
＠＠ -460,8 +459,8 ＠＠ valid_specifier_type_p (Lisp_Object type
DEFUN ("valid-specifier-type-p", Fvalid_specifier_type_p, 1, 1, 0, /*
Given a SPECIFIER-TYPE, return non-nil if it is valid.
-Valid types are 'generic, 'integer, 'boolean, 'color, 'font, 'image,
-'face-boolean, and 'toolbar.
+Valid types are `generic', `integer', `boolean', `color', `font', `image',
+`face-boolean', and `toolbar'.
*/
(specifier_type))
{
＠＠ -578,8 +577,11 ＠＠ lower-level functions `add-spec-to-speci
`add-spec-list-to-specifier'. You can also temporarily bind a setting
to a specifier using `let-specifier'. To retrieve settings, use
`specifier-specs', or its lower-level counterpart
-`specifier-spec-list'. To determine the actual value, use
-`specifier-instance'.
+`specifier-spec-list'.
+
+To determine the actual value (i.e. the instance) in a particular domain, use
+`specifier-instance'. To determine the corresponding setting that yielded
+the value (i.e. the instantiator), use `specifier-instantiator'.
For more information, see `set-specifier', `specifier-instance',
`specifier-specs', and `add-spec-to-specifier'; or, for a detailed
＠＠ -588,9 +590,9 ＠＠ process works, see the chapter on specif
Reference Manual.
TYPE specifies the particular type of specifier, and should be one of
-the symbols 'generic, 'integer, 'natnum, 'boolean, 'color, 'font,
-'image, 'face-boolean, 'display-table, 'gutter, 'gutter-size,
-'gutter-visible or 'toolbar.
+the symbols `generic', `integer', `natnum', `boolean', `color', `font',
+`image', `face-boolean', `display-table', `gutter', `gutter-size',
+`gutter-visible' or `toolbar'.
For more information on particular types of specifiers, see the
functions `make-generic-specifier', `make-integer-specifier',
＠＠ -637,7 +639,7 ＠＠ Return the type of SPECIFIER.
DEFUN ("valid-specifier-locale-p", Fvalid_specifier_locale_p, 1, 1, 0, /*
Return t if LOCALE is a valid specifier locale.
-Valid locales are devices, frames, windows, buffers, and 'global.
+Valid locales are devices, frames, windows, buffers, and `global'.
\(nil is not valid.)
*/
(locale))
＠＠ -655,7 +657,7 ＠＠ Valid locales are devices, frames, windo
DEFUN ("valid-specifier-domain-p", Fvalid_specifier_domain_p, 1, 1, 0, /*
Return t if DOMAIN is a valid specifier domain.
-A domain is used to instance a specifier (i.e. determine the specifier's
+A domain is used to instantiate a specifier (i.e. determine the specifier's
value in that domain). Valid domains are image instances, windows, frames,
and devices. \(nil is not valid.) image instances are pseudo-domains since
instantiation will actually occur in the window the image instance itself is
＠＠ -675,9 +677,9 ＠＠ instantiated in.
DEFUN ("valid-specifier-locale-type-p", Fvalid_specifier_locale_type_p, 1, 1, 0,
/*
Given a specifier LOCALE-TYPE, return non-nil if it is valid.
-Valid locale types are 'global, 'device, 'frame, 'window, and 'buffer.
+Valid locale types are `global', `device', `frame', `window', and `buffer'.
\(Note, however, that in functions that accept either a locale or a locale
-type, 'global is considered an individual locale.)
+type, `global' is considered an individual locale.)
*/
(locale_type))
{
＠＠ -828,8 +830,8 ＠＠ Each tag has a predicate associated with
that tag applies to a particular device. The tags which are device types
and classes match devices of that type or class. User-defined tags can
have any predicate, or none (meaning that all devices match). When
-attempting to instance a specifier, a particular instantiator is only
-considered if the device of the domain being instanced over matches
+attempting to instantiate a specifier, a particular instantiator is only
+considered if the device of the domain being instantiated over matches
all tags in the tag set attached to that instantiator.
Most of the time, a tag set is not specified, and the instantiator
＠＠ -976,7 +978,7 ＠＠ device. If PREDICATE is omitted, the ta
You can redefine an existing user-defined specifier tag. However,
you cannot redefine the built-in specifier tags (the device types
-and classes) or the symbols nil, t, 'all, or 'global.
+and classes) or the symbols nil, t, `all', or `global'.
*/
(tag, predicate))
{
＠＠ -990,7 +992,7 ＠＠ and classes) or the symbols nil, t, 'all
/* Try to prevent common instantiators and locales from being
redefined, to reduce ambiguity */
if (NILP (tag) || EQ (tag, Qt) || EQ (tag, Qall) || EQ (tag, Qglobal))
- invalid_change ("Cannot define nil, t, 'all, or 'global", tag);
+ invalid_change ("Cannot define nil, t, `all', or `global'", tag);
assoc = assq_no_quit (tag, Vuser_defined_tags);
if (NILP (assoc))
{
＠＠ -1476,7 +1478,7 ＠＠ specifier_get_external_inst_list (Lisp_O
type);
if (!inst_list || NILP (*inst_list))
{
- /* nil for *inst_list should only occur in 'global */
+ /* nil for *inst_list should only occur in `global' */
assert (!inst_list || EQ (locale, Qglobal));
return Qnil;
}
＠＠ -1834,12 +1836,12 ＠＠ specifier_copy_locale_type (Lisp_Object
/* map MAPFUN over the locales in SPECIFIER that are given in LOCALE.
CLOSURE is passed unchanged to MAPFUN. LOCALE can be one of
- -- nil (same as 'all)
- -- a single locale, locale type, or 'all
- -- a list of locales, locale types, and/or 'all
+ -- nil (same as `all')
+ -- a single locale, locale type, or `all'
+ -- a list of locales, locale types, and/or `all'
- MAPFUN is called for each locale and locale type given; for 'all,
- it is called for the locale 'global and for the four possible
+ MAPFUN is called for each locale and locale type given; for `all',
+ it is called for the locale `global' and for the four possible
locale types. In each invocation, either LOCALE will be a locale
and LOCALE_TYPE will be the locale type of this locale,
or LOCALE will be nil and LOCALE_TYPE will be a locale type.
＠＠ -1920,7 +1922,7 ＠＠ map_specifier (Lisp_Object specifier, Li
DEFUN ("add-spec-to-specifier", Fadd_spec_to_specifier, 2, 5, 0, /*
Add a specification to SPECIFIER.
The specification maps from LOCALE (which should be a window, buffer,
-frame, device, or 'global, and defaults to 'global) to INSTANTIATOR,
+frame, device, or `global', and defaults to `global') to INSTANTIATOR,
whose allowed values depend on the type of the specifier. Optional
argument TAG-SET limits the instantiator to apply only to the specified
tag set, which should be a list of tags all of which must match the
＠＠ -1931,26 +1933,26 ＠＠ containing that symbol. Optional argume
do if there are already specifications in the specifier.
It should be one of
- 'prepend Put at the beginning of the current list of
+ `prepend' Put at the beginning of the current list of
instantiators for LOCALE.
- 'append Add to the end of the current list of
+ `append' Add to the end of the current list of
instantiators for LOCALE.
- 'remove-tag-set-prepend (this is the default)
+ `remove-tag-set-prepend' (this is the default)
Remove any existing instantiators whose tag set is
the same as TAG-SET; then put the new instantiator
at the beginning of the current list. ("Same tag
set" means that they contain the same elements.
The order may be different.)
- 'remove-tag-set-append
+ `remove-tag-set-append'
Remove any existing instantiators whose tag set is
the same as TAG-SET; then put the new instantiator
at the end of the current list.
- 'remove-locale Remove all previous instantiators for this locale
+ `remove-locale' Remove all previous instantiators for this locale
before adding the new spec.
- 'remove-locale-type Remove all specifications for all locales of the
+ `remove-locale-type' Remove all specifications for all locales of the
same type as LOCALE (this includes LOCALE itself)
before adding the new spec.
- 'remove-all Remove all specifications from the specifier
+ `remove-all' Remove all specifications from the specifier
before adding the new spec.
You can retrieve the specifications for a particular locale or locale type
＠＠ -1989,7 +1991,7 ＠＠ The format of SPEC-LIST is
((LOCALE (TAG-SET . INSTANTIATOR) ...) ...)
where
- LOCALE := a window, a buffer, a frame, a device, or 'global
+ LOCALE := a window, a buffer, a frame, a device, or `global'
TAG-SET := an unordered list of zero or more TAGS, each of which
is a symbol
TAG := a device class (see `valid-device-class-p'), a device type
＠＠ -2105,17 +2107,17 ＠＠ DEFUN ("specifier-spec-list", Fspecifier
Return the spec-list of specifications for SPECIFIER in LOCALE.
If LOCALE is a particular locale (a buffer, window, frame, device,
-or 'global), a spec-list consisting of the specification for that
+or `global'), a spec-list consisting of the specification for that
locale will be returned.
-If LOCALE is a locale type (i.e. 'buffer, 'window, 'frame, or 'device),
+If LOCALE is a locale type (i.e. `buffer', `window', `frame', or `device'),
a spec-list of the specifications for all locales of that type will be
returned.
-If LOCALE is nil or 'all, a spec-list of all specifications in SPECIFIER
+If LOCALE is nil or `all', a spec-list of all specifications in SPECIFIER
will be returned.
-LOCALE can also be a list of locales, locale types, and/or 'all; the
+LOCALE can also be a list of locales, locale types, and/or `all'; the
result is as if `specifier-spec-list' were called on each element of the
list and the results concatenated together.
＠＠ -2155,11 +2157,11 ＠＠ in Lisp programs, and is as follows:
1. If there is only one instantiator, then an inst-pair (i.e. cons of
tag and instantiator) will be returned; otherwise a list of
inst-pairs will be returned.
-2. For each inst-pair returned, if the instantiator's tag is 'any,
+2. For each inst-pair returned, if the instantiator's tag is `any',
the tag will be removed and the instantiator itself will be returned
instead of the inst-pair.
3. If there is only one instantiator, its value is nil, and its tag is
- 'any, a one-element list containing nil will be returned rather
+ `any', a one-element list containing nil will be returned rather
than just nil, to distinguish this case from there being no
instantiators at all.
*/
＠＠ -2205,15 +2207,15 ＠＠ DEFUN ("remove-specifier", Fremove_speci
Remove specification(s) for SPECIFIER.
If LOCALE is a particular locale (a window, buffer, frame, device,
-or 'global), the specification for that locale will be removed.
+or `global'), the specification for that locale will be removed.
-If instead, LOCALE is a locale type (i.e. 'window, 'buffer, 'frame,
-or 'device), the specifications for all locales of that type will be
+If instead, LOCALE is a locale type (i.e. `window', `buffer', `frame',
+or `device'), the specifications for all locales of that type will be
removed.
-If LOCALE is nil or 'all, all specifications will be removed.
+If LOCALE is nil or `all', all specifications will be removed.
-LOCALE can also be a list of locales, locale types, and/or 'all; this
+LOCALE can also be a list of locales, locale types, and/or `all'; this
is equivalent to calling `remove-specifier' for each of the elements
in the list.
＠＠ -2284,11 +2286,11 ＠＠ If DEST is nil or omitted, a new specifi
specifications copied into it. Otherwise, the specifications will be
copied into the existing specifier in DEST.
-If LOCALE is nil or 'all, all specifications will be copied. If LOCALE
+If LOCALE is nil or `all', all specifications will be copied. If LOCALE
is a particular locale, the specification for that particular locale will
be copied. If LOCALE is a locale type, the specifications for all locales
of that type will be copied. LOCALE can also be a list of locales,
-locale types, and/or 'all; this is equivalent to calling `copy-specifier'
+locale types, and/or `all'; this is equivalent to calling `copy-specifier'
for each of the elements of the list. See `specifier-spec-list' for more
information about LOCALE.
＠＠ -2339,7 +2341,7 ＠＠ the same as in `add-spec-to-specifier'.
/************************************************************************/
-/* Instancing */
+/* Instantiation */
/************************************************************************/
static Lisp_Object
＠＠ -2440,20 +2442,20 ＠＠ set_specifier_fallback (Lisp_Object spec
DEFUN ("specifier-fallback", Fspecifier_fallback, 1, 1, 0, /*
Return the fallback value for SPECIFIER.
Fallback values are provided by the C code for certain built-in
-specifiers to make sure that instancing won't fail even if all
+specifiers to make sure that instantiation won't fail even if all
specs are removed from the specifier, or to implement simple
inheritance behavior (e.g. this method is used to ensure that
-faces other than 'default inherit their attributes from 'default).
+faces other than `default' inherit their attributes from `default').
By design, you cannot change the fallback value, and specifiers
created with `make-specifier' will never have a fallback (although
a similar, Lisp-accessible capability may be provided in the future
to allow for inheritance).
-The fallback value will be an inst-list that is instanced like
+The fallback value will be an inst-list that is instantiated like
any other inst-list, a specifier of the same type as SPECIFIER
\(results in inheritance), or nil for no fallback.
-When you instance a specifier, you can explicitly request that the
+When you instantiate a specifier, you can explicitly request that the
fallback not be consulted. (The C code does this, for example, when
merging faces.) See `specifier-instance'.
*/
＠＠ -2469,7 +2471,8 ＠＠ specifier_instance_from_inst_list (Lisp_
Lisp_Object domain,
Lisp_Object inst_list,
Error_Behavior errb, int no_quit,
- Lisp_Object depth)
+ Lisp_Object depth,
+ Lisp_Object *instantiator)
{
/* This function can GC */
Lisp_Specifier *sp;
＠＠ -2498,7 +2501,9 ＠＠ specifier_instance_from_inst_list (Lisp_
if (device_matches_specifier_tag_set_p (device, tag_set))
{
Lisp_Object val = XCDR (tagged_inst);
+ Lisp_Object the_instantiator = val;
+
if (HAS_SPECMETH_P (sp, instantiate))
val = call_with_suspended_errors
((lisp_fn_t) RAW_SPECMETH (sp, instantiate),
＠＠ -2509,6 +2514,8 ＠＠ specifier_instance_from_inst_list (Lisp_
{
unbind_to (count);
UNGCPRO;
+ if (instantiator)
+ *instantiator = the_instantiator;
return val;
}
}
＠＠ -2532,7 +2539,8 ＠＠ specifier_instance_from_inst_list (Lisp_
Lisp_Object CIE_val = \
specifier_instance_from_inst_list (specifier, matchspec, \
domain, *CIE_inst_list, \
- errb, no_quit, depth); \
+ errb, no_quit, depth, \
+ instantiator); \
if (!UNBOUNDP (CIE_val)) \
return CIE_val; \
} \
＠＠ -2544,10 +2552,12 ＠＠ specifier_instance_from_inst_list (Lisp_
as we can determine. In practice, when called from redisplay the
arg will usually be a window and occasionally a frame. If
triggered by a user call, who knows what it will usually be. */
-Lisp_Object
-specifier_instance (Lisp_Object specifier, Lisp_Object matchspec,
- Lisp_Object domain, Error_Behavior errb, int no_quit,
- int no_fallback, Lisp_Object depth)
+
+static Lisp_Object
+specifier_instance_1 (Lisp_Object specifier, Lisp_Object matchspec,
+ Lisp_Object domain, Error_Behavior errb, int no_quit,
+ int no_fallback, Lisp_Object depth,
+ Lisp_Object *instantiator)
{
Lisp_Object buffer = Qnil;
Lisp_Object window = Qnil;
＠＠ -2555,6 +2565,9 ＠＠ specifier_instance (Lisp_Object specifie
Lisp_Object device = Qnil;
Lisp_Specifier *sp = XSPECIFIER (specifier);
+ if (instantiator)
+ *instantiator = Qunbound;
+
/* Attempt to determine buffer, window, frame, and device from the
domain. */
/* #### get image instances out of domains! */
＠＠ -2639,29 +2652,92 ＠＠ specifier_instance (Lisp_Object specifie
assert (CONSP (sp->fallback));
return specifier_instance_from_inst_list (specifier, matchspec, domain,
sp->fallback, errb, no_quit,
- depth);
+ depth, instantiator);
}
#undef CHECK_INSTANCE_ENTRY
Lisp_Object
+specifier_instance (Lisp_Object specifier, Lisp_Object matchspec,
+ Lisp_Object domain, Error_Behavior errb, int no_quit,
+ int no_fallback, Lisp_Object depth)
+{
+ return specifier_instance_1 (specifier, matchspec, domain, errb,
+ no_quit, no_fallback, depth, NULL);
+}
+
+Lisp_Object
specifier_instance_no_quit (Lisp_Object specifier, Lisp_Object matchspec,
Lisp_Object domain, Error_Behavior errb,
int no_fallback, Lisp_Object depth)
+{
+ return specifier_instance_1 (specifier, matchspec, domain, errb,
+ 1, no_fallback, depth, NULL);
+}
+
+static Lisp_Object
+specifier_matching_foo (Lisp_Object specifier,
+ Lisp_Object matchspec,
+ Lisp_Object domain,
+ Lisp_Object default_,
+ Lisp_Object no_fallback,
+ int want_instantiator)
{
- return specifier_instance (specifier, matchspec, domain, errb,
- 1, no_fallback, depth);
+ Lisp_Object instance, instantiator;
+
+ CHECK_SPECIFIER (specifier);
+ if (!UNBOUNDP (matchspec))
+ check_valid_specifier_matchspec (matchspec,
+ XSPECIFIER (specifier)->methods,
+ ERROR_ME);
+ domain = decode_domain (domain);
+
+ instance = specifier_instance_1 (specifier, matchspec, domain, ERROR_ME,
+ 0, !NILP (no_fallback), Qzero,
+ &instantiator);
+ return UNBOUNDP (instance) ? default_ : want_instantiator ? instantiator :
+ instance;
}
DEFUN ("specifier-instance", Fspecifier_instance, 1, 4, 0, /*
Instantiate SPECIFIER (return its value) in DOMAIN.
If no instance can be generated for this domain, return DEFAULT.
-DOMAIN should be a window, frame, or device. Other values that are legal
+DOMAIN is nearly always a window (defaulting to the selected window if
+omitted), but can be a window, frame, or device. Other values that are legal
as a locale (e.g. a buffer) are not valid as a domain because they do not
provide enough information to identify a particular device (see
-`valid-specifier-domain-p'). DOMAIN defaults to the selected window
-if omitted.
+`valid-specifier-domain-p'). Window domains are used internally in nearly
+all circumstances when computing specifier instances of display properties.
+Frame domains are used in a few circumstances (such as when computing the
+geometry of a frame based on properties such as the toolbar widths), and
+device domains are rarely if ever used internally.
+
+This function looks through the specifications in SPECIFIER that correspond
+to DOMAIN, from most specific (specifications for DOMAIN itself) to most
+general (global specifications), for matching instantiators, and attempts
+to compute an instance value for each instantiator found. The first
+successfully computed value is returned. The corresponding instantiator
+can be returned using `specifier-instantiator'.
+
+A specifier is a generalized object for controlling the value of a property --
+typically, but not necessarily, a display-related property -- that can vary
+over particular buffers, frames, device types, etc.
+
+A fundamental distinction must be made between the specification of a
+property's value, and the resulting value itself. This distinction is
+clearest in the case of an image -- the specification describes the source
+of the image (for example, a file of JPEG data), and the resulting value
+encapsulates a window-system object describing the image as displayed on a
+particular device (for example, a particular X display). The specification
+might also be an instruction of the form "use the background pixmap of the
+`modeline' face". A similar mapping exists between color strings and
+color-instance objects, and font strings and font-instance objects. In
+some cases, the specification and the resulting value are of the same type,
+but the distinction is still logically made.
+The specification of a value is called an instantiator, and the resulting
+value the instance.
+
"Instantiating" a specifier in a particular domain means determining
the specifier's "value" in that domain. This is accomplished by
searching through the specifications in the specifier that correspond
＠＠ -2673,7 +2749,7 ＠＠ specifications are searched for as follo
2. A specification whose locale is the window's buffer;
3. A specification whose locale is the window's frame;
4. A specification whose locale is the window's frame's device;
-5. A specification whose locale is 'global.
+5. A specification whose locale is `global'.
If all of those fail, then the C-code-provided fallback value for
this specifier is consulted (see `specifier-fallback'). If it is
＠＠ -2701,20 +2777,32 ＠＠ trying to debug why particular instantia
The returned value is dependent on the type of specifier. For example,
for a font specifier (as returned by the `face-font' function), the returned
value will be a font-instance object. For glyphs, the returned value
-will be a string, pixmap, or subwindow.
+will be an image-instance object.
See also `specifier-matching-instance'.
*/
(specifier, domain, default_, no_fallback))
{
- Lisp_Object instance;
+ return specifier_matching_foo (specifier, Qunbound, domain, default_,
+ no_fallback, 0);
+}
- CHECK_SPECIFIER (specifier);
- domain = decode_domain (domain);
+DEFUN ("specifier-instantiator", Fspecifier_instantiator, 1, 4, 0, /*
+Return instantiator that would be used to instantiate SPECIFIER in DOMAIN.
+If no instance can be generated for this domain, return DEFAULT.
+
+DOMAIN should be a window, frame, or device. Other values that are legal
+as a locale (e.g. a buffer) are not valid as a domain because they do not
+provide enough information to identify a particular device (see
+`valid-specifier-domain-p'). DOMAIN defaults to the selected window
+if omitted.
- instance = specifier_instance (specifier, Qunbound, domain, ERROR_ME, 0,
- !NILP (no_fallback), Qzero);
- return UNBOUNDP (instance) ? default_ : instance;
+See `specifier-instance' for more information about the instantiation process.
+*/
+ (specifier, domain, default_, no_fallback))
+{
+ return specifier_matching_foo (specifier, Qunbound, domain, default_,
+ no_fallback, 1);
}
DEFUN ("specifier-matching-instance", Fspecifier_matching_instance, 2, 5, 0, /*
＠＠ -2745,46 +2833,86 ＠＠ dependent on the particular type of spec
*/
(specifier, matchspec, domain, default_, no_fallback))
{
- Lisp_Object instance;
+ return specifier_matching_foo (specifier, matchspec, domain, default_,
+ no_fallback, 0);
+}
- CHECK_SPECIFIER (specifier);
- check_valid_specifier_matchspec (matchspec, XSPECIFIER (specifier)->methods,
- ERROR_ME);
- domain = decode_domain (domain);
+DEFUN ("specifier-matching-instantiator", Fspecifier_matching_instantiator,
+ 2, 5, 0, /*
+Return instantiator for instance of SPECIFIER in DOMAIN that matches MATCHSPEC.
+If no instance can be generated for this domain, return DEFAULT.
- instance = specifier_instance (specifier, matchspec, domain, ERROR_ME,
- 0, !NILP (no_fallback), Qzero);
- return UNBOUNDP (instance) ? default_ : instance;
+This function is identical to `specifier-matching-instance' but returns
+the instantiator used to generate the instance, rather than the actual
+instance.
+*/
+ (specifier, matchspec, domain, default_, no_fallback))
+{
+ return specifier_matching_foo (specifier, matchspec, domain, default_,
+ no_fallback, 1);
}
-DEFUN ("specifier-instance-from-inst-list", Fspecifier_instance_from_inst_list,
- 3, 4, 0, /*
-Attempt to convert a particular inst-list into an instance.
-This attempts to instantiate INST-LIST in the given DOMAIN,
-as if INST-LIST existed in a specification in SPECIFIER. If
-the instantiation fails, DEFAULT is returned. In most circumstances,
-you should not use this function; use `specifier-instance' instead.
-*/
- (specifier, domain, inst_list, default_))
+static Lisp_Object
+specifier_matching_foo_from_inst_list (Lisp_Object specifier,
+ Lisp_Object matchspec,
+ Lisp_Object domain,
+ Lisp_Object inst_list,
+ Lisp_Object default_,
+ int want_instantiator)
{
Lisp_Object val = Qunbound;
Lisp_Specifier *sp = XSPECIFIER (specifier);
struct gcpro gcpro1;
Lisp_Object built_up_list = Qnil;
+ Lisp_Object instantiator;
CHECK_SPECIFIER (specifier);
+ if (!UNBOUNDP (matchspec))
+ check_valid_specifier_matchspec (matchspec,
+ XSPECIFIER (specifier)->methods,
+ ERROR_ME);
check_valid_domain (domain);
check_valid_inst_list (inst_list, sp->methods, ERROR_ME);
GCPRO1 (built_up_list);
built_up_list = build_up_processed_list (specifier, domain, inst_list);
if (!NILP (built_up_list))
- val = specifier_instance_from_inst_list (specifier, Qunbound, domain,
+ val = specifier_instance_from_inst_list (specifier, matchspec, domain,
built_up_list, ERROR_ME,
- 0, Qzero);
+ 0, Qzero, &instantiator);
UNGCPRO;
- return UNBOUNDP (val) ? default_ : val;
+ return UNBOUNDP (val) ? default_ : want_instantiator ? instantiator : val;
+
+}
+
+DEFUN ("specifier-instance-from-inst-list", Fspecifier_instance_from_inst_list,
+ 3, 4, 0, /*
+Attempt to convert a particular inst-list into an instance.
+This attempts to instantiate INST-LIST in the given DOMAIN,
+as if INST-LIST existed in a specification in SPECIFIER. If
+the instantiation fails, DEFAULT is returned. In most circumstances,
+you should not use this function; use `specifier-instance' instead.
+*/
+ (specifier, domain, inst_list, default_))
+{
+ return specifier_matching_foo_from_inst_list (specifier, Qunbound,
+ domain, inst_list, default_,
+ 0);
}
+DEFUN ("specifier-instantiator-from-inst-list", Fspecifier_instantiator_from_inst_list,
+ 3, 4, 0, /*
+Attempt to convert an inst-list into an instance; return instantiator.
+This is identical to `specifier-instance-from-inst-list' but returns
+the instantiator used to generate the instance, rather than the instance
+itself.
+*/
+ (specifier, domain, inst_list, default_))
+{
+ return specifier_matching_foo_from_inst_list (specifier, Qunbound,
+ domain, inst_list, default_,
+ 1);
+}
+
DEFUN ("specifier-matching-instance-from-inst-list",
Fspecifier_matching_instance_from_inst_list,
4, 5, 0, /*
＠＠ -2800,24 +2928,24 ＠＠ works.
*/
(specifier, matchspec, domain, inst_list, default_))
{
- Lisp_Object val = Qunbound;
- Lisp_Specifier *sp = XSPECIFIER (specifier);
- struct gcpro gcpro1;
- Lisp_Object built_up_list = Qnil;
+ return specifier_matching_foo_from_inst_list (specifier, matchspec,
+ domain, inst_list, default_,
+ 0);
+}
- CHECK_SPECIFIER (specifier);
- check_valid_specifier_matchspec (matchspec, XSPECIFIER (specifier)->methods,
- ERROR_ME);
- check_valid_domain (domain);
- check_valid_inst_list (inst_list, sp->methods, ERROR_ME);
- GCPRO1 (built_up_list);
- built_up_list = build_up_processed_list (specifier, domain, inst_list);
- if (!NILP (built_up_list))
- val = specifier_instance_from_inst_list (specifier, matchspec, domain,
- built_up_list, ERROR_ME,
- 0, Qzero);
- UNGCPRO;
- return UNBOUNDP (val) ? default_ : val;
+DEFUN ("specifier-matching-instantiator-from-inst-list",
+ Fspecifier_matching_instantiator_from_inst_list,
+ 4, 5, 0, /*
+Attempt to convert an inst-list into an instance; return instantiator.
+This is identical to `specifier-matching-instance-from-inst-list' but returns
+the instantiator used to generate the instance, rather than the instance
+itself.
+*/
+ (specifier, matchspec, domain, inst_list, default_))
+{
+ return specifier_matching_foo_from_inst_list (specifier, matchspec,
+ domain, inst_list, default_,
+ 1);
}
＠＠ -3058,10 +3186,10 ＠＠ DEFINE_SPECIFIER_TYPE (generic);
"instance computed from it is likewise any kind of Lisp object. The\n"
"SPECIFIER-DATA should be an alist of methods governing how the specifier\n"
"works. All methods are optional, and reasonable default methods will be\n"
-"provided. Currently there are two defined methods: 'instantiate and\n"
-"'validate.\n"
+"provided. Currently there are two defined methods: `instantiate' and\n"
+"`validate'.\n"
"\n"
-"'instantiate specifies how to do the instantiation; if omitted, the\n"
+"`instantiate' specifies how to do the instantiation; if omitted, the\n"
"instantiator itself is simply returned as the instance. The method\n"
"should be a function that accepts three parameters (a specifier, the\n"
"instantiator that matched the domain being instantiated over, and that\n"
＠＠ -3073,7 +3201,7 ＠＠ DEFINE_SPECIFIER_TYPE (generic);
"the locale corresponding to the passed instantiator could be the window's\n"
"buffer or frame).\n"
"\n"
-"'validate specifies whether a given instantiator is valid; if omitted,\n"
+"`validate' specifies whether a given instantiator is valid; if omitted,\n"
"all instantiators are considered valid. It should be a function of\n"
"two arguments: an instantiator and a flag CAN-SIGNAL-ERROR. If this\n"
"flag is false, the function must simply return t or nil indicating\n"
＠＠ -3271,9 +3399,13 ＠＠ syms_of_specifier (void)
DEFSUBR (Fvalid_specifier_matchspec_p);
DEFSUBR (Fspecifier_fallback);
DEFSUBR (Fspecifier_instance);
+ DEFSUBR (Fspecifier_instantiator);
DEFSUBR (Fspecifier_matching_instance);
+ DEFSUBR (Fspecifier_matching_instantiator);
DEFSUBR (Fspecifier_instance_from_inst_list);
+ DEFSUBR (Fspecifier_instantiator_from_inst_list);
DEFSUBR (Fspecifier_matching_instance_from_inst_list);
+ DEFSUBR (Fspecifier_matching_instantiator_from_inst_list);
DEFSUBR (Fset_specifier_dirty_flag);
DEFSUBR (Fgeneric_specifier_p);
1.10 +39 -39 XEmacs/xemacs/man/lispref/glyphs.texi
Index: glyphs.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/glyphs.texi,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -p -r1.9 -r1.10
--- glyphs.texi 2004/09/22 02:06:27 1.9
+++ glyphs.texi 2005/09/26 08:41:56 1.10
＠＠ -88,25 +88,25 ＠＠ more information about specifier locales
＠section Images
＠menu
-* Image Specifiers:: Specifying an image's appearance.
+* Image Instantiators:: Specifying an image's appearance.
* Image Instantiator Conversion:: Lazy realization of graphics.
* Image Instantiator Formats:: A catalog of image descriptors.
* Image Instances:: Classes of graphical objects.
＠end menu
-＠node Image Specifiers
-＠subsection Image Specifiers
-＠cindex image specifiers
+＠node Image Instantiators
+＠subsection Image Instantiators
+＠cindex image instantiators
- An image specifier is a description of the actual graphical
+ An ＠dfn{image instantiator} is a description of the actual graphical
realization of a glyph. For example, a typical image description is
＠emph{the file system path to a PNG file}. Since redisplay doesn't know
about files, and in any case the image may need to be manipulated
(＠emph{e.g.}, a face's background pixmap must be clipped and tiled), the
PNG file must be converted internally to a window system bitmap or
pixmap object. We describe this process by writing that when XEmacs
-displays the image, it ＠dfn{instantiates} the ＠dfn{image instantiator}
+displays the image, it ＠dfn{instantiates} the image instantiator
into an ＠dfn{image instance}. Image instances are an internal object
type (similar to font instances and color instances), describing how the
image appears in a particular domain. On the other hand, image
＠＠ -114,8 +114,8 ＠＠ instantiators, which are just descriptio
appear, are represented using Lisp strings or vectors.
Furthermore the graphical realization will vary, and for some devices
-may not even be a bitmapped graphic. These variations may be controlled
-by the program by specifying different ＠dfn{image instantiators} in
+may not even be a bitmapped graphic. These variations may be
+controlled by the program by specifying different instantiators in
different locales. This is implemented with an ＠dfn{image specifier},
a specifier whose specifications are image instantiators.
＠＠ -156,9 +156,9 ＠＠ pointers]; etc.)
It is important to keep the distinction between image instantiator
format and image instance type in mind. Typically, a given image
instantiator format can result in many different image instance types.
-For example, ＠code{xpm} can be instanced as ＠code{color-pixmap},
+For example, ＠code{xpm} can be instantiated as ＠code{color-pixmap},
＠code{mono-pixmap}, or ＠code{pointer}; whereas ＠code{cursor-font} can be
-instanced only as ＠code{pointer}. On the other hand, a particular image
+instantiated only as ＠code{pointer}. On the other hand, a particular image
instance type can be generated by many different image instantiator
formats (e.g. ＠code{color-pixmap} can be generated by ＠code{xpm},
＠code{gif}, ＠code{jpeg}, etc.).
＠＠ -372,11 +372,11 ＠＠ are usable with each, and the kinds of i
＠table ＠code
＠item nothing
Don't display anything; no keywords are valid for this format. Can only be
-instanced as ＠code{nothing}.
+instantiated as ＠code{nothing}.
＠item string
-Display this image as a text string. Can only be instanced
-as ＠code{text}, although support for instancing as ＠code{mono-pixmap}
+Display this image as a text string. Can only be instantiated
+as ＠code{text}, although support for instantiation as ＠code{mono-pixmap}
should be added. The valid keyword is ＠code{:data}. The value should
be a string, and it is interpreted as a string of characters.
＠＠ -432,7 +432,7 ＠＠ XBM file.
＠item xpm
An XPM pixmap; only available if XPM support was compiled into this XEmacs.
-Can be instanced as ＠code{color-pixmap}, ＠code{mono-pixmap}, or
+Can be instantiated as ＠code{color-pixmap}, ＠code{mono-pixmap}, or
＠code{pointer}.
XPM is an add-on library for X that was designed to rectify the
＠＠ -476,7 +476,7 ＠＠ used to generate the alist.
An X-Face bitmap, used to encode people's faces in e-mail messages;
only available if X-Face support was compiled into this XEmacs.
-Will be instanced as ＠code{mono-pixmap}, ＠code{color-pixmap}, or
+Will be instantiated as ＠code{mono-pixmap}, ＠code{color-pixmap}, or
＠code{pointer}, depending on the target instance type and the presence
of color keywords.
＠＠ -526,7 +526,7 ＠＠ places'') and linked into the build.
Note that PNG is the standard format for images distributed with XEmacs,
so it is highly recommended that PNG support be built in.
-All of these instantiators will be instanced as ＠code{color-pixmap}.
+All of these instantiators will be instantiated as ＠code{color-pixmap}.
The valid keywords and their values are
＠table ＠code
＠＠ -539,7 +539,7 ＠＠ The name of a file containing standard-f
＠item cursor-font
Most window systems provide a set of standard cursors, which in X11 is
-called a cursor font. Can only be instanced as ＠code{pointer}. This
+called a cursor font. Can only be instantiated as ＠code{pointer}. This
should probably be fixed.
The valid keyword is ＠code{:data}. Its value should be a string
＠＠ -555,14 +555,14 ＠＠ Other window systems may have different
A glyph from a font; i.e. the name of a font, and glyph index into it
of the form ＠samp{＠var{font} fontname index [[mask-font] mask-index]}.
Only if X support was compiled into this XEmacs. Currently can only be
-instanced as ＠code{pointer}. This should probably be fixed.
+instantiated as ＠code{pointer}. This should probably be fixed.
＠c #### The above description is not very helpful, so it's not obvious
＠c how to instantiate a font image.
＠item mswindows-resource
An MS Windows pointer resource. Specifies a resource to retrieve
directly from the system (an OEM resource) or from a file, particularly
-an executable file. Can be instanced as ＠code{pointer} or
+an executable file. Can be instantiated as ＠code{pointer} or
＠code{color-pixmap}.
The valid keywords and their values are
＠＠ -601,23 +601,23 ＠＠ For icons:
＠end table
＠item subwindow
-An embedded windowing system window. Can only be instanced as
+An embedded windowing system window. Can only be instantiated as
＠code{subwindow}. Not implemented.
＠c #### Check status of subwindows ... I thought Andy implemented them.
＠item button
A button widget; either a push button, radio button or toggle button.
-Can only be instanced as ＠code{widget}.
+Can only be instantiated as ＠code{widget}.
＠item combo-box
A drop list of selectable items in a widget, for editing text.
-Can only be instanced as ＠code{widget}.
+Can only be instantiated as ＠code{widget}.
＠item edit-field
-A text editing widget. Can only be instanced as ＠code{widget}.
+A text editing widget. Can only be instantiated as ＠code{widget}.
＠item label
-A static, text-only, widget; for displaying text. Can only be instanced
+A static, text-only, widget; for displaying text. Can only be instantiated
as ＠code{widget}.
＠item layout
＠＠ -625,19 +625,19 ＠＠ A widget for controlling the positioning
Through the use of nested layouts, a widget hierarchy can be created
which can have the appearance of any standard dialog box or similar
arrangement; all of this is counted as one ＠dfn{glyph} and could appear
-in many of the places that expect a single glyph. Can only be instanced
+in many of the places that expect a single glyph. Can only be instantiated
as ＠code{widget}.
＠item native-layout
The native version of a layout widget.
-Can only be instanced as ＠code{widget}.
+Can only be instantiated as ＠code{widget}.
＠item progress-gauge
-A sliding widget, for showing progress. Can only be instanced as
+A sliding widget, for showing progress. Can only be instantiated as
＠code{widget}.
＠item tab-control
-A tab widget; a series of user selectable tabs. Can only be instanced
+A tab widget; a series of user selectable tabs. Can only be instantiated
as ＠code{widget}.
The required keyword is ＠code{:items}. Its value should be a list of
＠＠ -654,10 +654,10 ＠＠ and ＠code{:pixel-height} (positive integ
(The above is incomplete and may be inaccurate.)
＠item tree-view
-A folding widget. Can only be instanced as ＠code{widget}.
+A folding widget. Can only be instantiated as ＠code{widget}.
＠item scrollbar
-A scrollbar widget. Can only be instanced as ＠code{widget}.
+A scrollbar widget. Can only be instantiated as ＠code{widget}.
＠item autodetect
XEmacs tries to guess what format the data is in. If X support exists,
＠＠ -672,7 +672,7 ＠＠ the image will always be displayed as te
＠item inherit
Inherit from the background-pixmap property of a face. Can only be
-instanced as ＠code{mono-pixmap}.
+instantiated as ＠code{mono-pixmap}.
＠end table
There are two convenience variables for use with the XBM and XPM image
＠＠ -719,7 +719,7 ＠＠ This function returns non-＠code{nil} if
＠end defun
＠menu
-* Image Instance Types:: Each image instances has a particular type.
+* Image Instance Types:: Each image instance has a particular type.
* Image Instance Functions:: Functions for working with image instances.
＠end menu
＠＠ -834,7 +834,7 ＠＠ Return non-＠code{nil} if ＠var{object} is
This function creates a new image-instance object.
＠var{data} is an image instantiator, which describes the image
-(＠pxref{Image Specifiers}).
+(＠pxref{Image Instantiators}).
＠var{dest-types} should be a list of allowed image instance types that
can be generated. The ＠var{dest-types} list is unordered. If multiple
＠＠ -991,7 +991,7 ＠＠ if known.
＠end defun
Mono pixmaps and pointers may have their foreground and background
-colors set when instanced. Use these functions to access color
+colors set when instantiated. Use these functions to access color
information.
＠defun image-instance-foreground image-instance
＠＠ -1104,7 +1104,7 ＠＠ vector. The vector's first element spec
of the data, such as a string, a PNG file, or an MS Windows resource.
This is followed by properties (keyword-value pairs) specifying such
information as the name of a file containing an image, or pixmap data
-directly. ＠xref{Image Specifiers}.
+directly. ＠xref{Image Instantiators}.
The optional ＠var{type} specifies the type of the glyph. ＠var{type}
should be one of ＠code{buffer} (used for glyphs in an extent, the
＠＠ -1488,7 +1488,7 ＠＠ search dialog is formatted using layouts
Native widgets are manipulated as ＠emph{glyphs} (＠pxref{Glyphs}). Thus
they are created using ＠code{make-glyph}, with a format of one of the
widget types and a ＠code{:data} property specific to the widget being
-instanced.
+instantiated.
However, there is a technical difference between widgets and other kinds
of glyphs that is theoretically important. Because widgets
＠＠ -1838,7 +1838,7 ＠＠ specification.
If ＠var{property} does not name a built-in property, its value will
simply be returned unless it is a specifier object, in which case it
-will be instanced using ＠code{specifier-instance}.
+will be instantiated using ＠code{specifier-instance}.
Optional arguments ＠var{default} and ＠var{no-fallback} are the same as
in ＠code{specifier-instance}. ＠xref{Specifiers}.
＠＠ -2065,7 +2065,7 ＠＠ The parameters passed to ＠code{make-glyp
Specifiers", and can handle more image types than those shown above.
You can also put the raw image data into a string (e.g., if you put the
contents of a JPEG file into a string), and use that to create a glyph.
-＠xref{Image Specifiers}, for more information.
+＠xref{Image Instantiators}, for more information.
＠quotation
＠strong{Caution}: In order for XEmacs to read a particular graphics file
＠＠ -2079,7 +2079,7 ＠＠ To programmatically query whether or not
supported, you can use the ＠code{featurep} function, with one of:
＠code{gif}, ＠code{tiff}, ＠code{jpeg}, ＠code{xpm}, ＠code{xbm},
＠code{png}, or ＠code{xface}. For an up-to-date list, ＠ref{Image
-Specifiers}. Example:
+Instantiators}. Example:
＠example
;; Returns `t' if TIFF is supported:
1.23 +9 -17 XEmacs/xemacs/man/lispref/lispref.texi
Index: lispref.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/lispref.texi,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -p -r1.22 -r1.23
--- lispref.texi 2005/06/19 20:49:47 1.22
+++ lispref.texi 2005/09/26 08:41:56 1.23
＠＠ -941,15 +941,15 ＠＠ Specifiers
(under user control) in a wide variety
of contexts.
* Specifiers In-Depth:: Gory details about specifier innards.
-* Specifier Instancing:: Instancing means obtaining the ``value'' of
+* Specifier Instantiation:: Instantiation means obtaining the ``value'' of
a specifier in a particular context.
* Specifier Types:: Specifiers come in different flavors.
* Adding Specifications:: Specifications control a specifier's ``value''
by giving conditions under which a
particular value is valid.
* Retrieving Specifications:: Querying a specifier's specifications.
-* Specifier Instancing Functions::
- Functions to instance a specifier.
+* Specifier Instantiation Functions::
+ Functions to instantiate a specifier.
* Specifier Examples:: Making all this stuff clearer.
* Creating Specifiers:: Creating specifiers for your own use.
* Specifier Validation Functions::
＠＠ -977,21 +977,21 ＠＠ Faces
Fonts
* Font Specifiers:: Specifying how a font will appear.
-* Font Instances:: What a font specifier gets instanced as.
+* Font Instances:: What a font specifier gets instantiated as.
* Font Instance Names:: The name of a font instance.
* Font Instance Size:: The size of a font instance.
* Font Instance Characteristics:: Display characteristics of font instances.
* Font Convenience Functions:: Convenience functions that automatically
- instance and retrieve the properties
+ instantiate and retrieve the properties
of a font specifier.
Colors
* Color Specifiers:: Specifying how a color will appear.
-* Color Instances:: What a color specifier gets instanced as.
+* Color Instances:: What a color specifier gets instantiated as.
* Color Instance Properties:: Properties of color instances.
* Color Convenience Functions:: Convenience functions that automatically
- instance and retrieve the properties
+ instantiate and retrieve the properties
of a color specifier.
Glyphs
＠＠ -1004,22 +1004,14 ＠＠ Glyphs
Images
-* Image Specifiers:: Specifying an image's appearance.
+* Image Instantiators:: Specifying an image's appearance.
* Image Instantiator Conversion:: Lazy realization of graphics.
* Image Instantiator Formats:: A catalog of image descriptors.
* Image Instances:: Classes of graphical objects.
Image Instances
-* Image Instance Types:: Each image instances has a particular type.
-* Image Instance Functions:: Functions for working with image instances.
-
-Using Glyphs
-
-
-Image Instances
-
-* Image Instance Types:: Each image instances has a particular type.
+* Image Instance Types:: Each image instance has a particular type.
* Image Instance Functions:: Functions for working with image instances.
Using Glyphs
1.15 +54 -54 XEmacs/xemacs/man/lispref/specifiers.texi
Index: specifiers.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/specifiers.texi,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -p -r1.14 -r1.15
--- specifiers.texi 2004/06/18 07:18:40 1.14
+++ specifiers.texi 2005/09/26 08:41:57 1.15
＠＠ -14,7 +14,7 ＠＠ device. The value of many built-in prop
foreground, background, and such properties of a face and variables
such as ＠code{modeline-shadow-thickness} and
＠code{top-toolbar-height}, is actually a specifier object. The
-specifier object, in turn, is ``instanced'' in a particular situation
+specifier object, in turn, is ``instantiated'' in a particular situation
to yield the real value of the property in the current context.
＠defun specifierp object
＠＠ -28,7 +28,7 ＠＠ This function returns non-＠code{nil} if
of contexts.
* Simple Specifier Usage:: Getting started with specifiers.
* Specifiers In-Depth:: Gory details about specifier innards.
-* Specifier Instancing:: Instancing means obtaining the ``value'' of
+* Specifier Instantiation:: Instantiation means obtaining the ``value'' of
a specifier in a particular context.
* Specifier Types:: Specifiers come in different flavors.
* Adding Specifications:: Specifications control a specifier's ``value''
＠＠ -36,8 +36,8 ＠＠ This function returns non-＠code{nil} if
particular value is valid.
* Retrieving Specifications:: Querying a specifier's specifications.
* Specifier Tag Functions:: Working with specifier tags.
-* Specifier Instancing Functions::
- Functions to instance a specifier.
+* Specifier Instantiation Functions::
+ Functions to instantiate a specifier.
* Specifier Examples:: Making all this stuff clearer.
* Creating Specifiers:: Creating specifiers for your own use.
* Specifier Validation Functions::
＠＠ -89,12 +89,12 ＠＠ is available. The complex calculations
transparent to both user and programmer. You ask for what you want;
it's up to XEmacs to provide it, or a reasonable approximation.
-We call such a declaration a ＠dfn{specification}. A ＠dfn{specification}
-applies in a particular ＠dfn{locale}, which is a window, buffer, frame,
-device, or the global locale. The value part of the specification is
-called an ＠dfn{instantiator}. The process of determining the value in a
-particular context, or ＠dfn{domain}, is called ＠dfn{instantiation} or
-＠dfn{instancing}. A domain is a window, frame, or device.
+We call such a declaration a ＠dfn{specification}. A
+＠dfn{specification} applies in a particular ＠dfn{locale}, which is a
+window, buffer, frame, device, or the global locale. The value part
+of the specification is called an ＠dfn{instantiator}. The process of
+determining the value in a particular context, or ＠dfn{domain}, is
+called ＠dfn{instantiation}. A domain is a window, frame, or device.
The difference between ＠dfn{locale} and ＠dfn{domain} is somewhat subtle.
You may think of a locale as a class of domains, which may span
＠＠ -199,8 +199,8 ＠＠ a program manipulates specifications, cl
desirable.
In the case of the toolbar descriptor, it turns out that these are the
-same: the instancing process is trivial. However, many specifications
-have non-trivial instancing. Compare the results of the following forms
+same: the instantiation process is trivial. However, many specifications
+have non-trivial instantiation. Compare the results of the following forms
on my system. (The ＠samp{(cdr (first ...))} form is due to my use of
Mule. On non-Mule XEmacsen, just use ＠code{specifier-specs}.)
＠＠ -216,16 +216,16 ＠＠ In this case, ＠code{specifier-instance}
programs can't work on it, they can only pass it around. Worse, in some
environments the instantiation will fail, resulting in a different value
(when another instantiation succeeds), or worse yet, an error, if all
-attempts to instance the specifier fail. ＠code{specifier-instance} is
+attempts to instantiate the specifier fail. ＠code{specifier-instance} is
context-dependent, even for the exact same specification.
＠code{specifier-specs} is deterministic, and only depends on the
specifications.
Note that in the toolbar-changing code we operate in the global locale.
This means that narrower locales, if they have specifications, will
-shadow our changes. (Specifier instancing does not merge
+shadow our changes. (Specifier instantiation does not merge
specifications. It selects the "highest-priority successful
-specification" and instances that.)
+specification" and instantiates that.)
In fact, in our example, it seems pretty likely that different buffers
＠emph{should} have different buttons. (The icon can be the same, but
＠＠ -283,7 +283,7 ＠＠ Specifications}, for documentation of ＠c
＠cindex domain (in a specifier)
＠cindex locale (in a specifier)
＠cindex instantiator (in a specifier)
-＠cindex instancing (in a specifier)
+＠cindex instantiation (in a specifier)
＠cindex instance (in a specifier)
＠cindex inst-list (in a specifier)
＠cindex inst-pair (in a specifier)
＠＠ -293,7 +293,7 ＠＠ Specifications}, for documentation of ＠c
＠cindex specifier, domain
＠cindex specifier, locale
＠cindex specifier, instantiator
-＠cindex specifier, instancing
+＠cindex specifier, instantiation
＠cindex specifier, instance
＠cindex specifier, inst-list
＠cindex specifier, inst-pair
＠＠ -335,11 +335,11 ＠＠ particular situation?'' This involves lo
to see which ones apply to this particular situation, and perhaps
preferring one over another if more than one applies. In specifier
terminology, a ``particular situation'' is called a ＠dfn{domain}, and
-determining its value in a particular domain is called ＠dfn{instancing}.
+determining its value in a particular domain is called ＠dfn{instantiation}.
Most of the time, a domain is identified by a particular window. For
example, if the redisplay engine is drawing text in the default face in
a particular window, it retrieves the specifier for the foreground color
-of the default face and ＠dfn{instances} it in the domain given by that
+of the default face and ＠dfn{instantiates} it in the domain given by that
window; in other words, it asks the specifier, ``What is your value in
this window?''.
＠＠ -372,28 +372,28 ＠＠ All tags in a tag set must match a devic
to be instantiable over that device. (A null tag set is perfectly
valid, and trivially matches all devices.)
-＠c #### don't we have more device types now, gtk, ms-windows, mac-carbon?
-The valid device types (normally ＠code{x}, ＠code{tty}, and
-＠code{stream}) and device classes (normally ＠code{color},
-＠code{grayscale}, and ＠code{mono}) can always be used as tags, and match
-devices of the associated type or class (＠pxref{Consoles and Devices}).
-User-defined tags may be defined, with an optional predicate specified.
-An application can create its own tag, use it to mark all its
+The valid device types (normally ＠code{x}, ＠code{tty}, ＠code{stream},
+＠code{mswindows}, ＠code{msprinter}, and possibly ＠code{carbon}) and
+device classes (normally ＠code{color}, ＠code{grayscale}, and
+＠code{mono}) can always be used as tags, and match devices of the
+associated type or class (＠pxref{Consoles and Devices}). User-defined
+tags may be defined, with an optional predicate specified. An
+application can create its own tag, use it to mark all its
instantiators, and be fairly confident that it will not interfere with
other applications that modify the same specifier---Functions that add
a specification to a specifier usually only overwrite existing
inst-pairs with the same tag set as was given, and a particular tag or
tag set can be specified when removing instantiators.
-When a specifier is instanced in a domain, both the locale and the tag
+When a specifier is instantiated in a domain, both the locale and the tag
set can be viewed as specifying necessary conditions that must apply in
that domain for an instantiator to be considered as a possible result of
-the instancing. More specific locales always override more general
+the instantiation. More specific locales always override more general
locales (thus, there is no particular ordering of the specifications in
a specifier); however, the tag sets are simply considered in the order
that the inst-pairs occur in the specification's inst-list.
-Note also that the actual object that results from the instancing
+Note also that the actual object that results from the instantiation
(called an ＠dfn{instance object}) may not be the same as the instantiator
from which it was derived. For some specifier types (such as integer
specifiers and boolean specifiers), the instantiator will be returned
＠＠ -410,12 +410,12 ＠＠ device, etc. Furthermore, this conversi
might fail---a font or color might not exist on a particular device,
for example.
-＠node Specifier Instancing
-＠section How a Specifier Is Instanced
+＠node Specifier Instantiation
+＠section How a Specifier Is Instantiated
＠cindex fallback (in a specifier)
＠cindex specifier, fallback
-Instancing of a specifier in a particular window domain proceeds as
+Instantiation of a specifier in a particular window domain proceeds as
follows:
＠itemize ＠bullet
＠＠ -437,7 +437,7 ＠＠ match the device.)
If a matching tag set is found, the corresponding instantiator is passed
to the specifier's instantiation method, which is specific to the type
of the specifier. If it succeeds, the resulting instance object is
-returned as the result of the instancing and the instancing is done.
+returned as the result of the instantiation and the instantiation is done.
Otherwise, the operation continues, looking for another matching
inst-pair in the current specification.
＠item
＠＠ -446,36 +446,36 ＠＠ specification, the search starts over, l
as in the first step above.
＠item
If all specifications are exhausted and no instance object can be
-derived, the instancing fails. (Actually, this is not completely true.
+derived, the instantiation fails. (Actually, this is not completely true.
Some specifier objects for built-in properties have a ＠dfn{fallback}
value, which is either an inst-list or another specifier object, that is
-consulted if the instancing is about to fail. If it is an inst-list,
+consulted if the instantiation is about to fail. If it is an inst-list,
the searching proceeds using the inst-pairs in that list. If it is a
-specifier, the entire instancing starts over using that specifier
+specifier, the entire instantiation starts over using that specifier
instead of the given one. Fallback values are set by the C code and
cannot be modified, except perhaps indirectly, using any Lisp functions.
The purpose of them is to supply some values to make sure that
-instancing of built-in properties can't fail and to implement some basic
+instantiation of built-in properties can't fail and to implement some basic
specifier inheritance, such as the fact that faces inherit their
properties from the ＠code{default} face.)
＠end itemize
-It is also possible to instance a specifier over a frame domain or
+It is also possible to instantiate a specifier over a frame domain or
device domain instead of over a window domain. The C code, for example,
-instances the ＠code{top-toolbar-height} variable over a frame domain in
-order to determine the height of a frame's top toolbar. Instancing over
-a frame or device is similar to instancing over a window except that
+instantiates the ＠code{top-toolbar-height} variable over a frame domain in
+order to determine the height of a frame's top toolbar. Instantiation over
+a frame or device is similar to instantiation over a window except that
specifications for locales that cannot be derived from the domain are
-ignored. Specifically, instancing over a frame looks first for frame
-locales, then device locales, then the ＠code{global} locale. Instancing
+ignored. Specifically, instantiation over a frame looks first for frame
+locales, then device locales, then the ＠code{global} locale. Instantiation
over a device domain looks only for device locales and the ＠code{global}
locale.
-Note that specifiers are instanced on ＠emph{every} redisplay. (This is
+Note that specifiers are instantiated on ＠emph{every} redisplay. (This is
the concept; of course the implementation keeps track of changes and
-doesn't reinstance unchanged specifiers.) That means that changes in
+doesn't reinstantiate unchanged specifiers.) That means that changes in
specifiers controlling appearance are reflected immediately in the UI.
-Also, since specifiers are instanced completely, removing a
+Also, since specifiers are instantiated completely, removing a
specification can be just as effective as adding one.
＠emph{E.g.}, Giacomo Boffi wanted a modeline that indicates whether the
＠＠ -1109,7 +1109,7 ＠＠ no instantiators at all.
＠defun specifier-fallback specifier
This function returns the fallback value for ＠var{specifier}. Fallback
values are provided by the C code for certain built-in specifiers to
-make sure that instancing won't fail even if all specs are removed from
+make sure that instantiation won't fail even if all specs are removed from
the specifier, or to implement simple inheritance behavior (e.g. this
method is used to ensure that faces other than ＠code{default} inherit
their attributes from ＠code{default}). By design, you cannot change the
＠＠ -1117,11 +1117,11 ＠＠ fallback value, and specifiers created w
never have a fallback (although a similar, Lisp-accessible capability
may be provided in the future to allow for inheritance).
-The fallback value will be an inst-list that is instanced like
+The fallback value will be an inst-list that is instantiated like
any other inst-list, a specifier of the same type as ＠var{specifier}
(results in inheritance), or ＠code{nil} for no fallback.
-When you instance a specifier, you can explicitly request that the
+When you instantiate a specifier, you can explicitly request that the
fallback not be consulted. (The C code does this, for example, when
merging faces.) See ＠code{specifier-instance}.
＠end defun
＠＠ -1145,8 +1145,8 ＠＠ Each tag has a predicate associated with
that tag applies to a particular device. The tags which are device
types and classes match devices of that type or class. User-defined
tags can have any predicate, or none (meaning that all devices match).
-When attempting to instance a specifier, a particular instantiator is
-only considered if the device of the domain being instanced over matches
+When attempting to instantiate a specifier, a particular instantiator is
+only considered if the device of the domain being instantiated over matches
all tags in the tag set attached to that instantiator.
Most of the time, a tag set is not specified, and the instantiator gets
＠＠ -1201,8 +1201,8 ＠＠ This includes the built-in ones (the dev
This function returns the predicate for the given specifier tag.
＠end defun
-＠node Specifier Instancing Functions
-＠section Functions for Instancing a Specifier
+＠node Specifier Instantiation Functions
+＠section Functions for Instantiating a Specifier
＠defun specifier-instance specifier &optional domain default no-fallback
This function instantiates ＠var{specifier} (returns its value) in
＠＠ -1605,7 +1605,7 ＠＠ Display Table}).
＠defun valid-specifier-domain-p domain
This function returns non-＠code{nil} if ＠var{domain} is a valid
-specifier domain. A domain is used to instance a specifier
+specifier domain. A domain is used to instantiate a specifier
(i.e. determine the specifier's value in that domain). Valid domains
are a window, frame, or device. (＠code{nil} is not valid.)
＠end defun
- 1 participants
- 0 comments
CVS update by ben xemacs/src ...
18 years, 7 months
CVS Monitor
CVS Monitor
User: ben
Date: 05/09/26 10:29:35
Modified: xemacs/src ChangeLog rangetab.c
Log:
fix range table boundaries
rangetab.c: Fix bug in handling of range endpoints when not start-closed, end-open.
Revision Changes Path
1.858 +6 -0 XEmacs/xemacs/src/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v
retrieving revision 1.857
retrieving revision 1.858
diff -u -p -r1.857 -r1.858
--- ChangeLog 2005/09/24 16:31:37 1.857
+++ ChangeLog 2005/09/26 08:29:27 1.858
＠＠ -1,3 +1,9 ＠＠
+2005-09-26 Ben Wing <ben(a)xemacs.org>
+
+ * rangetab.c:
+ * rangetab.c (Fmap_range_table):
+ Fix bug in handling of range endpoints when not start-closed, end-open.
+
2005-09-17 Olivier Galibert <galibert(a)xemacs.org>
* intl.c (Fset_current_locale): setlocale return string is valid
1.24 +15 -3 XEmacs/xemacs/src/rangetab.c
Index: rangetab.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/rangetab.c,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -p -r1.23 -r1.24
--- rangetab.c 2005/04/08 23:11:31 1.23
+++ rangetab.c 2005/09/26 08:29:31 1.24
＠＠ -1,6 +1,6 ＠＠
/* XEmacs routines to deal with range tables.
Copyright (C) 1995 Sun Microsystems, Inc.
- Copyright (C) 1995, 2002, 2004 Ben Wing.
+ Copyright (C) 1995, 2002, 2004, 2005 Ben Wing.
This file is part of XEmacs.
＠＠ -606,8 +606,20 ＠＠ exactly once) if FUNCTION modifies or de
last = entry->last;
oldlen = Dynarr_length (rt->entries);
args[0] = function;
- args[1] = make_int (first);
- args[2] = make_int (last);
+ /* Fix up the numbers in accordance with the open/closedness of the
+ table. */
+ {
+ EMACS_INT premier = first, dernier = last;
+ switch (rt->type)
+ {
+ case RANGE_START_CLOSED_END_OPEN: break;
+ case RANGE_START_CLOSED_END_CLOSED: dernier--; break;
+ case RANGE_START_OPEN_END_OPEN: premier--; break;
+ case RANGE_START_OPEN_END_CLOSED: premier--, dernier--; break;
+ }
+ args[1] = make_int (premier);
+ args[2] = make_int (dernier);
+ }
args[3] = entry->val;
Ffuncall (countof (args), args);
/* Has FUNCTION removed the entry? */
- 1 participants
- 0 comments
CVS update by ben xemacsweb/Download make-zip-lib
18 years, 7 months
CVS Monitor
CVS Monitor
User: ben
Date: 05/09/26 10:25:54
Added: xemacsweb/Download make-zip-lib
Log:
New script make-zip-lib for creating optional-libs directories
Revision Changes Path
1.1 XEmacs/xemacsweb/Download/make-zip-lib
Index: make-zip-lib
===================================================================
#!/bin/sh
# Make a directory containing the pre-built auxiliary library files.
# Source and destination directories
srcdir=/src
destdir=/src/zipped
# Versions of the various libraries to be copied
compface=compface-1.5.1
db=db-4.3.28
gmp=gmp-4.1.2
jpeg=jpeg-6b
libpng=libpng-1.2.8
postgresql=postgresql-8.0.3
tiff=tiff-3.7.3
xpm=xpm-3.4k
zlib=zlib-1.2.3
# Files to be copied
# Do it.
mkdir -p $destdir
mkdir -p $destdir/$compface
cd $srcdir/$compface
cp compface.h *.exe *.lib *.dll $destdir/$compface
mkdir -p $destdir/$db/build_win32/Release
mkdir -p $destdir/$db/build_win32/Release_static
cd $srcdir/$db/build_win32
cp *.h $destdir/$db/build_win32
cd Release
cp *.dll *.lib *.exe $destdir/$db/build_win32/Release
cd ../Release_static
# Don't copy static .exe's; they're just way too big
cp *.lib $destdir/$db/build_win32/Release_static
mkdir -p $destdir/$gmp/gmp-dynamic
mkdir -p $destdir/$gmp/gmp-static
cd $srcdir/$gmp
cd gmp-dynamic
cp *.h *.dll *.lib $destdir/$gmp/gmp-dynamic
cd ../gmp-static
cp *.h *.lib $destdir/$gmp/gmp-static
mkdir -p $destdir/$jpeg
cd $srcdir/$jpeg
cp *.h *.exe *.lib $destdir/$jpeg
mkdir -p $destdir/$libpng
cd $srcdir/$libpng
cp *.h *.lib $destdir/$libpng
mkdir -p $destdir/$postgresql/src/interfaces/libpq/Release
cd $srcdir/$postgresql/src
cp -a include $destdir/$postgresql/src
cd interfaces/libpq
cp *.h $destdir/$postgresql/src/interfaces/libpq
cd Release
cp *.dll *.lib $destdir/$postgresql/src/interfaces/libpq/Release
mkdir -p $destdir/$tiff/libtiff
cd $srcdir/$tiff/libtiff
cp tiff.h tiffio.h tiffvers.h *.dll *.lib $destdir/$tiff/libtiff
mkdir -p $destdir/$xpm/X11
mkdir -p $destdir/$xpm/lib
cd $srcdir/$xpm/X11
cp *.h $destdir/$xpm/X11
cd ../lib
cp xpm.h XpmI.h simx.h *.lib *.dll $destdir/$xpm/lib
mkdir -p $destdir/$zlib
cd $srcdir/$zlib
cp *.h *.dll *.lib $destdir/$zlib
- 1 participants
- 0 comments
CVS update by ben xemacsweb/Download/win32 ...
18 years, 7 months
CVS Monitor
CVS Monitor
User: ben
Date: 05/09/26 10:25:08
Modified: xemacsweb/Download/win32 optional-libs.exe
Log:
Update optional libraries
Revision Changes Path
1.3 +9906 -7671XEmacs/xemacsweb/Download/win32/optional-libs.exe
<<Binary file>>
- 1 participants
- 0 comments
CVS update by ben xemacs/nt, xemacs.mak ...
18 years, 7 months
CVS Monitor
CVS Monitor
User: ben
Date: 05/09/26 10:13:03
Modified: xemacs/nt ChangeLog README config.inc.samp minitar.c
xemacs.mak
Log:
Compile Windows with gmp, ldap, postgresql, db, etc.
README: Major rewrite. Document how to compile various optional libs.
config.inc.samp: Update to recent versions of optional libs. Add support for
gmp, db, postgresql, ldap. Turn on optimization when not debug.
minitar.c: Include config.h.
xemacs.mak: Figure out VC++ version and use it to set debug and browser flags
appropriately.
Add support for building gmp, db, postgresql, ldap.
Rewrite handling of optional stuff so it is all added to single
variables OPT_* rather than to various FOO_* variables.
Pass -I$(SRC) to minitar.c so it compiles.
Pass module sources, not objects, to make-docfile.
Delete more stuff in `make clean'.
Revision Changes Path
1.190 +37 -0 XEmacs/xemacs/nt/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/nt/ChangeLog,v
retrieving revision 1.189
retrieving revision 1.190
diff -u -p -r1.189 -r1.190
--- ChangeLog 2005/09/25 19:13:43 1.189
+++ ChangeLog 2005/09/26 08:13:00 1.190
＠＠ -1,3 +1,40 ＠＠
+2005-09-26 Ben Wing <ben(a)xemacs.org>
+
+ * README:
+ Major rewrite. Document how to compile various optional libs.
+
+ * config.inc.samp:
+ Update to recent versions of optional libs. Add support for
+ gmp, db, postgresql, ldap. Turn on optimization when not debug.
+
+ * minitar.c:
+ Include config.h.
+
+ * xemacs.mak:
+ * xemacs.mak (HAVE_WIDGETS):
+ * xemacs.mak (OPT_DEFINES):
+ * xemacs.mak (OPT_OBJS):
+ * xemacs.mak (BROWSERFLAGS):
+ * xemacs.mak (INCLUDES):
+ * xemacs.mak (DEFINES):
+ * xemacs.mak (TEMACS_COMMON_OBJS):
+ * xemacs.mak (TEMACS_OBJS):
+ * xemacs.mak ($(OUTDIR)\postgresql.obj):
+ * xemacs.mak ($(BLDLIB_SRC)/minitar.exe):
+ * xemacs.mak ( NOTE):
+ * xemacs.mak (TEMACS_LIBS):
+ * xemacs.mak ($(RAW_EXE)):
+ * xemacs.mak (mostlyclean):
+ * xemacs.mak (versionclean):
+ Figure out VC++ version and use it to set debug and browser flags
+ appropriately.
+ Add support for building gmp, db, postgresql, ldap.
+ Rewrite handling of optional stuff so it is all added to single
+ variables OPT_* rather than to various FOO_* variables.
+ Pass -I$(SRC) to minitar.c so it compiles.
+ Pass module sources, not objects, to make-docfile.
+ Delete more stuff in `make clean'.
+
2005-09-25 Adrian Aichner <adrian(a)xemacs.org>
* xemacs.mak: Fix variable initialization order.
1.27 +172 -71 XEmacs/xemacs/nt/README
Index: README
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/nt/README,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -p -r1.26 -r1.27
--- README 2003/11/06 15:12:33 1.26
+++ README 2005/09/26 08:13:00 1.27
＠＠ -1,18 +1,21 ＠＠
Building and Installing XEmacs on Windows 95/98/NT/2000/XP -*- mode:outline -*-
+ Ben Wing
+
+ based on old version by
+
David Hobley
Marc Paquette
Jonathan Harris
- Ben Wing
-This is a port of XEmacs to Windows 95/98/NT/2000/XP. If you are looking for a
-port of GNU Emacs, get the latest release of the 21.x series from gnu.org.
-(At the time of writing, GNU Emacs does not support images but does support
-Mule.) NT 4.0 or later is required for building on Windows NT. Note that the
-developers typically use NT 4.0 and Windows 2000, and there may possibly be
-problems under Windows 95/98. If so, please report them to
-xemacs-nt(a)xemacs.org; we are committed to maintaining compatibility with all
-systems listed.
+This is a port of XEmacs to Windows 95/98/ME/NT/2000/XP. If you are
+looking for a port of GNU Emacs, get the latest release of the 21.x series
+from gnu.org. NT 4.0 or later is required for building on Windows NT.
+Note that the developers typically use NT 4.0 and Windows 2000 or XP, and
+there may possibly be problems under Windows 95/98. (One developer has
+successfully built on Windows ME, though, which is the successor of Windows
+98.) If so, please report them to xemacs-nt(a)xemacs.org; we are committed
+to maintaining compatibility with all systems listed.
* Required tools and sources
============================
＠＠ -38,7 +41,7 ＠＠ systems listed.
2. Grab the latest XEmacs source from
- ftp://ftp.xemacs.org/pub/xemacs/
+ http://ftp.xemacs.org/pub/xemacs/
or one of its mirrors listed at http://www.xemacs.org/Download/index.html.
＠＠ -48,16 +51,16 ＠＠ systems listed.
You'll also need the packages. You probably want to get the unified
packages bundle from
- ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo.tar.gz
+ http://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo.tar.gz
If you are building with international support, you also need
- ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-mule-sumo.tar.gz
+ http://ftp.xemacs.org/pub/xemacs/packages/xemacs-mule-sumo.tar.gz
Although we don't recommend it, you can also retrieve just the packages
you really need if you have an extremely slow net connection or are very
short on disk space. You can find the various packages in
- ftp://ftp.xemacs.org/pub/xemacs/packages/. You will need the xemacs-base
+ http://ftp.xemacs.org/pub/xemacs/packages/. You will need the xemacs-base
package (and mule-base, if building with international support). You'll
also need the texinfo package unless you have a copy of makeinfo.exe on
your machine. If you want to download additional or updated packages
＠＠ -75,40 +78,119 ＠＠ systems listed.
* Optional libraries
====================
+
+The easiest way to get the optional libraries is to grab the appropriate
+set of precompiled versions for your compiler:
+
+http://www.xemacs.org/Download/win32/optional-libs.exe
+
+or for VC++ 2005 (VC8)
+
+http://www.xemacs.org/Download/win32/optional-libs-vc8.exe
+
+unpack them somewhere and set the OPTIONAL_LIBRARY_DIR in config.inc
+to point to where you put them. This will automatically give you
+all the graphics libraries. (NOTE: optional-libs.exe was compiled with
+VC++ .NET and may or may not work with VC++ 6.0. If not, you will have
+to build them yourself until we provide VC6 binaries.)
+
+* Alternative: Building the optional libraries yourself
+=======================================================
+
+If you need to build the libraries yourself, grab them from
+http://ftp.xemacs.org/pub/xemacs/aux or get the latest version from the
+home page of the appropriate library, as listed on
+http://www.xemacs.org/Download/optLibs.html. The following instructions
+assume that you have the appropriate libraries and have unpacked them
+somewhere, e.g. c:\src.
+
+Directions for building the various libraries:
+
+1. You really want the XPM library. Copy nt\xpm.mak from the xemacs sources
+ to the lib/ subdirectory of the XPM sources, cd to that directory and
+ build xpm with 'nmake -f xpm.mak'.
+
+2. You probably also want PNG image support. Get PNG and ZLIB and read the
+ respective READMEs for details on how to build them.
+
+ cd to the ZLIB source directory and type 'nmake -f win32\Makefile.msc'.
+
+ cd to the libpng source directory, rename or move the zlib directory to
+ ..\zlib and type 'nmake -f scripts\makefile.vcawin32'.
+
+3. If you want TIFF support, cd to the TIFF source directory and type
+ 'nmake -f Makefile.vc'.
+
+4. If you want JPEG support, cd to the JPEG source directory and type
+ 'nmake -f makefile.vc'.
+
+5. If you want X-Face support, copy nt\compface.mak from the xemacs sources
+ to the compface directory, cd to that directory and build libcompface
+ with 'nmake -f compface.mak'.
+
+6. It's also possible to build the Sleepycat DB libraries. Open up the file
+
+ DB-SOURCE-DIR\docs\ref\build_win\intro.html
+
+ in a browser, where DB-SOURCE-DIR is the top-level source directory for
+ the Sleepcat DB libraries, and follow the directions. You should build the
+ `Release_static' target if you want to use the static version of this
+ library, or the `Release' target if you want to use the DLL version of
+ the library. To use the DLL version, you need to set BUILD_DATABASE_SHARED
+ to 1 in config.inc. The DLL version will make the executable much smaller,
+ but you will have to have the DLL present at run-time -- either in the
+ same directory as the XEmacs executable or somewhere in your path.
+
+7. It's possible, but difficult, to build shared libraries for GNU MP.
+ (Static libraries are not yet possible, as there is no makefile.vc for
+ this; you can't build static libraries for VC++ using MinGW.) Basically,
+ you need to build using MinGW and then generate native import libraries.
+ This is more or less described in the documentation, but the following
+ procedure seems to work:
+
+ -- In the top level of the GMP sources, configure using
-1. You really want the XPM library. Grab the latest version of the xpm
- sources (xpm-3.4k.tar.gz as of 2003-10-27) from
- ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack them somewhere. Copy
- nt\xpm.mak from the xemacs sources to the lib subdirectory of the xpm
- sources, cd to that directory and build xpm with 'nmake -f xpm.mak'.
-
-2. You probably also want PNG image support. Grab the latest versions of
- zlib and libpng (zlib-1.1.4 and libpng-1.2.5 as of 2003-10-27) from
- ftp://ftp.xemacs.org/pub/xemacs/aux/, unpack them somewhere and read the
- respective READMEs for details on how to build them. The following
- build procedure works for zlib-1.1.4 and libpng-1.2.5:
-
- cd to the zlib directory and type 'nmake -f nt\Makefile.nt'.
-
- cd to the libpng directory, rename or move the zlib directory to ..\zlib
- and type 'nmake -f scripts\makefile.vcwin32'.
-
-3. If you want TIFF support, grab the latest version of libtiff (tiff-v3.5.7
- as of 2003-10-27) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack
- it somewhere. Then cd to the libtiff subdirectory of the tiff directory
- and type 'nmake -f makefile.vc'.
-
-4. If you want JPEG support grab the latest version of jpegsrc (jpeg-6b as
- of 2003-10-27) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and read the
- README for details on how to build it.
-
-5. If you want X-Face support, grab the latest version of the compface
- distribution (1.4 as of 2003-10-27) from
- ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack it somewhere.
- Copy nt\compface.mak from the xemacs sources to the compface directory.
- cd to that directory and build libcompface with 'nmake -f compface.mak'.
+ CC='gcc -mno-cygwin' configure --build=pentium3-pc-mingw32 --disable-static --enable-shared
+ -- Edit the `libtool' script in the same directory and change the value
+ of CC from `gcc' to `gcc -mno-cygwin'.
+ -- Run `make'.
+
+ -- Run these commands:
+
+ lib /machine:IX86 /def:.libs/libgmp-3.dll-def
+ cp .libs/libgmp-3.dll-exp libgmp-3.exp
+ cp .libs/libgmp-3.dll .
+
+ -- You should now have an import library named libgmp-3.lib and a DLL
+ libgmp-3.dll.
+
+ -- NOTE: You will need to have this DLL accessible when XEmacs runs.
+ It either needs to be in the same directory as the XEmacs executable
+ or in your path.
+
+8. There are also pre-built binaries for GMP-4.1.2 at
+
+ http://www.cs.nyu.edu/exact/core/gmp/.
+
+ However, they don't seem to work properly for our purposes, as they
+ require LIBC.LIB rather than MSVCRT.DLL.
+
+9. You can build the client library for PostgreSQL by cd'ing to the src/
+ subdirectory of the PostgreSQL sources and running `nmake -f win32.mak'.
+
+10. It does not appear to be very easy to build OpenLDAP under
+ native MS Windows, as it is only experimentally supported. However, there
+ is a mailing list for this, which contains postings of recent binaries and
+ build patches; see
+
+ http://lucas.bergmans.us/hacks/openldap/
+
+ If you know how to build OpenLDAP, please write up a description of the
+ process and send it to us at xemacs-beta(a)xemacs.org.
+
+
* Building
==========
＠＠ -120,32 +202,47 ＠＠ systems listed.
line in config.inc as follows:
MULE=1
+
+ -- If you're using the pre-supplied optional library pack, all you should
+ have to do is set OPTIONAL_LIBRARY_DIR to the top-level directory
+ where you unpacked everything.
+
+ -- By default, support is enabled for all graphics formats, but not
+ currently for any of the other libraries in the optional library
+ pack. If you want support for GMP, Berkeley DB or PostgreSQL, set
+ the appropriate flag (HAVE_BIGNUM, HAVE_DATABASE or HAVE_POSTGRESQL,
+ respectively) to 1. We do not currently enable these by default
+ because of lack of sufficient testing, questionable usefulness in
+ the case of Berkeley DB and PostgreSQL, excessive library size in
+ the case of Berkeley DB (more than 2 MB for the static library!),
+ and lack of a static library in the case of GMP.
+
+ -- If you want to turn off support for any of the graphics libraries,
+ set the appropriate flag (HAVE_XPM, HAVE_GIF, HAVE_PNG, HAVE_JPEG,
+ HAVE_TIFF or HAVE_XFACE) to 0.
+
+ -- If you have compiled some of the libraries yourself, you will have to
+ specify the location of the top-level source directory for each of
+ these libraries. XEmacs assumes that the directory structure under
+ these directories is as it is in the sources, rather than in any
+ installed format.
- -- If you're building with XPM support, modify the appropriate lines in
+ For example, for XPM support, modify the appropriate lines in
config.inc as follows:
HAVE_XPM=1
XPM_DIR="x:\location\of\your\xpm\sources"
- and similarly for JPEG and TIFF support.
-
- -- If you're building with PNG support, modify the appropriate lines in
- config.inc as follows:
-
- HAVE_PNG=1
- PNG_DIR="x:\location\of\your\png\sources"
- ZLIB_DIR="x:\location\of\your\zlib\sources"
-
- -- If you're building with GIF support, modify the appropriate lines in
- config.inc as follows:
-
- HAVE_GIF=1
-
- -- If you're building with X-Face support, modify the appropriate lines in
- config.inc as follows:
+ Similarly for JPEG, TIFF, etc. support.
- HAVE_XFACE=1
- COMPFACE_DIR="x:\location\of\your\compface\sources"
+ For PNG support, you also need to specify ZLIB_DIR.
+ For GIF support, no directory is necessary as the appropriate code
+ is already in XEmacs.
+
+ If you want to use the DLL version of the Sleepycat DB library,
+ set BUILD_DATABASE_SHARED to 1. You will have to have the DLL
+ present at run-time -- either in the same directory as the XEmacs
+ executable or somewhere in your path.
-- By default, XEmacs will expect to find its packages in the
subdirectories "site-packages", "mule-packages" and "xemacs-packages"
＠＠ -201,12 +298,16 ＠＠ systems listed.
Start Menu.
5. To build using MS Visual Studio, you can use the workspace file
- `nt/xemacs.dsw'. This was prepared for Visual C++ 6.0. If you have a
- different version and neither file works, just open up `nt/xemacs.mak'
- from within Visual Studio and it will offer to wrap this Makefile in a
- workspace file, from which you can build. Assuming you want to run from
- the build directory (which you will want to do if you are planning on
- doing any development work on XEmacs), use the following settings in
+ `nt/xemacs.dsw'. This was prepared for Visual C++ 6.0. If you are using
+ Visual Studio .NET, open this file up inside of it and it will offer to
+ convert it to a .NET "solution" file. The same procedure should work
+ for newer versions of Visual Studio (e.g. Visual Studio 2005). If this
+ doesn't work (e.g. you are using Visual C++ 5 or even earlier), just
+ open up `nt/xemacs.mak' from within Visual Studio and it will offer to
+ wrap this Makefile in a workspace file, from which you can build.
+ Assuming you want to run from the build directory (which you will want
+ to do if you are planning on doing any development work on XEmacs), use
+ the following settings (for Visual C++ 6.0, at least) in
Project/Settings...:
Under the General tab:
＠＠ -267,8 +368,8 ＠＠ Ben Wing (current primary MS Windows mai
Mule code and some of the dialog box code)
Andy Piper (MS Windows contributor; author of the Cygwin support and the
MS Windows glyph and widget code)
-Jonathan Harris (MS Windows contributor; author of the MS Windows redisplay
- and underlying GUI code)
+Jonathan Harris (MS Windows contributor; original author of the MS Windows
+ redisplay and underlying GUI code)
Kirill Katsnelson (MS Windows contributor; author of the MS Windows process
and printing code and some of the dialog box code;
general guru on obscure MS Windows programming topics)
1.22 +60 -20 XEmacs/xemacs/nt/config.inc.samp
Index: config.inc.samp
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/nt/config.inc.samp,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -p -r1.21 -r1.22
--- config.inc.samp 2005/05/28 04:51:41 1.21
+++ config.inc.samp 2005/09/26 08:13:00 1.22
＠＠ -35,34 +35,36 ＠＠ OPTIONAL_LIBRARY_DIR=c:\src
# Set this to enable XPM support (virtually mandatory), and specify
# the directory containing xpm. Get the library from
-# http://ftp.xemacs.org/aux/xpm-3.4k.tar.gz.
+# http://ftp.xemacs.org/pub/xemacs/aux/xpm-3.4k.tar.gz, or the latest
+# version (note that the library hasn't been updated in years) from
+# http://www.inria.fr/koala/lehors/xpm.html.
HAVE_XPM=1
XPM_DIR=$(OPTIONAL_LIBRARY_DIR)\xpm-3.4k
# Set this to enable GIF support (built-in).
HAVE_GIF=1
-# Set this to enable PNG support (virtually mandatory), and specify
-# the directories containing png and zlib. Get the latest version from
-# ftp://ftp.uu.net/graphics/png/. NOTE: In order to compile libpng,
-# you will have to rename the zlib directory to just `zlib'. We don't
-# do that here so we can preserve the version number, like for the other
-# libraries.
+# Set this to enable PNG support (virtually mandatory), and specify the
+# directories containing png and zlib. Get the latest version of PNG from
+# http://www.libpng.org/pub/png/libpng.html. Get the latest version of ZLIB
+# from http://www.gzip.org/zlib/. NOTE: In order to compile libpng, you will
+# have to rename the zlib directory to just `zlib'. We don't do that here
+# so we can preserve the version number, like for the other libraries.
HAVE_PNG=1
PNG_DIR=$(OPTIONAL_LIBRARY_DIR)\libpng-1.2.8
-ZLIB_DIR=$(OPTIONAL_LIBRARY_DIR)\zlib-1.2.1
+ZLIB_DIR=$(OPTIONAL_LIBRARY_DIR)\zlib-1.2.3
# Set this to enable JPEG support (useful, but not necessary), and specify
# the directory containing jpeg. Get the latest version from
-# ftp://ftp.uu.net/graphics/jpeg/.
+# http://www.ijg.org/ or ftp://ftp.uu.net/graphics/jpeg/.
HAVE_JPEG=1
JPEG_DIR=$(OPTIONAL_LIBRARY_DIR)\jpeg-6b
# Set this to enable TIFF support (not very important), and specify the
# directory containing tiff. Get the latest version from
-# ftp://ftp.uu.net/graphics/tiff/.
+# http://www.remotesensing.org/libtiff/.
HAVE_TIFF=1
-TIFF_DIR=$(OPTIONAL_LIBRARY_DIR)\tiff-v3.5.7
+TIFF_DIR=$(OPTIONAL_LIBRARY_DIR)\tiff-3.7.3
# Set this to enable XFace support (not very important), and specify the
# directory containing compface. Get the library from
＠＠ -70,6 +72,39 ＠＠ TIFF_DIR=$(OPTIONAL_LIBRARY_DIR)\tiff-v3
HAVE_XFACE=1
COMPFACE_DIR=$(OPTIONAL_LIBRARY_DIR)\compface-1.5.1
+# Set this to enable bignum support (useful, but not necessary), and specify
+# the directory containing GNU MP. Get the latest version from
+# http://www.swox.com/gmp/.
+HAVE_BIGNUM=0
+BIGNUM_DIR=$(OPTIONAL_LIBRARY_DIR)\gmp-4.1.4
+
+# Set this to enable Berkeley DB support (not very important), and specify
+# the directory containing Sleepcat DB. Get the latest version from
+# http://www.sleepycat.com/products/db.shtml. If you want to use the
+# shared-library (DLL) version instead of the static library, set
+# BUILD_DATABASE_SHARED to 1.
+HAVE_DATABASE=0
+BUILD_DATABASE_SHARED=0
+DATABASE_DIR=$(OPTIONAL_LIBRARY_DIR)\db-4.3.28
+
+# Set this to enable PostgreSQL support (not very important), and specify
+# the directory containing PostgreSQL. Get the latest version from
+# http://www.postgresql.org/.
+HAVE_POSTGRESQL=0
+POSTGRESQL_DIR=$(OPTIONAL_LIBRARY_DIR)\postgresql-8.0.3
+
+# Set this to enable LDAP support (not very important), and specify
+# the directory containing LDAP. It is not easy to build OpenLDAP under
+# native MS Windows, as it is only experimentally supported. However, there
+# is a mailing list for this, which contains postings of recent binaries and
+# build patches; see
+#
+# http://lucas.bergmans.us/hacks/openldap/
+#
+# Get the latest version of OpenLDAP from http://www.openldap.org/.
+HAVE_LDAP=0
+LDAP_DIR=$(OPTIONAL_LIBRARY_DIR)\openldap-2.3.4
+
############################################################################
# Build settings #
############################################################################
＠＠ -116,8 +151,21 ＠＠ COMPFACE_DIR=$(OPTIONAL_LIBRARY_DIR)\com
# the actual file system).
MAKEINFO=c:\cygwin\bin\makeinfo.exe
-# Set this to turn on optimization when compiling.
+# Set this to enable debug code in XEmacs that doesn't slow things down,
+# and to add debugging information to the executable. (The code that's
+# enabled in XEmacs is primarily extra commands that aid in debugging
+# problems. The kind of debugging code that slows things down --
+# i.e. internal error-checking -- is controlled by the ERROR_CHECK_ALL
+# variable, below.)
+DEBUG_XEMACS=1
+
+# Set this to turn on optimization when compiling. Normally this should
+# be the opposite of DEBUG_XEMACS.
+!if $(DEBUG_XEMACS)
OPTIMIZED_BUILD=0
+!else
+OPTIMIZED_BUILD=1
+!endif
# Set this to build with the fastcall calling convention, which uses registers
# instead of the stack and should speed things up a bit
＠＠ -131,14 +179,6 ＠＠ USE_FASTCALL=0
# Set this to compile in support for profiling. If you want line-by-line
# profiling under VC++, you also need debugging turned on.
PROFILE_SUPPORT=0
-
-# Set this to enable debug code in XEmacs that doesn't slow things down,
-# and to add debugging information to the executable. (The code that's
-# enabled in XEmacs is primarily extra commands that aid in debugging
-# problems. The kind of debugging code that slows things down --
-# i.e. internal error-checking -- is controlled by the ERROR_CHECK_ALL
-# variable, below.)
-DEBUG_XEMACS=1
# Set this to enable support for edit-and-continue under VC++.
# WARNING: This turns on incremental linking, which is known to lead to
1.9 +4 -0 XEmacs/xemacs/nt/minitar.c
Index: minitar.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/nt/minitar.c,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -p -r1.8 -r1.9
--- minitar.c 2003/11/06 22:53:31 1.8
+++ minitar.c 2005/09/26 08:13:00 1.9
＠＠ -12,6 +12,10 ＠＠
If it breaks, you get to keep both pieces */
+#ifdef HAVE_CONFIG_H
+# include <config.h>
+#endif
+
#include <stdio.h>
#include <stdlib.h>
#include <errno.h>
1.116 +285 -105 XEmacs/xemacs/nt/xemacs.mak
Index: xemacs.mak
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/nt/xemacs.mak,v
retrieving revision 1.115
retrieving revision 1.116
diff -u -p -r1.115 -r1.116
--- xemacs.mak 2005/09/25 19:13:43 1.115
+++ xemacs.mak 2005/09/26 08:13:00 1.116
＠＠ -1,7 +1,7 ＠＠
# Makefile for Microsoft NMAKE -*- Makefile -*-
#
# Copyright (C) 1995 Board of Trustees, University of Illinois.
-# Copyright (C) 1995, 1996, 2000, 2001, 2002, 2003, 2004 Ben Wing.
+# Copyright (C) 1995, 1996, 2000, 2001, 2002, 2003, 2004, 2005 Ben Wing.
# Copyright (C) 1997, 1998, 2000 Jonathan Harris.
# Copyright (C) 1995 Sun Microsystems, Inc.
# Copyright (C) 1998 Free Software Foundation, Inc.
＠＠ -95,6 +95,14 ＠＠ BLDSRC=$(BLDROOT)\src
# This appears in the dependency file
LWLIB_SRCDIR=$(SRCROOT)\lwlib
+########################### Figure out current version of VC++.
+
+!if [echo MSC_VER=_MSC_VER > $(OUTDIR)\vcversion.c]
+!endif
+!if [cl /nologo /EP $(OUTDIR)\vcversion.c > $(OUTDIR)\vcversion.tmp]
+!endif
+!include "$(OUTDIR)\vcversion.tmp"
+
########################### Process the config.inc options.
!if !defined(INFODOCK)
＠＠ -148,6 +156,21 ＠＠ HAVE_NATIVE_SOUND=1
!if !defined(HAVE_WIDGETS)
HAVE_WIDGETS=1
!endif
+!if !defined(HAVE_DATABASE)
+HAVE_DATABASE=0
+!endif
+!if !defined(BUILD_DATABASE_SHARED)
+BUILD_DATABASE_SHARED=0
+!endif
+!if !defined(HAVE_POSTGRESQL)
+HAVE_POSTGRESQL=0
+!endif
+!if !defined(HAVE_LDAP)
+HAVE_LDAP=0
+!endif
+!if !defined(HAVE_BIGNUM)
+HAVE_BIGNUM=0
+!endif
!if !defined(OPTIMIZED_BUILD)
OPTIMIZED_BUILD=1
!endif
＠＠ -249,6 +272,7 ＠＠ CONFIG_ERROR=1
!message Please specify root directory for your GTK installation: GTK_DIR=path
CONFIG_ERROR=1
!endif
+
!if $(HAVE_MS_WINDOWS) && $(HAVE_XPM) && !defined(XPM_DIR)
!message Please specify root directory for your XPM installation: XPM_DIR=path
CONFIG_ERROR=1
＠＠ -257,6 +281,7 ＠＠ CONFIG_ERROR=1
!message Specified XPM directory does not contain "$(XPM_DIR)\lib\Xpm.lib"
CONFIG_ERROR=1
!endif
+
!if $(HAVE_MS_WINDOWS) && $(HAVE_PNG) && !defined(PNG_DIR)
!message Please specify root directory for your PNG installation: PNG_DIR=path
CONFIG_ERROR=1
＠＠ -265,6 +290,7 ＠＠ CONFIG_ERROR=1
!message Specified PNG directory does not contain "$(PNG_DIR)\libpng.lib"
CONFIG_ERROR=1
!endif
+
!if $(HAVE_MS_WINDOWS) && $(HAVE_PNG) && !defined(ZLIB_DIR)
!message Please specify root directory for your ZLIB installation: ZLIB_DIR=path
CONFIG_ERROR=1
＠＠ -273,6 +299,7 ＠＠ CONFIG_ERROR=1
!message Specified ZLIB directory does not contain "$(ZLIB_DIR)\zlib.lib"
CONFIG_ERROR=1
!endif
+
!if $(HAVE_MS_WINDOWS) && $(HAVE_TIFF) && !defined(TIFF_DIR)
!message Please specify root directory for your TIFF installation: TIFF_DIR=path
CONFIG_ERROR=1
＠＠ -281,6 +308,7 ＠＠ CONFIG_ERROR=1
!message Specified TIFF directory does not contain "$(TIFF_DIR)\libtiff\libtiff.lib"
CONFIG_ERROR=1
!endif
+
!if $(HAVE_MS_WINDOWS) && $(HAVE_JPEG) && !defined(JPEG_DIR)
!message Please specify root directory for your JPEG installation: JPEG_DIR=path
CONFIG_ERROR=1
＠＠ -289,6 +317,7 ＠＠ CONFIG_ERROR=1
!message Specified JPEG directory does not contain "$(JPEG_DIR)\libjpeg.lib"
CONFIG_ERROR=1
!endif
+
!if $(HAVE_MS_WINDOWS) && $(HAVE_XFACE) && !defined(COMPFACE_DIR)
!message Please specify root directory for your COMPFACE installation: COMPFACE_DIR=path
CONFIG_ERROR=1
＠＠ -297,10 +326,71 ＠＠ CONFIG_ERROR=1
!message Specified COMPFACE directory does not contain "$(COMPFACE_DIR)\libcompface.lib"
CONFIG_ERROR=1
!endif
+
!if $(HAVE_MS_WINDOWS) && $(HAVE_TOOLBARS) && !$(HAVE_XPM)
!message Toolbars require XPM support
CONFIG_ERROR=1
!endif
+
+!if $(HAVE_MS_WINDOWS) && $(HAVE_BIGNUM) && !defined(BIGNUM_DIR)
+!message Please specify root directory for your BIGNUM installation: BIGNUM_DIR=path
+CONFIG_ERROR=1
+!endif
+!if $(HAVE_MS_WINDOWS) && $(HAVE_BIGNUM) && defined(BIGNUM_DIR)
+!if $(BUILD_BIGNUM_MINGW_SHARED)
+!if !exist("$(BIGNUM_DIR)\libgmp-3.lib")
+!message Specified BIGNUM directory does not contain "$(BIGNUM_DIR)\libgmp-3.lib"
+CONFIG_ERROR=1
+!endif
+!else
+!if $(BUILD_BIGNUM_NATIVE_SHARED)
+!if !exist("$(BIGNUM_DIR)\gmp-dynamic\gmp.lib")
+!message Specified BIGNUM directory does not contain "$(BIGNUM_DIR)\gmp-dynamic\gmp.lib"
+CONFIG_ERROR=1
+!endif
+!else
+!if !exist("$(BIGNUM_DIR)\gmp-static\gmp.lib")
+!message Specified BIGNUM directory does not contain "$(BIGNUM_DIR)\gmp-static\gmp.lib"
+CONFIG_ERROR=1
+!endif
+!endif
+!endif
+!endif
+
+!if $(HAVE_MS_WINDOWS) && $(HAVE_DATABASE) && !defined(DATABASE_DIR)
+!message Please specify root directory for your DATABASE installation: DATABASE_DIR=path
+CONFIG_ERROR=1
+!endif
+!if $(HAVE_MS_WINDOWS) && $(HAVE_DATABASE) && defined(DATABASE_DIR)
+!if $(BUILD_DATABASE_SHARED)
+!if !exist("$(DATABASE_DIR)\build_win32\Release\libdb43.lib")
+!message Specified DATABASE directory does not contain "$(DATABASE_DIR)\build_win32\Release\libdb43.lib"
+CONFIG_ERROR=1
+!endif
+!else
+!if !exist("$(DATABASE_DIR)\build_win32\Release_static\libdb43s.lib")
+!message Specified DATABASE directory does not contain "$(DATABASE_DIR)\build_win32\Release_static\libdb43s.lib"
+CONFIG_ERROR=1
+!endif
+!endif
+!endif
+
+!if $(HAVE_MS_WINDOWS) && $(HAVE_POSTGRESQL) && !defined(POSTGRESQL_DIR)
+!message Please specify root directory for your POSTGRESQL installation: POSTGRESQL_DIR=path
+CONFIG_ERROR=1
+!endif
+!if $(HAVE_MS_WINDOWS) && $(HAVE_POSTGRESQL) && defined(POSTGRESQL_DIR) && !exist("$(POSTGRESQL_DIR)\src\interfaces\libpq\Release\libpq.lib")
+!message Specified POSTGRESQL directory does not contain "$(POSTGRESQL_DIR)\src\interfaces\libpq\Release\libpq.lib"
+CONFIG_ERROR=1
+!endif
+!if $(HAVE_MS_WINDOWS) && $(HAVE_LDAP) && !defined(LDAP_DIR)
+!message Please specify root directory for your LDAP installation: LDAP_DIR=path
+CONFIG_ERROR=1
+!endif
+!if $(HAVE_MS_WINDOWS) && $(HAVE_LDAP) && defined(LDAP_DIR) && !exist("$(LDAP_DIR)\openldap.lib")
+!message Specified LDAP directory does not contain "$(LDAP_DIR)\openldap.lib"
+CONFIG_ERROR=1
+!endif
!if $(CONFIG_ERROR)
!error Configuration error(s) found
!endif
＠＠ -385,137 +475,175 ＠＠ EMACS_CONFIGURATION=ppc-pc-win32
STACK_TRACE_EYE_CATCHER=$(XEMACS_VERSION_STRING:.=_)
STACK_TRACE_EYE_CATCHER=xemacs_$(STACK_TRACE_EYE_CATCHER:-=_)_$(EMACS_CONFIGURATION:-=_)
PROGRAM_DEFINES=$(PROGRAM_DEFINES) -DSTACK_TRACE_EYE_CATCHER=$(STACK_TRACE_EYE_CATCHER)
+
+########################### Determine includes/defines/object files/libraries
+########################### for all configuration options given.
-########################### Determine includes/defines/object file for
-########################### various options.
+OPT_DEFINES=
+OPT_INCLUDES=
+OPT_LIBS=
+OPT_OBJS=
+TEMACS_MODULE_OBJS=
+TEMACS_MODULE_SRCS=
!if $(HAVE_MS_WINDOWS)
-MSW_DEFINES=-DHAVE_MS_WINDOWS
-MSW_INCLUDES=
-MSW_LIBS=comctl32.lib
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_MS_WINDOWS
+OPT_LIBS=$(OPT_LIBS) comctl32.lib
+OPT_OBJS=$(OPT_OBJS) \
+ $(OUTDIR)\console-msw.obj \
+ $(OUTDIR)\device-msw.obj \
+ $(OUTDIR)\event-msw.obj \
+ $(OUTDIR)\frame-msw.obj \
+ $(OUTDIR)\glyphs-msw.obj \
+ $(OUTDIR)\gui-msw.obj \
+ $(OUTDIR)\objects-msw.obj \
+ $(OUTDIR)\redisplay-msw.obj \
+ $(OUTDIR)\select-msw.obj \
+ $(OUTDIR)\dired-msw.obj
+!if $(HAVE_MENUBARS)
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_MENUBARS
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\menubar.obj $(OUTDIR)\menubar-msw.obj
+!endif
+!if $(HAVE_SCROLLBARS)
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_SCROLLBARS
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\scrollbar.obj $(OUTDIR)\scrollbar-msw.obj
+!endif
+!if $(HAVE_TOOLBARS)
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_TOOLBARS
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\toolbar.obj $(OUTDIR)\toolbar-msw.obj
+!endif
+!if $(HAVE_WIDGETS)
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_WIDGETS
+!endif
+!if $(HAVE_DIALOGS)
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_DIALOGS
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\dialog.obj $(OUTDIR)\dialog-msw.obj
+!endif
+# end !if $(HAVE_MS_WINDOWS)
+!endif
!if $(HAVE_XPM)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_XPM -DFOR_MSW
-MSW_INCLUDES=$(MSW_INCLUDES) -I"$(XPM_DIR)" -I"$(XPM_DIR)\lib"
-MSW_LIBS=$(MSW_LIBS) "$(XPM_DIR)\lib\Xpm.lib"
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_XPM -DFOR_MSW
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(XPM_DIR)" -I"$(XPM_DIR)\lib"
+OPT_LIBS=$(OPT_LIBS) "$(XPM_DIR)\lib\Xpm.lib"
!endif
!if $(HAVE_GIF)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_GIF
-MSW_GIF_OBJ=$(OUTDIR)\dgif_lib.obj $(OUTDIR)\gif_io.obj
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_GIF
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\dgif_lib.obj $(OUTDIR)\gif_io.obj
!endif
!if $(HAVE_PNG)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_PNG
-MSW_INCLUDES=$(MSW_INCLUDES) -I"$(PNG_DIR)" -I"$(ZLIB_DIR)"
-MSW_LIBS=$(MSW_LIBS) "$(PNG_DIR)\libpng.lib" "$(ZLIB_DIR)\zlib.lib"
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_PNG
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(PNG_DIR)" -I"$(ZLIB_DIR)"
+OPT_LIBS=$(OPT_LIBS) "$(PNG_DIR)\libpng.lib" "$(ZLIB_DIR)\zlib.lib"
!endif
!if $(HAVE_TIFF)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_TIFF
-MSW_INCLUDES=$(MSW_INCLUDES) -I"$(TIFF_DIR)\libtiff"
-MSW_LIBS=$(MSW_LIBS) "$(TIFF_DIR)\libtiff\libtiff.lib"
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_TIFF
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(TIFF_DIR)\libtiff"
+OPT_LIBS=$(OPT_LIBS) "$(TIFF_DIR)\libtiff\libtiff.lib"
!endif
!if $(HAVE_JPEG)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_JPEG
-MSW_INCLUDES=$(MSW_INCLUDES) -I"$(JPEG_DIR)"
-MSW_LIBS=$(MSW_LIBS) "$(JPEG_DIR)\libjpeg.lib"
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_JPEG
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(JPEG_DIR)"
+OPT_LIBS=$(OPT_LIBS) "$(JPEG_DIR)\libjpeg.lib"
!endif
!if $(HAVE_XFACE)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_XFACE
-MSW_INCLUDES=$(MSW_INCLUDES) -I"$(COMPFACE_DIR)"
-MSW_LIBS=$(MSW_LIBS) "$(COMPFACE_DIR)\libcompface.lib"
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_XFACE
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(COMPFACE_DIR)"
+OPT_LIBS=$(OPT_LIBS) "$(COMPFACE_DIR)\libcompface.lib"
!endif
!if $(HAVE_ZLIB)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_ZLIB
-MSW_INCLUDES=$(MSW_INCLUDES) -I"$(ZLIB_DIR)"
-MSW_LIBS=$(MSW_LIBS) "$(ZLIB_DIR)\zlib.lib"
-!endif
-!if $(HAVE_MENUBARS)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_MENUBARS
-MSW_MENUBAR_OBJ=$(OUTDIR)\menubar.obj $(OUTDIR)\menubar-msw.obj
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_ZLIB
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(ZLIB_DIR)"
+OPT_LIBS=$(OPT_LIBS) "$(ZLIB_DIR)\zlib.lib"
+!endif
+!if $(HAVE_BIGNUM)
+OPT_DEFINES=$(OPT_DEFINES) -DWITH_NUMBER_TYPES -DWITH_GMP
+!if $(BUILD_BIGNUM_MINGW_SHARED)
+OPT_LIBS=$(OPT_LIBS) "$(BIGNUM_DIR)\libgmp-3.lib"
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(BIGNUM_DIR)"
+!else
+!if $(BUILD_BIGNUM_NATIVE_SHARED)
+OPT_LIBS=$(OPT_LIBS) "$(BIGNUM_DIR)\gmp-dynamic\gmp.lib"
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(BIGNUM_DIR)\gmp-dynamic"
+!else
+OPT_LIBS=$(OPT_LIBS) "$(BIGNUM_DIR)\gmp-static\gmp.lib"
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(BIGNUM_DIR)\gmp-static"
+!endif
+!endif
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\number-gmp.obj $(OUTDIR)\number.obj
+!endif
+!if $(HAVE_DATABASE)
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_DATABASE -DHAVE_BERKELEY_DB -DDB_H_FILE=\"db.h\"
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(DATABASE_DIR)\build_win32"
+!if $(BUILD_DATABASE_SHARED)
+OPT_LIBS=$(OPT_LIBS) "$(DATABASE_DIR)\build_win32\Release\libdb43.lib"
+!else
+OPT_LIBS=$(OPT_LIBS) "$(DATABASE_DIR)\build_win32\Release_static\libdb43s.lib"
+!endif
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\database.obj
+!endif
+!if $(HAVE_POSTGRESQL)
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_POSTGRESQL -DHAVE_POSTGRESQLV7 -DLIBPQ_FE_H_FILE=\"libpq-fe.h\"
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(POSTGRESQL_DIR)\src\include" -I"$(POSTGRESQL_DIR)\src\interfaces\libpq"
+OPT_LIBS=$(OPT_LIBS) "$(POSTGRESQL_DIR)\src\interfaces\libpq\Release\libpq.lib"
+TEMACS_MODULE_OBJS=$(TEMACS_MODULE_OBJS) $(OUTDIR)\postgresql.obj
+TEMACS_MODULE_SRCS=$(TEMACS_MODULE_SRCS) $(SRCROOT)\modules\postgresql\postgresql.c
+!endif
+!if $(HAVE_LDAP)
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_LDAP -DHAVE_LDAP_SET_OPTION -DHAVE_LDAP_RESULT2ERROR -DHAVE_LDAP_PARSE_RESULT
+OPT_INCLUDES=$(OPT_INCLUDES) -I"$(LDAP_DIR)"
+OPT_LIBS=$(OPT_LIBS) "$(LDAP_DIR)\openldap.lib"
+TEMACS_MODULE_OBJS=$(TEMACS_MODULE_OBJS) $(OUTDIR)\eldap.obj
+TEMACS_MODULE_SRCS=$(TEMACS_MODULE_SRCS) $(SRCROOT)\modules\ldap\eldap.c
!endif
-!if $(HAVE_SCROLLBARS)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_SCROLLBARS
-MSW_SCROLLBAR_OBJ=$(OUTDIR)\scrollbar.obj $(OUTDIR)\scrollbar-msw.obj
-!endif
-!if $(HAVE_TOOLBARS)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_TOOLBARS
-MSW_TOOLBAR_OBJ=$(OUTDIR)\toolbar.obj $(OUTDIR)\toolbar-msw.obj
-!endif
-!if $(HAVE_WIDGETS)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_WIDGETS
-!endif
-!if $(HAVE_DIALOGS)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_DIALOGS
-MSW_DIALOG_OBJ=$(OUTDIR)\dialog.obj $(OUTDIR)\dialog-msw.obj
-!endif
!if $(HAVE_NATIVE_SOUND)
-MSW_DEFINES=$(MSW_DEFINES) -DHAVE_NATIVE_SOUND
+OPT_DEFINES=$(OPT_DEFINES) -DHAVE_NATIVE_SOUND
!endif
-TEMACS_MSW_OBJS=\
- $(OUTDIR)\console-msw.obj \
- $(OUTDIR)\device-msw.obj \
- $(OUTDIR)\event-msw.obj \
- $(OUTDIR)\frame-msw.obj \
- $(OUTDIR)\glyphs-msw.obj \
- $(OUTDIR)\gui-msw.obj \
- $(OUTDIR)\objects-msw.obj \
- $(OUTDIR)\redisplay-msw.obj \
- $(OUTDIR)\select-msw.obj \
- $(OUTDIR)\dired-msw.obj \
- $(MSW_MENUBAR_OBJ) \
- $(MSW_SCROLLBAR_OBJ) \
- $(MSW_TOOLBAR_OBJ) \
- $(MSW_DIALOG_OBJ) \
- $(MSW_GIF_OBJ)
-
-# end !if $(HAVE_MS_WINDOWS)
-!endif
-
!if $(MULE)
-MULE_DEFINES=-DMULE
-TEMACS_MULE_OBJS=\
+OPT_DEFINES=$(OPT_DEFINES) -DMULE
+OPT_OBJS=$(OPT_OBJS) \
$(OUTDIR)\mule-ccl.obj \
$(OUTDIR)\mule-charset.obj \
$(OUTDIR)\mule-coding.obj
!endif
!if $(DEBUG_XEMACS)
-TEMACS_DEBUG_OBJS=$(OUTDIR)\debug.obj $(OUTDIR)\tests.obj
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\debug.obj $(OUTDIR)\tests.obj
!endif
!if $(QUICK_BUILD)
-QUICK_DEFINES=-DQUICK_BUILD
+OPT_DEFINES=$(OPT_DEFINES) -DQUICK_BUILD
!endif
!if $(ERROR_CHECK_ALL)
-ERROR_CHECK_DEFINES=-DERROR_CHECK_ALL
+OPT_DEFINES=$(OPT_DEFINES) -DERROR_CHECK_ALL
!endif
!if $(USE_UNION_TYPE)
-UNION_DEFINES=-DUSE_UNION_TYPE
+OPT_DEFINES=$(OPT_DEFINES) -DUSE_UNION_TYPE
!endif
!if $(USE_PORTABLE_DUMPER)
-DUMPER_DEFINES=-DPDUMP
-TEMACS_DUMP_OBJS=$(OUTDIR)\dumper.obj
+OPT_DEFINES=$(OPT_DEFINES) -DPDUMP
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\dumper.obj
!else
-TEMACS_DUMP_OBJS=$(OUTDIR)\unexnt.obj
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\unexnt.obj
!endif
!if $(USE_KKCC)
-KKCC_DEFINES=-DUSE_KKCC
+OPT_DEFINES=$(OPT_DEFINES) -DUSE_KKCC
!endif
-
!if $(MC_ALLOC)
-MC_ALLOC_DEFINES=-DMC_ALLOC
-TEMACS_MC_ALLOC_OBJS=$(OUTDIR)\mc-alloc.obj
+OPT_DEFINES=$(OPT_DEFINES) -DMC_ALLOC
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\mc-alloc.obj
!endif
!if $(USE_SYSTEM_MALLOC)
-MALLOC_DEFINES=-DSYSTEM_MALLOC
+OPT_DEFINES=$(OPT_DEFINES) -DSYSTEM_MALLOC
!else
-MALLOC_DEFINES=-DGNU_MALLOC
-TEMACS_ALLOC_OBJS=$(OUTDIR)\free-hook.obj $(OUTDIR)\gmalloc.obj \
+OPT_DEFINES=$(OPT_DEFINES) -DGNU_MALLOC
+OPT_OBJS=$(OPT_OBJS) $(OUTDIR)\free-hook.obj $(OUTDIR)\gmalloc.obj \
$(OUTDIR)\ntheap.obj $(OUTDIR)\vm-limit.obj
!endif
＠＠ -533,27 +661,46 ＠＠ CCV=＠$(CC)
!if $(DEBUG_XEMACS)
# ---- Debugging support ----
+! if $(MSC_VER) >= 1400
+# VC 7 sets opt:noref automatically with -debug. VC 8 apparently doesn't
+# do this, and then complains if you try to use edit-and-continue without
+# giving it.
+DEBUG_FLAG_LINK_DEBUG=-debug -opt:noref
+# This turns on additional run-time checking
+# For some reason it causes spawning of make-docfile to crash in VC 7
+DEBUG_FLAG_COMPILE_DEBUG=-RTC1
+! else
+DEBUG_FLAG_LINK_DEBUG=-debug:full
+DEBUG_FLAG_COMPILE_DEBUG=
+! endif
+
! if $(SUPPORT_EDIT_AND_CONTINUE)
# support edit-and-continue
-DEBUG_FLAGS_COMPILE=-ZI
+DEBUG_FLAGS_COMPILE=$(DEBUG_FLAG_COMPILE_DEBUG) -ZI
# WARNING: There is a very good reason for -incremental:no, as it can cause
# all sorts of weird crashes in or after a pdump load. We must allow
# incremental linking for edit-and-continue to work, however.
-DEBUG_FLAGS_LINK=-debug:full
+DEBUG_FLAGS_LINK=$(DEBUG_FLAG_LINK_DEBUG)
! else
-DEBUG_FLAGS_COMPILE=-Zi
-DEBUG_FLAGS_LINK=-debug:full -incremental:no
+DEBUG_FLAGS_COMPILE=$(DEBUG_FLAG_COMPILE_DEBUG) -Zi
+DEBUG_FLAGS_LINK=$(DEBUG_FLAG_LINK_DEBUG) -incremental:no
! endif
-DEBUG_DEFINES=-DDEBUG_XEMACS -D_DEBUG
+
+OPT_DEFINES=$(OPT_DEFINES) -DDEBUG_XEMACS -D_DEBUG
+
+! if $(MSC_VER) >= 1300
+#BROWSERFLAGS=-FR -Fd$(OUTDIR)\temacs.pdb
+BROWSERFLAGS=-FR$*.sbr -Fd$(OUTDIR)\temacs.pdb
+! else
#BROWSERFLAGS=-Fr -Fd$(OUTDIR)\temacs.pdb
BROWSERFLAGS=-Fr$*.sbr -Fd$(OUTDIR)\temacs.pdb
+! endif
!else
# ---- No debugging support ----
DEBUG_FLAGS_COMPILE=
DEBUG_FLAGS_LINK=-incremental:no
-DEBUG_DEFINES=
BROWSERFLAGS=
!endif
＠＠ -572,6 +719,9 ＠＠ LIBC_LIB=libc.lib
!endif
!if $(OPTIMIZED_BUILD)
+!if $(SUPPORT_EDIT_AND_CONTINUE)
+!error Edit-and-continue is not compatible with optimization.
+!endif
# -G5 means optimize for Pentium. (According to the code-optimization
# article, -GB is the same as -G5, and -G6, i.e. optimze for Pentium Pro,
# gains you little over -G5 for PPro's but causes big slowdowns for
＠＠ -610,12 +760,10 ＠＠ CPLUSPLUS_COMPILE_FLAGS=
########################### Determine generic includes/defines/flags.
-INCLUDES=-I$(NT)\inc -I$(SRC) $(MSW_INCLUDES)
+INCLUDES=-I$(NT)\inc -I$(SRC) $(OPT_INCLUDES)
-DEFINES=$(MSW_DEFINES) $(MULE_DEFINES) $(UNION_DEFINES) \
- $(DUMPER_DEFINES) $(KKCC_DEFINES) $(MC_ALLOC_DEFINES) \
- $(MALLOC_DEFINES) $(QUICK_DEFINES) $(ERROR_CHECK_DEFINES) \
- $(DEBUG_DEFINES) -DWIN32_LEAN_AND_MEAN -DWIN32_NATIVE -Demacs \
+DEFINES=$(OPT_DEFINES) \
+ -DWIN32_LEAN_AND_MEAN -DWIN32_NATIVE -Demacs \
-DHAVE_CONFIG_H $(PROGRAM_DEFINES) $(PATH_DEFINES)
CFLAGS_NO_OPT=-nologo -W3 -DSTRICT $(DEBUG_FLAGS_COMPILE)
＠＠ -653,13 +801,8 ＠＠ TEMACS_CPP_CDECL_FLAGS=$(CFLAGS_CDECL) $
########################### Determine XEmacs object files.
-TEMACS_OBJS= \
- $(TEMACS_MSW_OBJS)\
- $(TEMACS_MULE_OBJS)\
- $(TEMACS_DEBUG_OBJS)\
- $(TEMACS_ALLOC_OBJS)\
- $(TEMACS_DUMP_OBJS)\
- $(TEMACS_MC_ALLOC_OBJS)\
+TEMACS_COMMON_OBJS= \
+ $(OPT_OBJS)\
$(OUTDIR)\abbrev.obj \
$(OUTDIR)\alloc.obj \
$(OUTDIR)\alloca.obj \
＠＠ -753,6 +896,14 ＠＠ TEMACS_OBJS= \
$(OUTDIR)\window.obj \
$(OUTDIR)\win32.obj
+TEMACS_OBJS= \
+ $(TEMACS_COMMON_OBJS) \
+ $(TEMACS_MODULE_OBJS)
+
+TEMACS_DOC_SOURCES= \
+ $(TEMACS_COMMON_OBJS) \
+ $(TEMACS_MODULE_SRCS)
+
#########################################################################
## Implicit rules ##
#########################################################################
＠＠ -822,6 +973,12 ＠＠ $(OUTDIR)\emacs.obj: $(SRCROOT)\version.
$(OUTDIR)\libinterface.obj: $(SRC)\libinterface.c
$(CCV) $(TEMACS_CPP_CDECL_FLAGS) $(SRC)\$((a)B).c -Fo$＠ $(BROWSERFLAGS)
+$(OUTDIR)\postgresql.obj: $(SRCROOT)\modules\postgresql\postgresql.c
+ $(CCV) -I$(SRC) $(TEMACS_CPP_FLAGS) $(SRCROOT)\modules\postgresql\postgresql.c -Fo$＠ $(BROWSERFLAGS)
+
+$(OUTDIR)\eldap.obj: $(SRCROOT)\modules\ldap\eldap.c
+ $(CCV) -I$(SRC) $(TEMACS_CPP_FLAGS) $(SRCROOT)\modules\ldap\eldap.c -Fo$＠ $(BROWSERFLAGS)
+
###################### Generated source files
$(OUTDIR)\nul:
＠＠ -920,7 +1077,7 ＠＠ $(BLDLIB_SRC)/movemail.exe : $(LIB_SRC)/
# Minitar uses zlib so just use cdecl to simplify things
$(BLDLIB_SRC)/minitar.exe : $(NT)/minitar.c
- $(CCV) -I"$(ZLIB_DIR)" $(LIB_SRC_DEFINES) $(CFLAGS_CDECL_NO_LIB) -MD $(LINK_DEPENDENCY_ARGS) "$(ZLIB_DIR)\zlib.lib"
+ $(CCV) -I$(SRC) -I"$(ZLIB_DIR)" $(LIB_SRC_DEFINES) $(CFLAGS_CDECL_NO_LIB) -MD $(LINK_DEPENDENCY_ARGS) "$(ZLIB_DIR)\zlib.lib"
LIB_SRC_TOOLS = \
$(BLDLIB_SRC)/etags.exe \
＠＠ -1034,6 +1191,22 ＠＠ XEmacs $(XEMACS_VERSION_STRING) $(xemacs
!if $(HAVE_WIDGETS)
Compiling in support for widgets.
!endif
+!if $(HAVE_BIGNUM)
+ Compiling in support for arbitrary-precision numbers.
+!endif
+!if $(HAVE_DATABASE)
+!if $(BUILD_DATABASE_SHARED)
+ Compiling in support for Berkeley Databases (DLL version).
+!else
+ Compiling in support for Berkeley Databases (static-library version).
+!endif
+!endif
+!if $(HAVE_POSTGRESQL)
+ Compiling in support for PostgreSQL.
+!endif
+!if $(HAVE_LDAP)
+ Compiling in support for LDAP.
+!endif
!if $(HAVE_NATIVE_SOUND)
Compiling in support for native sounds.
!endif
＠＠ -1096,7 +1269,7 ＠＠ TEMACS_ENTRYPOINT=-entry:mainCRTStartup
!endif
TEMACS_BROWSE=$(BLDSRC)\temacs.bsc
-TEMACS_LIBS=$(LASTFILE) $(MSW_LIBS) \
+TEMACS_LIBS=$(LASTFILE) $(OPT_LIBS) \
oldnames.lib kernel32.lib user32.lib gdi32.lib comdlg32.lib advapi32.lib \
shell32.lib wsock32.lib netapi32.lib winmm.lib winspool.lib ole32.lib \
mpr.lib uuid.lib imm32.lib $(LIBC_LIB)
＠＠ -1162,6 +1335,7 ＠＠ TEMACS_DUMP_DEP = $(OUTDIR)\temacs.res
!endif
$(RAW_EXE): $(TEMACS_OBJS) $(LASTFILE) $(TEMACS_DUMP_DEP)
+ ＠echo link $(TEMACS_LFLAGS) -out:$＠ $(TEMACS_OBJS) $(TEMACS_DUMP_DEP) $(TEMACS_LIBS)
link.exe ＠<<
$(TEMACS_LFLAGS) -out:$＠ $(TEMACS_OBJS) $(TEMACS_DUMP_DEP) $(TEMACS_LIBS)
<<
＠＠ -1188,10 +1362,10 ＠＠ docfile ::
docfile :: $(DOC)
# We need to write the QUICK_BUILD stuff as-is (and not just have no
-# dependencies for DOC) because DOC needs TEMACS_OBJS as dependencies to
+# dependencies for DOC) because DOC needs TEMACS_DOC_SOURCES as dependencies to
# get $(**) right. The `touch' is needed because of the way nmake
# calculates dependencies; see comments in src/Makefile.in.in.
-$(DOC): $(BLDLIB_SRC)\make-docfile.exe $(BLDSRC)\NEEDTODUMP $(TEMACS_OBJS)
+$(DOC): $(BLDLIB_SRC)\make-docfile.exe $(BLDSRC)\NEEDTODUMP $(TEMACS_DOC_SOURCES)
!if $(QUICK_BUILD)
if not exist $(DOC) $(TEMACS_BATCH) -l $(LISP)\make-docfile.el -- -o $(DOC) -i $(SRCROOT)\site-packages ＠<<
$(**)
＠＠ -1421,7 +1595,7 ＠＠ $(INFODIR)\new-users-guide.info: $(NEW_U
info: makeinfo-test $(INFO_FILES)
#########################################################################
-## Testing-related targets ##
+## Testing, TAGS, install, clean, etc. ##
#########################################################################
########################### Automated tests
＠＠ -1502,18 +1676,24 ＠＠ mostlyclean:
-$(DEL) $(OUTDIR)\*.lib
-$(DEL) $(OUTDIR)\*.obj
-$(DEL) $(OUTDIR)\*.pdb
+ -$(DEL) $(OUTDIR)\*.idb
+ -$(DEL) $(OUTDIR)\*.ilk
-$(DEL) $(OUTDIR)\*.res
-$(DEL) $(OUTDIR)\*.sbr
-$(DEL) $(BLDSRC)\*.exe
-$(DEL) $(BLDSRC)\*.dmp
-$(DEL) $(BLDSRC)\*.map
-$(DEL) $(BLDSRC)\*.pdb
+ -$(DEL) $(BLDSRC)\*.idb
+ -$(DEL) $(BLDSRC)\*.ilk
-$(DEL) $(BLDSRC)\NEEDTODUMP
-$(DEL) $(BLDSRC)\dump-id.c
-$(DEL) $(SRC)\*.bsc
-$(DEL) $(BLDLIB_SRC)\*.exe
-$(DEL) $(BLDLIB_SRC)\*.obj
-$(DEL) $(BLDLIB_SRC)\*.pdb
+ -$(DEL) $(BLDLIB_SRC)\*.idb
+ -$(DEL) $(BLDLIB_SRC)\*.ilk
-$(DEL) $(BLDLIB_SRC)\*.res
versionclean:
- 1 participants
- 0 comments
CVS update by viteno xemacs-builds/viteno ...
18 years, 7 months
CVS Monitor
CVS Monitor
User: viteno
Date: 05/09/26 08:23:38
Modified: xemacs-builds/viteno package-index setup-packages.ini
Log:
Package database backup:
- ecrypto-0.20
- mail-lib-1.74
- pgg-1.06
- sasl-1.16
- sieve-1.18
- texinfo-1.30
Revision Changes Path
1.246 +36 -36 XEmacs/xemacs-builds/viteno/package-index
Index: package-index
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs-builds/viteno/package-index,v
retrieving revision 1.245
retrieving revision 1.246
diff -u -p -r1.245 -r1.246
--- package-index 2005/09/21 07:23:53 1.245
+++ package-index 2005/09/26 06:23:35 1.246
＠＠ -282,19 +282,19 ＠＠
(package-get-update-base-entry (quote
(pgg
(standards-version 1.1
- version "1.05"
+ version "1.06"
author-version "0.1"
- date "2004-09-16"
- build-date "2004-09-16"
+ date "2005-09-26"
+ build-date "2005-09-26"
maintainer "Simon Josefsson <simon(a)josefsson.org>"
distribution xemacs
priority low
category "standard"
dump nil
description "Emacs interface to various PGP implementations."
- filename "pgg-1.05-pkg.tar.gz"
- md5sum "5cfc3e806955aae30b0b9a906fa4daec"
- size 33364
+ filename "pgg-1.06-pkg.tar.gz"
+ md5sum "6cb9d38dfe23cdd8ff62291be5a8b03a"
+ size 33917
provides (pgg pgg-def pgg-parse pgg-gpg pgg-pgp pgg-pgp5)
requires (xemacs-base fsf-compat edebug ecrypto)
type regular
＠＠ -436,19 +436,19 ＠＠
(package-get-update-base-entry (quote
(ecrypto
(standards-version 1.1
- version "0.19"
+ version "0.20"
author-version "2.0"
- date "2004-11-30"
- build-date "2004-11-30"
+ date "2005-09-26"
+ build-date "2005-09-26"
maintainer "Simon Josefsson <simon(a)josefsson.org>"
distribution xemacs
priority low
category "standard"
dump nil
description "Crypto functionality in Emacs Lisp."
- filename "ecrypto-0.19-pkg.tar.gz"
- md5sum "48bcb5885e0102dff89ce39065a0ce07"
- size 76283
+ filename "ecrypto-0.20-pkg.tar.gz"
+ md5sum "eb94f451a4d279cd92f8f2bcb9b9b79b"
+ size 76257
provides (ascii-armor blowfish des hex-util md4 md5-dl md5-el md5 paranoid rander rc16 rijndael sha1-dl sha1-el sha1)
requires (xemacs-base)
type regular
＠＠ -480,19 +480,19 ＠＠
(package-get-update-base-entry (quote
(sasl
(standards-version 1.1
- version "1.15"
+ version "1.16"
author-version "1.14.4"
- date "2004-09-16"
- build-date "2004-09-16"
+ date "2005-09-26"
+ build-date "2005-09-26"
maintainer "Simon Josefsson <simon(a)josefsson.org>"
distribution xemacs
priority low
category "standard"
dump nil
description "Simple Authentication and Security Layer (SASL) library."
- filename "sasl-1.15-pkg.tar.gz"
- md5sum "db2bf9631d223f662c4b5d022b62e89c"
- size 27743
+ filename "sasl-1.16-pkg.tar.gz"
+ md5sum "2799ab3b97e3d3cd2fd5ca0385b04931"
+ size 27864
provides (hmac-def hmac-md5 hmac-sha1 ntlm sasl sasl-cram sasl-digest sasl-ntlm sasl-plain sasl-login sasl-anonymous)
requires (ecrypto)
type regular
＠＠ -823,19 +823,19 ＠＠ semantic-sas
(package-get-update-base-entry (quote
(mail-lib
(standards-version 1.1
- version "1.73"
+ version "1.74"
author-version "No-Upstream-Ver"
- date "2005-04-03"
- build-date "2005-04-03"
+ date "2005-09-26"
+ build-date "2005-09-26"
maintainer "Simon Josefsson <simon(a)josefsson.org>"
distribution xemacs
priority medium
category "standard"
dump nil
description "Fundamental lisp files for providing email support."
- filename "mail-lib-1.73-pkg.tar.gz"
- md5sum "e4e198b52c3f89a34777d51aee2ea126"
- size 210720
+ filename "mail-lib-1.74-pkg.tar.gz"
+ md5sum "5cee1009b7feb62887bd290b1a04dea9"
+ size 211172
provides (base64 browse-url-xemacs browse-url highlight-headers mail-abbrevs mail-extr mail-utils mailheader netrc pop3 reporter rfc2104 rfc822 rmail rmail-mini rmailout sendmail smtpmail starttls tls)
requires (eterm xemacs-base fsf-compat sh-script ecrypto)
type regular
＠＠ -955,19 +955,19 ＠＠ semantic-sas
(package-get-update-base-entry (quote
(sieve
(standards-version 1.1
- version "1.17"
+ version "1.18"
author-version "No-Upstream-Ver"
- date "2004-09-16"
- build-date "2004-09-16"
+ date "2005-09-26"
+ build-date "2005-09-26"
maintainer "Simon Josefsson <simon(a)josefsson.org>"
distribution xemacs
priority low
category "standard"
dump nil
description "Manage Sieve email filtering scripts."
- filename "sieve-1.17-pkg.tar.gz"
- md5sum "43824832e8bad443960793e5f54c2c7f"
- size 26892
+ filename "sieve-1.18-pkg.tar.gz"
+ md5sum "254bfbb81e4204ab8e57066baee8e78f"
+ size 27387
provides (sieve sieve-mode sieve-manage)
requires (xemacs-base mail-lib cc-mode sasl ecrypto sh-script)
type regular
＠＠ -1747,19 +1747,19 ＠＠ semantic-sas
(package-get-update-base-entry (quote
(texinfo
(standards-version 1.1
- version "1.29"
+ version "1.30"
author-version "No-Upstream-Ver"
- date "2005-03-26"
- build-date "2005-03-26"
+ date "2005-09-26"
+ build-date "2005-09-26"
maintainer "XEmacs Development Team <xemacs-beta(a)xemacs.org>"
distribution xemacs
priority high
category "standard"
dump nil
description "XEmacs TeXinfo support."
- filename "texinfo-1.29-pkg.tar.gz"
- md5sum "0844f60696d1bca22892efee687b45b4"
- size 145067
+ filename "texinfo-1.30-pkg.tar.gz"
+ md5sum "afa4dfa82a93fc7d4b85096621b8acdf"
+ size 145763
provides (makeinfo tex-mode texinfmt texinfo texnfo-tex texnfo-upd)
requires (text-modes xemacs-base)
type regular
1.234 +12 -12 XEmacs/xemacs-builds/viteno/setup-packages.ini
Index: setup-packages.ini
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs-builds/viteno/setup-packages.ini,v
retrieving revision 1.233
retrieving revision 1.234
diff -u -p -r1.233 -r1.234
--- setup-packages.ini 2005/09/21 07:23:53 1.233
+++ setup-packages.ini 2005/09/26 06:23:36 1.234
＠＠ -196,8 +196,8 ＠＠ version: 1.34
install: packages/reftex-1.34-pkg.tar.gz 352338
＠ texinfo
-version: 1.29
-install: packages/texinfo-1.29-pkg.tar.gz 145067
+version: 1.30
+install: packages/texinfo-1.30-pkg.tar.gz 145763
＠ textools
version: 1.15
＠＠ -312,8 +312,8 ＠＠ version: 1.10
install: packages/clearcase-1.10-pkg.tar.gz 105865
＠ sieve
-version: 1.17
-install: packages/sieve-1.17-pkg.tar.gz 26892
+version: 1.18
+install: packages/sieve-1.18-pkg.tar.gz 27387
＠ ps-print
version: 1.11
＠＠ -332,8 +332,8 ＠＠ version: 1.48
install: packages/jde-1.48-pkg.tar.gz 2404962
＠ mail-lib
-version: 1.73
-install: packages/mail-lib-1.73-pkg.tar.gz 210720
+version: 1.74
+install: packages/mail-lib-1.74-pkg.tar.gz 211172
＠ pcl-cvs
version: 1.66
＠＠ -380,16 +380,16 ＠＠ version: 0.12
install: packages/sml-mode-0.12-pkg.tar.gz 82366
＠ sasl
-version: 1.15
-install: packages/sasl-1.15-pkg.tar.gz 27743
+version: 1.16
+install: packages/sasl-1.16-pkg.tar.gz 27864
＠ ocaml
version: 0.05
install: packages/ocaml-0.05-pkg.tar.gz 64887
＠ ecrypto
-version: 0.19
-install: packages/ecrypto-0.19-pkg.tar.gz 76283
+version: 0.20
+install: packages/ecrypto-0.20-pkg.tar.gz 76257
＠ docbookide
version: 0.07
＠＠ -416,8 +416,8 ＠＠ version: 1.08
install: packages/perl-modes-1.08-pkg.tar.gz 165731
＠ pgg
-version: 1.05
-install: packages/pgg-1.05-pkg.tar.gz 33364
+version: 1.06
+install: packages/pgg-1.06-pkg.tar.gz 33917
＠ ecb
version: 1.22
- 1 participants
- 0 comments