From: Bruno H. <br...@cl...> - 2004-11-25 20:05:14
|
Through testing the clos.tst and mop.tst testsuite on various other MOP implementations, I can somewhat estimate how much of the MOP they implement (i.e. how many of the subprotocols they implement, or how many interesting functionalities they allow to be programmed by the user). The ranking is CLISP CVS 100% SBCL 0.8.16 90% CMUCL 19a 85% ALLEGRO 6.2, OpenMCL 0.14.2 75% LISPWORKS 4.3 50% LispWorks is very deceiving: It doesn't even define classes such as SPECIALIZER and EQL-SPECIALIZER. Some operations that are allowed according to the MOP trigger a stack overflow. Calls to SET-FUNCALLABLE-INSTANCE-FUNCTION trigger serious GC problems, etc. (Other than that, LispWorks is also deceiving because of its low quality. Where an SBCL bug triggers an error message "CALL-METHOD outside of a effective method form", LispWorks just says: "malformed". Also a simple stack overflow is often enough to drag it down, with complete loss of the session data.) Bruno |
From: Sam S. <sd...@gn...> - 2004-11-26 20:19:16
|
> * Bruno Haible <oe...@py...t> [2004-11-25 21:04:31 +0100]: > > Through testing the clos.tst and mop.tst testsuite on various other MOP > implementations, I can somewhat estimate how much of the MOP they implement > (i.e. how many of the subprotocols they implement, or how many interesting > functionalities they allow to be programmed by the user). The ranking is > > CLISP CVS 100% > SBCL 0.8.16 90% > CMUCL 19a 85% > ALLEGRO 6.2, OpenMCL 0.14.2 75% > LISPWORKS 4.3 50% > > LispWorks is very deceiving: It doesn't even define classes such as > SPECIALIZER and EQL-SPECIALIZER. Some operations that are allowed according > to the MOP trigger a stack overflow. Calls to > SET-FUNCALLABLE-INSTANCE-FUNCTION trigger serious GC problems, etc. > (Other than that, LispWorks is also deceiving because of its low quality. > Where an SBCL bug triggers an error message "CALL-METHOD outside of a > effective method form", LispWorks just says: "malformed". Also a simple > stack overflow is often enough to drag it down, with complete loss of the > session data.) Good! would you like to announce MOP availability for pretesting on SF and clisp-announce? -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> Between grand theft and a legal fee, there only stands a law degree. |
From: Bruno H. <br...@cl...> - 2004-11-26 21:49:43
|
Sam wrote: > would you like to announce MOP availability for pretesting on SF and > clisp-announce? That would be a good idea, indeed, to let people test the CLOS for a few weeks, before we get to the portability testing with 2.33.90/91/92/... prereleases. Can you update impnotes.html and make a 2.33.80 snapshot? I still haven't found time to search for an image processing tool that can nicely shrink the mop-*.png files by 50%, but that's the kind of thing that must be acceptable in a prerelease :-) Bruno |
From: Sam S. <sd...@gn...> - 2004-11-27 23:56:01
|
> * Bruno Haible <oe...@py...t> [2004-11-26 22:48:56 +0100]: > > I still haven't found time to search for an image processing tool that > can nicely shrink the mop-*.png files by 50% imagemagick? -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> ((lambda (x) `(,x ',x)) '(lambda (x) `(,x ',x))) |
From: Reini U. <ru...@x-...> - 2004-11-28 15:45:02
|
Sam Steingold schrieb: >>* Bruno Haible <oe...@py...t> [2004-11-26 22:48:56 +0100]: >>I still haven't found time to search for an image processing tool that >>can nicely shrink the mop-*.png files by 50% > > imagemagick? no, the best known png shrinker is PNGOUT at http://www.advsys.net/ken/utils.htm#pngout -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
From: Bruno H. <br...@cl...> - 2004-12-25 15:41:03
|
Sam wrote: > > I still haven't found time to search for an image processing tool that > > can nicely shrink the mop-*.png files by 50% > > imagemagick? Yes, thanks, that worked nicely. Bruno |
From: Sam S. <sd...@gn...> - 2004-11-28 02:11:01
|
> * Bruno Haible <oe...@py...t> [2004-11-26 22:48:56 +0100]: > > Can you update impnotes.html and make a 2.33.80 snapshot? msgfmt --statistics --check -o de.gmo de.po de.po:7176: format specifications in 'msgid' and 'msgstr' are not equivalent de.po:7256: format specifications in 'msgid' and 'msgstr' are not equivalent de.po:7351: format specifications in 'msgid' and 'msgstr' are not equivalent de.po:7361: format specifications in 'msgid' and 'msgstr' are not equivalent de.po:7376: format specifications in 'msgid' and 'msgstr' are not equivalent msgfmt: found 5 fatal errors make[1]: *** [de.gmo] Error 1 -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> OK, so you're a Ph.D. Just don't touch anything. |
From: Bruno H. <br...@cl...> - 2004-11-29 12:34:28
|
Sam wrote: > msgfmt --statistics --check -o de.gmo de.po > de.po:7176: format specifications in 'msgid' and 'msgstr' are not equivalent That's a bug in gettext 0.14.1. Please use http://www.haible.de/bruno/gnu/gettext-0.15-pre1.tar.gz Bruno |
From: Sam S. <sd...@gn...> - 2004-11-29 14:54:32
|
> * Bruno Haible <oe...@py...t> [2004-11-29 13:33:36 +0100]: > > Sam wrote: >> msgfmt --statistics --check -o de.gmo de.po >> de.po:7176: format specifications in 'msgid' and 'msgstr' are not equivalent > > That's a bug in gettext 0.14.1. Please use > http://www.haible.de/bruno/gnu/gettext-0.15-pre1.tar.gz I try to build from sources only those packages to which I contribute. Could you please update the src/po/ directory with your latest gettext? thanks! -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> Life is like a diaper -- short and loaded. |
From: Sam S. <sd...@gn...> - 2004-11-29 18:59:41
|
> * Bruno Haible <oe...@py...t> [2004-11-29 13:33:36 +0100]: > > Sam wrote: >> msgfmt --statistics --check -o de.gmo de.po >> de.po:7176: format specifications in 'msgid' and 'msgstr' are not equivalent > > That's a bug in gettext 0.14.1. Please use > http://www.haible.de/bruno/gnu/gettext-0.15-pre1.tar.gz gcc -shared .libs/gettext-po.o -L/usr/lib -L/cygdrive/d/gnu/gettext-0.15-pre1/ gettext-tools/intl/.libs -L/cygdrive/d/gnu/gettext-0.15-pre1/gettext-tools/lib/. libs ./.libs/libgettextsrc.dll.a ../lib/.libs/libgettextlib.dll.a -o .libs/cygg ettextpo-0.dll -Wl,--image-base=0x10000000 -Wl,--out-implib,.libs/libgettextpo.d ll.a Creating library file: .libs/libgettextpo.dll.a .libs/gettext-po.o(.text+0x2d): In function `po_file_create': /cygdrive/d/gnu/gettext-0.15-pre1/gettext-tools/src/gettext-po.c:75: undefined r eference to `_libintl_gettext' .libs/gettext-po.o(.text+0xc3b): In function `po_error_logger': /cygdrive/d/gnu/gettext-0.15-pre1/gettext-tools/src/gettext-po.c:720: undefined reference to `_libintl_vasprintf' .libs/gettext-po.o(.text+0xc7d):/cygdrive/d/gnu/gettext-0.15-pre1/gettext-tools/ src/gettext-po.c:721: undefined reference to `_libintl_gettext' Info: resolving _po_error by linking to __imp__po_error (auto-import) Info: resolving _po_error_at_line by linking to __imp__po_error_at_line (auto-im port) Info: resolving _po_multiline_warning by linking to __imp__po_multiline_warning (auto-import) Info: resolving _po_multiline_error by linking to __imp__po_multiline_error (aut o-import) Info: resolving _format_language by linking to __imp__format_language (auto-impo rt) collect2: ld returned 1 exit status make[4]: *** [libgettextpo.la] Error 1 it will save both of us a lot of time if you just regenerated the PO files yourself. you will be the one updating the translations anyway... -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> MS Windows: error: the operation completed successfully. |
From: Bruno H. <br...@cl...> - 2004-11-29 16:37:18
|
Sam wrote: > Could you please update the src/po/ directory with your latest gettext? That's quite useless, since the next times you do "make -f Makefile.devel" on your own, it will again produce the PO files incorrectly. If everytime you make a release, you need to wait 1 day for me to produce and commit correct PO files, making releases will become a weird process. You are making the releases, so you need the appropriate tools. Bruno |
From: Sam S. <sd...@gn...> - 2004-11-29 17:07:03
|
> * Bruno Haible <oe...@py...t> [2004-11-29 17:36:26 +0100]: > > Sam wrote: >> Could you please update the src/po/ directory with your latest gettext? > > That's quite useless, since the next times you do "make -f > Makefile.devel" on your own, it will again produce the PO files > incorrectly. "cvs up -C" will take care of that. > If everytime you make a release, you need to wait 1 day for me to > produce and commit correct PO files, making releases will become a > weird process. only until gettext works with clisp. > You are making the releases, so you need the appropriate tools. when are you going to release gettext 0.15? -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> There are 10 kinds of people: those who count in binary and those who do not. |
From: Bruno H. <br...@cl...> - 2004-11-29 18:21:12
|
Sam wrote: > only until gettext works with clisp. gettext 0.15-pre1 works with clisp. gettext 0.14.1 did not! > > You are making the releases, so you need the appropriate tools. > > when are you going to release gettext 0.15? Three or six months after the clisp release. I put my effort on the clisp release in the next two months and will put my effort on gettext afterwards. Bruno |
From: Bruno H. <br...@cl...> - 2004-11-29 21:13:02
|
Sam wrote: > .libs/gettext-po.o(.text+0x2d): In function `po_file_create': > /cygdrive/d/gnu/gettext-0.15-pre1/gettext-tools/src/gettext-po.c:75: > undefined reference to `_libintl_gettext' > .libs/gettext-po.o(.text+0xc3b): In function `po_error_logger': > /cygdrive/d/gnu/gettext-0.15-pre1/gettext-tools/src/gettext-po.c:720: > undefined reference to `_libintl_vasprintf' I see, thanks: Missing dependencies of libgettextpo. You will now be mentioned in gettext's THANKS file :-) As a workaround, configure with --disable-shared --enable-static. Sorry. Bruno |
From: Sam S. <sd...@gn...> - 2004-11-29 21:29:48
|
> * Bruno Haible <oe...@py...t> [2004-11-29 22:11:41 +0100]: > > I see, thanks: Missing dependencies of libgettextpo. You will now be > mentioned in gettext's THANKS file :-) Thanks! :-) > As a workaround, configure with --disable-shared --enable-static. Sorry. $ ./configure --disable-shared --enable-static checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin configure: creating ./config.status config.status: creating Makefile configure: configuring in autoconf-lib-link configure: running /bin/bash './configure' --prefix=/usr/local '--disable-share d' '--enable-static' --cache-file=/dev/null --srcdir=. configure: error: invalid feature name: shared configure: error: /bin/bash './configure' failed for autoconf-lib-link $ ./configure --enable-static checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin configure: creating ./config.status config.status: creating Makefile configure: configuring in autoconf-lib-link configure: running /bin/bash './configure' --prefix=/usr/local '--enable-static ' --cache-file=/dev/null --srcdir=. configure: error: invalid feature name: static configure: error: /bin/bash './configure' failed for autoconf-lib-link -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> The world will end in 5 minutes. Please log out. |
From: Bruno H. <br...@cl...> - 2004-11-29 21:59:39
|
Sam wrote: > configure: error: invalid feature name: shared > configure: error: invalid feature name: static Oh, I hate these automake updates which silently break things... Probably the quickest way out for you is to wrap the entire gettext-po.c file into a #if 0 #endif because you won't need the resulting library anyway. Bruno |