Mercurial > hg > xemacs-beta
annotate man/lispref/back.texi @ 4903:70089046adef
fix compile problems in intl-encap* under VS6
-------------------- ChangeLog entries follow: --------------------
lib-src/ChangeLog addition:
2010-01-30 Ben Wing <ben@xemacs.org>
* make-mswin-unicode.pl:
Make it possible to specify an overridden prototype in cases where
either Cygwin or Visual Studio has errors in their headers that
can be corrected by falling back to a less qualified type (typically
without const).
src/ChangeLog addition:
2010-01-30 Ben Wing <ben@xemacs.org>
* intl-auto-encap-win32.c:
* intl-auto-encap-win32.c (qxeExtractAssociatedIcon):
* intl-auto-encap-win32.c (qxeExtractIconEx):
* intl-auto-encap-win32.c (qxeCreateMDIWindow):
* intl-auto-encap-win32.c (qxeCreateWindowStation):
* intl-auto-encap-win32.c (qxeDdeCreateStringHandle):
* intl-auto-encap-win32.c (qxeAbortSystemShutdown):
* intl-auto-encap-win32.c (qxeRegConnectRegistry):
* intl-auto-encap-win32.c (qxeGetICMProfile):
* intl-auto-encap-win32.h:
Rebuild.
* intl-encap-win32.c:
* intl-encap-win32.c (qxeUpdateICMRegKey):
Delete manual definitions of functions with former errors in
Cygwin headers but no longer. Use "override" with some functions
where Cygwin or VS6 accidentally omits a const declaration or
includes an extra one. Use "no" on SendMessageTimeout, which
has an error in the VS6 prototype (you could manually fix this
with an ifdef to split the Cygwin vs. VS6 calls, if we ever
actually used this function).
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Sat, 30 Jan 2010 20:34:23 -0600 |
| parents | 3ecd8885ac67 |
| children |
| rev | line source |
|---|---|
| 428 | 1 \input /home/gd/gnu/doc/texinfo.tex @c -*-texinfo-*- |
| 2 @c %**start of header | |
| 3 @setfilename ../../info/back-cover | |
| 4 @settitle XEmacs Lisp Reference Manual | |
| 5 @c %**end of header | |
| 6 . | |
| 7 @sp 7 | |
| 8 @center @titlefont {XEmacs Lisp} | |
| 9 @sp 1 | |
| 10 | |
| 11 @quotation | |
| 12 Most of the XEmacs text editor is written in the programming | |
| 13 language called XEmacs Lisp. You can write new code in XEmacs Lisp and | |
| 14 install it as an extension to the editor. However, XEmacs Lisp is more | |
| 15 than a mere ``extension language''; it is a full computer programming | |
| 16 language in its own right. You can use it as you would any other | |
| 17 programming language. | |
| 18 | |
| 19 Because XEmacs Lisp is designed for use in an editor, it has special | |
| 20 features for scanning and parsing text as well as features for handling | |
| 21 files, buffers, displays, subprocesses, and so on. XEmacs Lisp is | |
| 22 closely integrated with the editing facilities; thus, editing commands | |
| 23 are functions that can also conveniently be called from Lisp programs, | |
| 24 and parameters for customization are ordinary Lisp variables. | |
| 25 | |
| 26 This manual describes XEmacs Lisp. Generally speaking, the earlier | |
| 27 chapters describe features of XEmacs Lisp that have counterparts in | |
| 28 many programming languages, and later chapters describe features that | |
| 29 are peculiar to XEmacs Lisp or relate specifically to editing. | |
| 30 @end quotation | |
| 31 | |
| 32 @hfil | |
| 33 @bye |