AW: AW: AW: Bug in function window-list
21 years, 10 months
Berndl, Klaus
Berndl, Klaus
Klaus> Hmm, IMHO a somehow "contructed" argument and disadvantage.
>Nonsense.
Dito!
Klaus> "`next-window' is a built-in function
Klaus> (next-window &optional WINDOW MINIBUF WHICH-FRAMES WHICH-DEVICES)
Klaus> Documentation:
Klaus> Return the next window after WINDOW in the canonical ordering of
Klaus> windows. If omitted, WINDOW defaults to the selected window. ..."
Klaus> You see the word "canonical"??!!
>Yes, I do. You see that word somewhere in the documentation or name for
>`window-list'?
No, unfortunatelly not ;-)
Klaus> If i understand you right then you say it is best to make no
Klaus> specification for API-functions on which programmers can rely
Klaus> because maybe someone wants to change it later and then all
Klaus> already existing code fails or has to be rewritten, right?
>No, you didn't understand me right. I didn't say anything of the sort.
>`window-list' already has a specification, and there's no good reason to
>change it, because there's no existing code that assumes a different
>specification from it.
This argumentaion now is pure nonsense
>If you want a function with a different behavior,
>by all means write it and give it a name indicative of what it does.
Ok, i'm not keen wasting valuable time....forget it, i will write my own
(maybe - not probably i must admit - 123534 other people have to do it too ;-)
- 2 participants
- 1 comments
AW: AW: Bug in function window-list
21 years, 10 months
Berndl, Klaus
Berndl, Klaus
>>>>> "Klaus" == Klaus Berndl <Berndl> writes:
Klaus> No, here i do not agree with you and Stephen. Reasons:
Klaus> - Changing current `window-list' so it always returns a somehow canonical
Klaus> ordered list is very simple and has really no disadvantage (at least as fas
Klaus> i can see)
>Yes, it has, namely that people tend to then rely on that canonical
>order, even though it's not part of the natural specification---this
>makes it impossible to change later, should it become opportune to do
>so. (If it's one thing XEmacs history has taught us, then that's it,
>thank goodness.)
Hmm, IMHO a somehow "contructed" argument and disadvantage. See `next-window'
and the documentation (just the first few lines):
"`next-window' is a built-in function
(next-window &optional WINDOW MINIBUF WHICH-FRAMES WHICH-DEVICES)
Documentation:
Return the next window after WINDOW in the canonical ordering of windows.
If omitted, WINDOW defaults to the selected window.
..."
You see the word "canonical"??!! I really can not imagine what good reason should
exist (or even in any future come up) which would make sense and necessary to
change the order from the canonical one to any other.
If i understand you right then you say it is best to make no specification
for API-functions on which programmers can rely because maybe someone wants
to change it later and then all already existing code fails or has to be
rewritten, right?
Yes, of course this is true for inhertitance-hierarchies in OO-programming etc..
and some other design issues too but really not for defining a senseful order of
a result list especially if the same order is already there (and also documented)
In other API-functions e.g. in `next-window'. Then i'm wondering why you XEmacs-
people have defined the order of `next-window', because now it is impossible
to change the order, `next-window' will select the next window - which is IMHO good,
that this is impossible!!
Sometimes concret and clear specifications of API-functions are really helpful and
necessary especially for stable applications this is what years of designing and
programming of big applications has taught me, thang goodness.
Back to window-list: Cause of really no order-specification of this function i have
to write my own window-list function if i want this canonical order which is IMHO
complete waste of time and code because there is already one. At least a further
optional argument "order-canonical" could be added so i can apply this order to the
list if i want (without programming the whole stuff again).
Compare it with SQL: Here you have also no order specification but you CAN apply
someone if you NEED any!
Ok, such an additional optional parameter for `window-list' would satisfy both of
us, you because you can change the default order of window-list whenever you
want and me, because i have to program the whole function again though there is
already one.
Thoughts?
Ciao,
Klaus
- 2 participants
- 1 comments
AW: Bug in function window-list
21 years, 10 months
Berndl, Klaus
Berndl, Klaus
>>>>> "Stephen" == Stephen J Turnbull <stephen(a)xemacs.org> writes:
>>>>> "Klaus" == Klaus Berndl <Berndl> writes:
Klaus> If i understand the function window-list right it should return a
Klaus> window-list in that order `other-window', `walk-windows' or
Klaus> `next-window' would return/ Move?! Is my understanding right?
Stephen> The documentation says "a list." No promise about order
Stephen> (except that the specified window comes first), no mention of
Stephen> the other functions.
>Stephen's right.
Yes, indeed, i admit
Klaus> If not then i would vote for that order!
Stephen> Why? It seems to me that if you have an application that wants
Stephen> to walk through the windows in `walk-windows' order it should
Stephen> use `walk-windows'. Keeping a list around and depending on its
Stephen> order to be correct later is just asking for trouble.
Stephen> In any case, if you're going to make this change you need to
Stephen> fix the documentation of window-list and walk-windows at least
Stephen> to specify that they give the same order, and maybe what that
Stephen> order is.
>I don't think this is the right approach for a function called only
>`window-list.' If you need this kind of functionality, you should
>simply add a new function that's called `window-list-in-next-order.'
>Not that I think *this* would be particularly useful: If you need to
>traverse the windows according to some order, it's probably a better
>idea to do so explicitly.
No, here i do not agree with you and Stephen. Reasons:
- Changing current `window-list' so it always returns a somehow canonical
ordered list is very simple and has really no disadvantage (at least as fas
i can see)
- A window list is not only for walking through the windows of this list (for
this task `walk-windows' is indeed the right and better function. But sometimes
i want to get the current-window-list of a frame, save it and use it later (maybe
comparison or something else). I think you can not progose for which jobs a
programmer could use the result of `window-list' and maybe some of these jobs could
profite from the fact that the ordering of the result list is known. Currently it
is undefined (i mean the order of the list is always the same but the docu does
not say anything about the order!)
- Just that i can rely, that `other-window', `next-window', walk-windows'
and `window-list' always operate/return (on) the windows in the same order is IMHO
a valuable fact even it is just for consistency.
I really not understand, why my suggestion to make `window-list' returning a defined
order (and then why not using the "canonical" order of some other window-functions?!)
runs against you, because the change is very simple and has really no side-effects for
existing code (because existing code is not allowed to be based on any order of the
result list, because there is no defined order like Stephen says right) and also
has no other disadvantages (or can you tell me any?).
Ciao,
Klaus
- 2 participants
- 1 comments
Re: ClearCase mode
21 years, 10 months
Michael Diers
Michael Diers
Adrian Aichner <adrian(a)xemacs.org> schrieb am 14.01.03 09:10:12:
> >>>>> "Peter" == Peter R Torpman <einpton(a)ks.ericsson.se> writes:
[...]
> Peter> I was wondering if it is possible to add a default header
> Peter> to the checkin comment. (In vc-cc it is possible to set a
> Peter> default-comment variable so that there is a skeleton for
> Peter> users to fill in when checking in files)
[...]
> Michael, could you please take a look at this?
The mechanism for initializing a comment buffer with a user-provided text is already there, c.f. clearcase-comment-start-entry function.
Looks feasible. I'll try to come up with something, please stand by.
--
Michael
______________________________________________________________________________
Testsieg! Laut Computer-Bild ist WEB.DE FreeMail der sicherste
E-Mail Anbieter Deutschlands. Mehr: http://freemail.web.de/features/?mc=021131
- 1 participants
- 0 comments
Bug in function window-list
21 years, 10 months
Berndl, Klaus
Berndl, Klaus
If i understand the function window-list right it should return a window-list
in that order `other-window', `walk-windows' or `next-window' would return/
Move?! Is my understanding right? If not then i would vote for that order!
Ok, then current window-list function is buggy, because it returns the wrong
order.
This is function defined in emacs-version:
"21.4 (patch 10) \"Military Intelligence (RC5 Windows)\" XEmacs Lucid"
(defun window-list (&optional frame minibuf window)
"Return a list of windows on FRAME, beginning with WINDOW.
FRAME and WINDOW default to the selected ones.
Optional second arg MINIBUF t means count the minibuffer window
even if not active. If MINIBUF is neither t nor nil it means
not to count the minibuffer even if it is active."
(setq window (or window (selected-window))
frame (or frame (selected-frame)))
(if (not (eq (window-frame window) frame))
(error "Window must be on frame."))
(let ((current-frame (selected-frame))
list)
(unwind-protect
(save-window-excursion
(select-frame frame)
(walk-windows
(function (lambda (cur-window)
(if (not (eq window cur-window))
(setq list (cons cur-window list)))))
minibuf)
(setq list (cons window list)))
(select-frame current-frame)))))
This should be (IMHO):
(defun window-list (&optional frame minibuf window)
"Return a list of windows on FRAME, beginning with WINDOW.
FRAME and WINDOW default to the selected ones.
Optional second arg MINIBUF t means count the minibuffer window
even if not active. If MINIBUF is neither t nor nil it means
not to count the minibuffer even if it is active."
(setq window (or window (selected-window))
frame (or frame (selected-frame)))
(if (not (eq (window-frame window) frame))
(error "Window must be on frame."))
(let ((current-frame (selected-frame))
list)
(unwind-protect
(save-window-excursion
(select-frame frame)
(walk-windows
(function (lambda (cur-window)
(if (not (eq window cur-window))
(setq list (cons cur-window list)))))
minibuf)
;; This is needed to get the right windows-order, i.e. the same
;; order of windows than `walk-windows' walks through!
(setq list (nreverse list))
(setq list (cons window list)))
(select-frame current-frame)))))
Ciao,
Klaus
- 3 participants
- 2 comments
[Failure] XEmacs 21.5-b10 "burdock" (+CVS-20030114) i586-pc-win32
21 years, 10 months
Adrian Aichner
Adrian Aichner
Still failing for native windows build!
Adrian
> XEmacs Build Report generated by emacs-version
> 21.4 (patch 11) "Native Windows TTY Support (Windows)" XEmacs Lucid
> with system-configuration
> i586-pc-win32
> follows:
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\Installation:
> (Output from most recent run of ./configure)
OS version:
Microsoft Windows 2000 [Version 5.00.2195]
OS: Windows_NT
XEmacs 21.5-b10 "burdock" (+CVS-20030114) configured for `i586-pc-win32'.
Building XEmacs using "NMAKE".
Building XEmacs using make flags " ".
Building XEmacs in "c:\\Hacking\\cvs.xemacs.org\\XEmacs\\xemacs-21.5\\nt".
Using compiler "cl -nologo -W3 -DSTRICT -ZI -Od -MDd".
Compiling as C++.
Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.5-b10".
Package path is "~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\mule-packages;c:\\Program Files\\XEmacs\\xemacs-packages".
Compiling in support for Microsoft Windows native GUI.
Compiling in international (MULE) support.
Compiling in support for XPM images.
Compiling in support for GIF images.
Compiling in support for PNG images.
Compiling in support for TIFF images.
Compiling in support for JPEG images.
Compiling in support for X-Face message headers.
Compiling in support for GZIP compression/decompression.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Using portable dumper.
Using system malloc.
Using DLL version of C runtime library.
Compiling in extra internal error-checking.
WARNING: ---------------------------------------------------------
WARNING: Compiling in support for runtime error checking.
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
Compiling in debugging support (no slowdown).
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\xemacs-21.5-cvs-update.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* "
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\
Compilation started at Wed Jan 15 07:32:26 2003 +0100 (W. Europe Standard Time)
? nt/xemacs-21.5-make-distclean-error.err
P version.sh
M etc/package-index.LATEST.gpg
M info/dir
rcsmerge: warning: conflicts during merge
C lisp/ChangeLog
M lisp/package-get.el
P lisp/window-xemacs.el
M man/Makefile
M man/xemacs/xemacs.texi
M nt/xemacs.mak
P src/ChangeLog
P src/depend
P src/window.c
cvs server: Updating tests
cvs server: Updating tests/DLL
Compilation finished at Wed Jan 15 07:35:07
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\xemacs-21.5-make-install.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* "
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\
nmake /f xemacs.mak install
Compilation started at Wed Jan 15 07:54:50 2003 +0100 (W. Europe Standard Time)
WARNING: Compiling without dependency information.
Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.5-b10".
Compiling in extra internal error-checking.
WARNING: ---------------------------------------------------------
WARNING: Compiling in support for runtime error checking.
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
1 file(s) copied.
1 File(s) copied
1 File(s) copied
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/make-dump-id.ilk"; linking nonincrementally
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/etags.ilk"; linking nonincrementally
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/hexl.ilk"; linking nonincrementally
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/i.ilk"; linking nonincrementally
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/winclient.ilk"; linking nonincrementally
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/make-docfile.ilk"; linking nonincrementally
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/mmencode.ilk"; linking nonincrementally
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/movemail.ilk"; linking nonincrementally
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/sorted-doc.ilk"; linking nonincrementally
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/wakeup.ilk"; linking nonincrementally
LINK: warning LNK4076: invalid incremental status file "c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5\nt\..\lib-src/minitar.ilk"; linking nonincrementally
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\text.h(42) : warning C4273: 'strlwr' : inconsistent dll linkage. dllexport assumed.
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\text.h(45) : warning C4273: 'strupr' : inconsistent dll linkage. dllexport assumed.
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\text.h(42) : warning C4273: 'strlwr' : inconsistent dll linkage. dllexport assumed.
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\text.h(45) : warning C4273: 'strupr' : inconsistent dll linkage. dllexport assumed.
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\text.h(42) : warning C4273: 'strlwr' : inconsistent dll linkage. dllexport assumed.
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\text.h(45) : warning C4273: 'strupr' : inconsistent dll linkage. dllexport assumed.
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\text.h(42) : warning C4273: 'strlwr' : inconsistent dll linkage. dllexport assumed.
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\text.h(45) : warning C4273: 'strupr' : inconsistent dll linkage. dllexport assumed.
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\text.h(42) : warning C4273: 'strlwr' : inconsistent dll linkage. dllexport assumed.
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\text.h(45) : warning C4273: 'strupr' : inconsistent dll linkage. dllexport assumed.
c:\hacking\cvs.xemacs.org\xemacs\xemacs-21.5\src\glyphs-msw.c(1657) : error C2660: 'UnCompAll' : function does not take 1 parameters
NMAKE: fatal error U1077: 'cl' : return code '0x2'
Compilation exited abnormally with code 2 at Wed Jan 15 07:56:05
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
- 1 participants
- 0 comments
inexplicable exit
21 years, 10 months
Anthony Paris
Anthony Paris
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
Please describe as succinctly as possible:
- What happened.
- What you thought should have happened.
- Precisely what you were doing at the time.
Please also include any C or lisp back-traces that you may have.
================================================================
Dear Bug Team!
Ever since i began using xemacs on RedHat 8.0, the application will
suddenly crash with no warning as i open a file, or switch between
buffers.
PLEASE ADVISE.
================================================================
System Info to help track down your bug:
---------------------------------------
uname -a: Linux astest 2.4.9-e.8smp #1 SMP Fri Jul 19 15:38:30 EDT 2002 i686 unknown unknown GNU/Linux
./configure 'i386-redhat-linux-gnu' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--datadir=/usr/share' '--libdir=/usr/lib' '--mandir=/usr/share/man/man1' '--infodir=/usr/share/info' '--with-gpm=no' '--with-sound=native' '--with-pop' '--mail-locking=lockf' '--with-clash-detection' '--debug=no' '--error-checking=none' '--with-mule=yes' '--with-database=berkdb' '--with-ldap=yes' '--with-hesiod=no' '--with-canna=yes' '--with-wnn=yes' '--with-widgets=motif' '--with-menubars=lucid' '--with-scrollbars=lucid' '--with-dialogs=motif' '--with-xim=xlib' '--with-msw=no' '--with-xfs=yes' '--pdump'
XEmacs 21.4.8 "Honest Recruiter" configured for `i386-redhat-linux'.
Compilation / Installation:
Source code location: /usr/src/build/141167-i386/BUILD/xemacs-21.4.8
Installation prefix: /usr
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -O2 -march=i386 -mcpu=i686
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Using Lucid menubars.
Using Lucid scrollbars.
Using Motif dialog boxes.
Using Motif native widgets.
TTY:
Compiling in support for ncurses.
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Sound:
Compiling in support for sound (native).
Databases:
Compiling in support for Berkeley database.
Compiling in support for LDAP.
Compiling in support for PostgreSQL.
- Using PostgreSQL header file: libpq-fe.h
- Using PostgreSQL V7 bindings.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
- Using XFontSet to provide bilingual menubar.
Compiling in support for Canna on Mule.
Compiling in support for the WNN input method on Mule.
Mail:
Compiling in support for POP mail retrieval.
Compiling in support for "lockf" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new portable dumper.
Load-Path Lisp Shadows:
----------------------
(/usr/lib/xemacs/xemacs-packages/lisp/apel/alist
/usr/share/xemacs-21.4.8/lisp/alist)
Installed XEmacs Packages:
-------------------------
((zenirc:version 1.13 :type regular)
(xslt-process :version 1.1 :type regular)
(xslide :version 1.02 :type regular)
(xemacs-devel :version 1.47 :type single-file)
(xemacs-base :version 1.66 :type regular)
(w3 :version 1.25 :type regular)
(vm :version 7.07 :type regular)
(viper :version 1.34 :type regular)
(view-process :version 1.11 :type regular)
(vhdl :version 1.15 :type regular)
(vc-cc :version 1.21 :type regular)
(vc :version 1.33 :type regular)
(tramp :version 1.05 :type regular)
(tpu :version 1.12 :type regular)
(tooltalk :version 1.13 :type regular)
(tm :version 1.34 :type regular)
(time :version 1.11 :type regular)
(textools :version 1.12 :type regular)
(text-modes :version 1.48 :type single-file)
(texinfo :version 1.2 :type regular)
(supercite :version 1.19 :type regular)
(strokes :version 1.08 :type regular)
(speedbar :version 1.23 :type regular)
(sounds-wav :version 1.1 :type regular)
(sounds-au :version 1.1 :type regular)
(slider :version 1.13 :type regular)
(sieve :version 1.07 :type regular)
(sh-script :version 1.15 :type regular)
(sgml :version 1.08 :type regular)
(semantic :version 1.12 :type regular)
(scheme :version 1.11 :type regular)
(rmail :version 1.13 :type regular)
(reftex :version 1.25 :type regular)
(psgml :version 1.28 :type regular)
(ps-print :version 1.04 :type regular)
(prog-modes
:version
1
.6
:type
single-file)
(pcomplete :version 1.01 :type regular)
(pcl-cvs :version 1.63 :type regular)
(pc :version 1.25 :type single-file)
(os-utils :version 1.28 :type single-file)
(net-utils :version 1.27 :type single-file)
(mmm-mode :version 1.0 :type regular)
(misc-games :version 1.15 :type single-file)
(mine :version 1.14 :type regular)
(mh-e :version 1.14 :type regular)
(mailcrypt :version 2.11 :type regular)
(mail-lib :version 1.47 :type regular)
(jde :version 1.35 :type regular)
(ispell :version 1.24 :type regular)
(ilisp :version 1.27 :type regular)
(igrep :version 1.08 :type regular)
(idlwave :version 1.25 :type regular)
(ibuffer :version 1.08 :type regular)
(hm--html-menus :version 1.18 :type regular)
(haskell-mode :version 1.04 :type regular)
(gnus :version 1.62 :type regular)
(gnats :version 1.15 :type regular)
(games :version 1.13 :type regular)
(fsf-compat :version 1.11 :type single-file)
(frame-icon :version 1.09 :type regular)
(forms :version 1.14 :type regular)
(footnote :version 1.15 :type regular)
(eudc :version 1.36 :type regular)
(eterm :version 1.13 :type regular)
(ess :version 1.02 :type regular)
(eshell :version 1.03 :type regular)
(emerge :version 1.09 :type regular)
(elib :version 1.1 :type single-file)
(eieio :version 1.02 :type regular)
(efs :version 1.29 :type regular)
(edt :version 1.12 :type regular)
(edit-utils :version 1.89 :type single-file)
(ediff :version 1.41 :type regular)
(edebug :version 1.14 :type regular)
(dired :version 1.12 :type regular)
(dictionary :version 1.11 :type regular)
(debug :version 1.15 :type regular)
(crisp :version 1.12 :type regular)
(cookie :version 1.14 :type regular)
(clearcase :version 1.04 :type regular)
(cc-mode :version 1.28 :type regular)
(calendar :version 1.18 :type regular)
(calc :version 1.23 :type regular)
(c-support :version 1.16 :type single-file)
(build :version 1.06 :type regular)
(bbdb :version 1.21 :type regular)
(auctex :version 1.32 :type regular)
(ada :version 1.1 :type regular)
(mule-ucs :version 1.04 :type regular)
(mule-base :version 1.42 :type regular)
(lookup :version 1.12 :type regular)
(locale :version 1.18 :type regular)
(leim :version 1.18 :type regular)
(latin-unity :version 1.05 :type regular)
(egg-its :version 1.26 :type regular)
(edict :version 1.13 :type regular))
Features:
--------
(mail-abbrevs xemacsbug shadow sendmail rfc822 wid-edit efs-cu env
dired-faces dired-xemacs dired font disp-table blink-cursor
pending-del paren blink-paren time cus-face shell comint ring vc-hooks
desktop un-define mule-uni zenirc-autoloads xslt-process-autoloads
xslide-autoloads xemacs-devel-autoloads xemacs-base-autoloads
w3-autoloads vm-autoloads viper-autoloads view-process-autoloads
vhdl-autoloads vc-cc-autoloads vc-autoloads tramp-autoloads
tpu-autoloads tooltalk-autoloads tm-autoloads time-autoloads
textools-autoloads text-modes-autoloads texinfo-autoloads
supercite-autoloads strokes-autoloads speedbar-autoloads
sounds-wav-autoloads sounds-au-autoloads slider-autoloads
sieve-autoloads sh-script-autoloads sgml-autoloads semantic-autoloads
scheme-autoloads rmail-autoloads reftex-autoloads psgml-autoloads
ps-print-autoloads prog-modes-autoloads pcomplete-autoloads
pcl-cvs-autoloads pc-autoloads os-utils-autoloads net-utils-autoloads
mmm-mode-autoloads misc-games-autoloads mine-autoloads mh-e-autoloads
mailcrypt-autoloads mail-lib-autoloads jde-autoloads ispell-autoloads
ilisp-autoloads igrep-autoloads idlwave-autoloads ibuffer-autoloads
hm--html-menus-autoloads haskell-mode-autoloads gnus-autoloads
gnats-autoloads games-autoloads fsf-compat-autoloads
frame-icon-autoloads forms-autoloads footnote-autoloads eudc-autoloads
eterm-autoloads ess-autoloads eshell-autoloads emerge-autoloads
elib-autoloads eieio-autoloads efs-autoloads edt-autoloads
edit-utils-autoloads ediff-autoloads edebug-autoloads dired-autoloads
dictionary-autoloads debug-autoloads crisp-autoloads cookie-autoloads
clearcase-autoloads cc-mode-autoloads calendar-autoloads
calc-autoloads c-support-autoloads build-autoloads bbdb-autoloads
auctex-autoloads apel-autoloads ada-autoloads mule-ucs-autoloads
mule-base-autoloads lookup-autoloads locale-autoloads leim-autoloads
latin-unity-autoloads egg-its-autoloads edict-autoloads lisp-autoloads
loadhist auto-show fontl-hooks x-iso8859-1 canna-leim slovenian czech
romanian ccl mule-help code-cmds gutter-items menubar-items x-menubar
mode-motion mouse itimer auto-save lisp-mode easymenu iso8859-1 page
buff-menu lib-complete cus-file derived frame text-props obsolete
cus-start custom widget cl-extra mini-cl cl cl-19 packages backquote
very-early-lisp postgresqlv7 postgresql CANNA file-coding wnn mule
lucid-scrollbars cut-buffer lucid-menubars motif-dialogs x
c-balloon-help tty-frames tty toolbar native-sound scrollbar
unix-processes multicast network-streams subprocesses modules
menu-accelerator-support menubar berkeley-db md5 xemacs xim gutter
tiff png gif jpeg xpm xbm lisp-float-type linux dialog devices
window-system base64)
Recent keystrokes:
-----------------
misc-user button2 button2up C-x k RET C-x k RET misc-user
misc-user misc-user misc-user misc-user misc-user misc-user
misc-user misc-user misc-user misc-user misc-user misc-user
misc-user misc-user button1 button1up button1 button1up
button1 button1up misc-user
Recent messages (most recent first):
-----------------------------------
Loading xemacsbug...done
Loading xemacsbug...
Loading about...done
Loading about...
Loading efs-cu...done
Loading efs-cu...
Reading directory /home/aparis/.saves-*...done
Reading directory /home/aparis/.saves-*...
Loading env...done
Loading env...
Loading dired...done
Loading dired-mule...done
Loading dired-mule...
Loading dired...
Loading font...done
Loading font...
Loading blink-cursor...done
Loading blink-cursor...
Loading pending-del...done
Loading pending-del...
- 2 participants
- 1 comments
Ah, the joys of a new compiler
21 years, 10 months
Vin Shelton
Vin Shelton
I downloaded the Intel C/C++ compiler for x86 architectures and have
been running with it in order to add some spice to my life. I have
discovered some interesting things:
1. By default, 21.4 will only build with this compiler if I
configure with pdump. If I try to configure --pdump=no, I get an
error because -lgcc is not a valid library. This aborts
configure because sizeof(short) = 0.
2. If I edit src/s/linux.h and #define ORDINARY_LINK, I can
configure and build successfully. However, upon first run, I get
an error which looks suspiciously like the HANNIBAL LECTOR error:
gdb /opt/build/xemacs-21.4-2003-01-09-1600-icc3/src/xemacs core
then type `where' at the debugger prompt. No GDB on your system? You may
have DBX, or XDB, or SDB. (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited'
in case of future recurrance of the crash.
Lisp backtrace follows:
# bind (frame-being-created)
make-frame(nil #<x-device on ":0.0" 0x1d64>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (condition-case ... . ((t (byte-code " oÂ" ... 1))))
# bind (error-data)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
zsh: segmentation fault (core dumped) src/xemacs
3. In fact, it was our old friend Hannibal, because, when I ran
configure with LDFLAGS='-z nocombreloc', I could successfully run
my shiny new XEmacs.
4. While building (either with or without pdump, I noticed a number
of warnings:
/opt/src/xemacs-21.4-2003-01-09-1600/src/emacs.c(2915): warning #556: a value of type "void (*)(void *)" cannot be assigned to an entity of type "void (*)(void *, const void *)"
__free_hook =
^
/opt/src/xemacs-21.4-2003-01-09-1600/src/emacs.c(2989): warning #556: a value of type "void (*)(void *)" cannot be assigned to an entity of type "void (*)(void *, const void *)"
__free_hook =
^
/opt/src/xemacs-21.4-2003-01-09-1600/src/process-unix.c(236): warning #266: function declared implicitly
master_fd = getpt ();
^
/opt/src/xemacs-21.4-2003-01-09-1600/src/process-unix.c(292): warning #266: function declared implicitly
slave_name = ptsname (master_fd);
^
/opt/src/xemacs-21.4-2003-01-09-1600/src/process-unix.c(292): warning #556: a value of type "int" cannot be assigned to an entity of type "const char *"
slave_name = ptsname (master_fd);
^
/opt/src/xemacs-21.4-2003-01-09-1600/src/process-unix.c(321): warning #266: function declared implicitly
grantpt (master_fd);
^
/opt/src/xemacs-21.4-2003-01-09-1600/src/process-unix.c(335): warning #266: function declared implicitly
unlockpt (master_fd);
^
/opt/src/xemacs-21.4-2003-01-09-1600/src/glyphs.c(1992): warning #186: pointless comparison of unsigned integer with zero
assert (XIMAGE_INSTANCE_YOFFSET (image_instance) >= 0
^
/opt/src/xemacs-21.4-2003-01-09-1600/src/glyphs.c(1992): warning #186: pointless comparison of unsigned integer with zero
assert (XIMAGE_INSTANCE_YOFFSET (image_instance) >= 0
^
/usr/local/intel/compiler70/ia32/bin/icc -c -O3 -mcpu=pentiumpro -tpp6 -march=pentiumiii -axK -ip -Demacs -I. -DHAVE_CONFIG_H -I/usr/local/include -I/usr/X11R6/include /opt/src/xemacs-21.4-2003-01-09-1600/src/glyphs-eimage.c
/opt/src/xemacs-21.4-2003-01-09-1600/src/glyphs-eimage.c(1286): warning #186: pointless comparison of unsigned integer with zero
for (i = height - 1; i >= 0; i--)
^
/opt/src/xemacs-21.4-2003-01-09-1600/src/redisplay-x.c(980): warning #167: argument of type "long *" is incompatible with parameter of type "unsigned long *"
if (!XGetFontProperty (xfont, XA_UNDERLINE_POSITION, &upos))
^
/opt/src/xemacs-21.4-2003-01-09-1600/src/redisplay-x.c(982): warning #167: argument of type "long *" is incompatible with parameter of type "unsigned long *"
if (!XGetFontProperty (xfont, XA_UNDERLINE_THICKNESS, &uthick))
I hope someone finds all this interesting.
- Vin
- 6 participants
- 7 comments
RE: Re: union type is EVIL EVIL EVIL
21 years, 10 months
Ben Wing
Ben Wing
it's useful to compile with union type to catch problems, as stephen mentions, but it has such a propensity to create random crashes due to compiler bugs, which often appear like xemacs problems, that people who don't have a good idea of its uses should not use it.
it's similar with c++ but there are other advantages ... for example my recently-introduced bad-gcpro-catching code. note also that it's possible to catch insufficient gcproing using c++, but somewhat difficult. i put in a comment to this effect in my kkcc patch.
ben
------- Original Message -------
On
Tue, 17 Dec 2002 22:35:11 +0900 Stephen J. Turnbull?wrote:
>>>>> "Ville" == Ville Skytt <Ville> writes:
Ville> On Tue, 2002-12-17 at 04:20, Ben Wing wrote:
>> stephen -- while you're in the process of modifying PROBLEMS,
>> please add an entry about union type and its propensity to
>> cause crashes. here's some text that should get you started:
Ville> [...]
Ville> Uh, --use-union-type has been many times suggested on
Ville> xemacs-beta as a way to prevent crashes in something
Ville> related to aggressive compiler
Ville> What's correct?
To some extent, both. Sometimes you lose, and other times you lose
big. There's nothing we can do about compiler bugs except write them
up in PROBLEMS and code defensively. There are any number of
temporaries in XEmacs notated with "Compiler XYZ chokes without this."
This is more of the same. :-(
To me it's a pragmatic issue (if anything, union type is more
"righteous" than the int Lisp_Object type). GCC (and now VC++) has
historically had problems with unions.[1] OTOH unions have historically
been good at smoking out "if (lisp_object) ..." constructs and the
like, and to some extent aliasing issues.
I think if you look, you'll find that (a) it's often been me
recommending union type[2] and (b) --use-union-type typically doesn't
solve any problems. If better diagnosis tools are now available, then
there may be reason to avoid union type.
Footnotes:
[1] They've also had problems with std C++ ... but I doubt Ben would
argue that is EVIL EVIL EVIL ;-)
[2] Ie, you're really only citing one opinion.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
- 8 participants
- 17 comments
21.5.10 modules build failure on Solaris 8
21 years, 10 months
Raymond Toy
Raymond Toy
XEmacs built from a full tarball on Solaris 8 with gcc 3.1. I
configured as usual with:
../configure --verbose --extra-verbose --with-mule --with-pop
--with-sound=noesd --prefix=/apps/public/XEmacs/21.5
--bindir=/apps/public/XEmacs/21.5/bin/solaris2.8 --with-workshop
--with-dialogs=motif --with-widgets=motif
'--site-includes=/apps/public/solaris2.8/usr/openwin/include
/apps/public/solaris2.8/include'
'--site-libraries=/apps/public/solaris2.8/usr/openwin/lib
/apps/public/solaris2.8/lib'
When running make, I get these errors trying to build the modules:
make[1]: Leaving directory `/apps/public/XEmacs/src/xemacs-21.5.10/build-modules/lwlib'
cd ./modules/ldap && make all
make[1]: Entering directory `/apps/public/XEmacs/src/xemacs-21.5.10/build-modules/modules/ldap'
../../lib-src/ellcc -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wundef -Wstrict-prototypes -Wpacked -Wshadow -Wmissing-declarations -Wpointer-arith -g -O3 --mode=compile --mod-output=eldap.o -I../../src -I/apps/public/XEmacs/src/xemacs-21.5.10/modules/ldap/../../src -c /apps/public/XEmacs/src/xemacs-21.5.10/modules/ldap/eldap.c
In file included from /apps/public/XEmacs/src/xemacs-21.5.10/modules/ldap/eldap.c:34:
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:103:8: warning: "SIZEOF_VOID_P" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:103:28: warning: "SIZEOF_LONG" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:120:5: warning: "SIZEOF_SHORT" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:123:7: warning: "SIZEOF_INT" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:128:2: #error Unable to find a 16-bit integral type
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:131:5: warning: "SIZEOF_INT" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:135:7: warning: "SIZEOF_LONG" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:140:7: warning: "SIZEOF_SHORT" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:145:51: #if with no expression
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:149:5: warning: "SIZEOF_LONG" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:153:7: warning: "SIZEOF_LONG_LONG" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:160:5: warning: "SIZEOF_LONG_LONG" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:757:7: warning: "SIZEOF_VOID_P" is not defined
/apps/public/XEmacs/src/xemacs-21.5.10/src/lisp.h:757:24: warning: "SIZEOF_INT" is not defined
In file included from /apps/public/XEmacs/src/xemacs-21.5.10/modules/ldap/eldap.c:34:
And so on. It seems that it can't find config.h but there are not
complaints about not being able to find config.h from the compiler.
If you need more information please ask. I didn't want to clutter the
mailing list with too much possibly useless info just yet. :-)
Ray
- 3 participants
- 6 comments