Menu
▾
▴
clisp-devel — closed list for developers and testers
You can subscribe to this list here.
| 2000 |
Jan
(81) |
Feb
(55) |
Mar
(459) |
Apr
(159) |
May
(126) |
Jun
(69) |
Jul
(48) |
Aug
(29) |
Sep
(106) |
Oct
(76) |
Nov
(155) |
Dec
(161) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(122) |
Feb
(150) |
Mar
(294) |
Apr
(124) |
May
(197) |
Jun
(266) |
Jul
(111) |
Aug
(259) |
Sep
(163) |
Oct
(142) |
Nov
(101) |
Dec
(86) |
| 2002 |
Jan
(187) |
Feb
(108) |
Mar
(274) |
Apr
(157) |
May
(346) |
Jun
(242) |
Jul
(345) |
Aug
(187) |
Sep
(263) |
Oct
(69) |
Nov
(30) |
Dec
(76) |
| 2003 |
Jan
(125) |
Feb
(191) |
Mar
(87) |
Apr
(69) |
May
(107) |
Jun
(66) |
Jul
(112) |
Aug
(161) |
Sep
(184) |
Oct
(137) |
Nov
(28) |
Dec
(61) |
| 2004 |
Jan
(148) |
Feb
(99) |
Mar
(365) |
Apr
(225) |
May
(311) |
Jun
(204) |
Jul
(95) |
Aug
(214) |
Sep
(256) |
Oct
(290) |
Nov
(239) |
Dec
(152) |
| 2005 |
Jan
(253) |
Feb
(183) |
Mar
(178) |
Apr
(88) |
May
(175) |
Jun
(195) |
Jul
(122) |
Aug
(81) |
Sep
(119) |
Oct
(200) |
Nov
(110) |
Dec
(179) |
| 2006 |
Jan
(154) |
Feb
(64) |
Mar
(55) |
Apr
(69) |
May
(66) |
Jun
(64) |
Jul
(80) |
Aug
(59) |
Sep
(62) |
Oct
(90) |
Nov
(132) |
Dec
(106) |
| 2007 |
Jan
(58) |
Feb
(51) |
Mar
(59) |
Apr
(19) |
May
(33) |
Jun
(52) |
Jul
(15) |
Aug
(50) |
Sep
(41) |
Oct
(259) |
Nov
(323) |
Dec
(136) |
| 2008 |
Jan
(205) |
Feb
(128) |
Mar
(203) |
Apr
(126) |
May
(307) |
Jun
(166) |
Jul
(259) |
Aug
(181) |
Sep
(217) |
Oct
(265) |
Nov
(256) |
Dec
(132) |
| 2009 |
Jan
(104) |
Feb
(81) |
Mar
(27) |
Apr
(21) |
May
(85) |
Jun
(237) |
Jul
(243) |
Aug
(199) |
Sep
(178) |
Oct
(151) |
Nov
(64) |
Dec
(39) |
| 2010 |
Jan
(33) |
Feb
(146) |
Mar
(125) |
Apr
(109) |
May
(52) |
Jun
(135) |
Jul
(103) |
Aug
(68) |
Sep
(99) |
Oct
(88) |
Nov
(45) |
Dec
(56) |
| 2011 |
Jan
(19) |
Feb
(32) |
Mar
(50) |
Apr
(105) |
May
(46) |
Jun
(22) |
Jul
(101) |
Aug
(80) |
Sep
(52) |
Oct
(16) |
Nov
(10) |
Dec
(29) |
| 2012 |
Jan
(8) |
Feb
(22) |
Mar
(17) |
Apr
(68) |
May
(19) |
Jun
(19) |
Jul
(12) |
Aug
(6) |
Sep
(13) |
Oct
(5) |
Nov
(5) |
Dec
(5) |
| 2013 |
Jan
(6) |
Feb
(4) |
Mar
(3) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
(16) |
Apr
(1) |
May
(8) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(8) |
Mar
(23) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(1) |
Oct
|
Nov
|
Dec
(5) |
| 2016 |
Jan
|
Feb
|
Mar
(16) |
Apr
(6) |
May
(53) |
Jun
(19) |
Jul
(3) |
Aug
(39) |
Sep
(24) |
Oct
(2) |
Nov
(19) |
Dec
|
| 2017 |
Jan
(13) |
Feb
(44) |
Mar
(208) |
Apr
(12) |
May
(94) |
Jun
(54) |
Jul
(18) |
Aug
(52) |
Sep
(12) |
Oct
(22) |
Nov
(27) |
Dec
(93) |
| 2018 |
Jan
(85) |
Feb
(28) |
Mar
(16) |
Apr
(47) |
May
(16) |
Jun
(15) |
Jul
(10) |
Aug
(3) |
Sep
(5) |
Oct
|
Nov
(6) |
Dec
|
| 2019 |
Jan
(4) |
Feb
(6) |
Mar
(12) |
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2020 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2022 |
Jan
(2) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(10) |
Oct
(5) |
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
(9) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(28) |
Dec
(3) |
| 2025 |
Jan
(8) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Bruno H. <br...@cl...> - 2017-02-23 13:10:05
|
Hi Daniel, > I think a changelog is a very useful thing to have, but I always felt that > the one of CLISP is by far too detailed. > > Perhaps this [1] could give an inspiration how to keep a changelog that > only contains "important" changes. > [1] http://keepachangelog.com/en/0.3.0/ This kind of log is "for users and contributors to see precisely what notable changes have been made between each release (or version) of the project". In GNU, the NEWS file [2] serves this purpose. Whereas the ChangeLog [3] is for "people investigating bugs in the future". That's why it is so detailed. Bruno [2] https://www.gnu.org/prep/standards/html_node/NEWS-File.html [3] https://www.gnu.org/prep/standards/html_node/Change-Logs.html |
|
From: Daniel J. <dan...@gm...> - 2017-02-23 08:44:28
|
Hi, I think a changelog is a very useful thing to have, but I always felt that the one of CLISP is by far too detailed. Perhaps this [1] could give an inspiration how to keep a changelog that only contains "important" changes. The "full detailed list of changes" would then be maintained through commit messages. Best, Daniel (Yes I'm still here, though only reading. Long story short, I'm basically ill since last October and thus have barely time for anything) [1] http://keepachangelog.com/en/0.3.0/ Bruno Haible <br...@cl...> schrieb am Do., 23. Feb. 2017, 01:16: > Hi Sam, > > > ChangeLog is obsolete. Even Emacs does not use it anymore. > > Different groups of developers make different choices. > > > While I see obvious benefits > > The not so obvious benefits are: > > - We can really keep track of the history over long periods of time. > Whereas when we rely on a VCS, we lose info at each move to a different > location. (Like the gmane.org article URLs became obsolete six months > ago.) > In the recent move of libffcall from cvs to git we did not lose info, > but it cost me two days of work to achieve this result. > > - You get educated to review your changes before committing them. > > - You can access a ChangeLog without any tools, just with a text editor. > > > for me the main drawback is that it > > dramatically increases the probability of conflicts. > > 1) There is a tool for automatically resolving these conflicts: > > http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=lib/git-merge-changelog.c > You find the installation instructions at lines 42..48, 77..88 of this > file. > > 2) Even without it, yes there would be conflicts, but they are easy to > resolve, > since you remember what you have added. Conflicts are only difficult to > resolve > if you don't remember what were your changes versus what were the other > person's > changes. > > > If I make a local commit and do not push it right away, it is almost > > certain that I will have to go through either merge or strip/recommit > > because rebase will definitely fail. > > It is not the intent of ChangeLog that you feel the need to push > immediately. Just keep the same patience as before. > > In all projects I work in (from gnulib to libffcall), I find ChangeLogs > useful. > In projects without ChangeLog (e.g. XFree86), I found it hard to work. > > I admit that in projects with many branches and merges (like the github > workflow) > ChangeLogs are not appropriate. But clisp is not in this situation. > > Bruno > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > clisp-devel mailing list > cli...@li... > https://lists.sourceforge.net/lists/listinfo/clisp-devel > |
|
From: Bruno H. <br...@cl...> - 2017-02-23 00:44:51
|
Re https://sourceforge.net/p/clisp/mailman/message/35677912/ Hi Jerry, > The clisp package is currently failing to build in Fedora Rawhide, > due to this build failure in the fastcgi module: Thanks. Should be fixed now. Please continue reporting if something else breaks / broke too. Bruno |
|
From: Bruno H. <br...@cl...> - 2017-02-23 00:15:41
|
Hi Sam,
> ChangeLog is obsolete. Even Emacs does not use it anymore.
Different groups of developers make different choices.
> While I see obvious benefits
The not so obvious benefits are:
- We can really keep track of the history over long periods of time.
Whereas when we rely on a VCS, we lose info at each move to a different
location. (Like the gmane.org article URLs became obsolete six months ago.)
In the recent move of libffcall from cvs to git we did not lose info,
but it cost me two days of work to achieve this result.
- You get educated to review your changes before committing them.
- You can access a ChangeLog without any tools, just with a text editor.
> for me the main drawback is that it
> dramatically increases the probability of conflicts.
1) There is a tool for automatically resolving these conflicts:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=lib/git-merge-changelog.c
You find the installation instructions at lines 42..48, 77..88 of this file.
2) Even without it, yes there would be conflicts, but they are easy to resolve,
since you remember what you have added. Conflicts are only difficult to resolve
if you don't remember what were your changes versus what were the other person's
changes.
> If I make a local commit and do not push it right away, it is almost
> certain that I will have to go through either merge or strip/recommit
> because rebase will definitely fail.
It is not the intent of ChangeLog that you feel the need to push
immediately. Just keep the same patience as before.
In all projects I work in (from gnulib to libffcall), I find ChangeLogs useful.
In projects without ChangeLog (e.g. XFree86), I found it hard to work.
I admit that in projects with many branches and merges (like the github workflow)
ChangeLogs are not appropriate. But clisp is not in this situation.
Bruno
|
|
From: Pascal B. <pj...@in...> - 2017-02-22 22:51:42
|
> On 22 Feb 2017, at 21:11, Sam Steingold <sd...@gn...> wrote: > > Hi, > > ChangeLog is obsolete. Even Emacs does not use it anymore. > > While I see obvious benefits, for me the main drawback is that it > dramatically increases the probability of conflicts. > If I make a local commit and do not push it right away, it is almost > certain that I will have to go through either merge or strip/recommit > because rebase will definitely fail. > > WDYT? There would be the option of generating it automatically from git log when making the tarball, but then git logs are usually much more detailed than a high level ChangeLog. Probably, people interested in the history can always checkout from the repository instead of using tarballs. -- __Pascal J. Bourguignon__ |
|
From: Sam S. <sd...@gn...> - 2017-02-22 20:11:10
|
Hi, ChangeLog is obsolete. Even Emacs does not use it anymore. While I see obvious benefits, for me the main drawback is that it dramatically increases the probability of conflicts. If I make a local commit and do not push it right away, it is almost certain that I will have to go through either merge or strip/recommit because rebase will definitely fail. WDYT? -- Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504 http://steingoldpsychology.com http://www.childpsy.net http://www.dhimmitude.org https://jihadwatch.org http://jij.org http://iris.org.il http://memri.org There are two ways to write error-free programs; only the third one works. |
|
From: Jerry J. <log...@gm...> - 2017-02-20 19:29:31
|
Greetings, The clisp package is currently failing to build in Fedora Rawhide, due to this build failure in the fastcgi module: In file included from /builddir/build/BUILD/clisp-2.49/modules/fastcgi/fastcgi_wrappers.c:24:0: /builddir/build/BUILD/clisp-2.49/build/gllib/unistd.h:139:3: error: #error "Please include config.h first." #error "Please include config.h first." ^~~~~ Is this perhaps related to the recent gnulib update? Simply adding "#include <config.h>" to the top of fastcgi_wrappers.c fixed the problem for me. Regards, -- Jerry James http://www.jamezone.org/ |
|
From: <cli...@li...> - 2017-02-20 17:17:05
|
Send clisp-cvs mailing list submissions to cli...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/clisp-cvs or, via email, send a message with subject or body 'help' to cli...@li... You can reach the person managing the list at cli...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of clisp-cvs digest..." CLISP CVS commits for today Today's Topics: 1. clisp: Define a single place to set the libsigsegv download URL. (cli...@li...) 2. clisp: Recommend libsigsegv 2.11. (cli...@li...) 3. clisp: Disable the 'ulimit -s 16384' recommendation, except on P... (cli...@li...) 4. clisp: Fix build failure on Linux with musl libc. (cli...@li...) 5. clisp: maint: Fix conflict between fix-perms.sh and gnulib import. (cli...@li...) 6. clisp: Modernize: Really update to the newest gnulib. (cli...@li...) 7. clisp: Make --with-{libsigsegv,libffcall}-prefix with clang on 6... (cli...@li...) 8. clisp: Fix build failure with clang. (cli...@li...) 9. clisp: Fix clang warning "flag '-falign-functions=4' is not supp... (cli...@li...) 10. clisp: Fix collision between ASCII character names and Unicode c... (cli...@li...) ---------------------------------------------------------------------- Message: 1 Date: Mon, 20 Feb 2017 17:16:48 +0000 From: cli...@li... Subject: clisp: Define a single place to set the libsigsegv download URL. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/5163d60da64c changeset: 15720:5163d60da64ccaa9aec91cff1ce3d4d0dee23ac5 user: Bruno Haible <br...@cl...> date: 2017-02-19 12:25:37 +0100 description: Define a single place to set the libsigsegv download URL. diffstat: configure | 12 ++++++++---- src/ChangeLog | 6 ++++++ 2 files changed, 14 insertions(+), 4 deletions(-) ------------------------------ Message: 2 Date: Mon, 20 Feb 2017 17:16:49 +0000 From: cli...@li... Subject: clisp: Recommend libsigsegv 2.11. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/605c6af75ff0 changeset: 15721:605c6af75ff014e3a5186e21a683555a3fc35825 user: Bruno Haible <br...@cl...> date: 2017-02-19 12:28:02 +0100 description: Recommend libsigsegv 2.11. diffstat: configure | 2 +- src/ChangeLog | 5 +++++ 2 files changed, 6 insertions(+), 1 deletions(-) ------------------------------ Message: 3 Date: Mon, 20 Feb 2017 17:16:50 +0000 From: cli...@li... Subject: clisp: Disable the 'ulimit -s 16384' recommendation, except on P... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/3d2a5226028f changeset: 15722:3d2a5226028f5d07fe5bbb9c8269c67bc1e72451 user: Bruno Haible <br...@cl...> date: 2017-02-19 12:50:51 +0100 description: Disable the 'ulimit -s 16384' recommendation, except on PowerPC. diffstat: configure | 13 +++++++++++-- src/ChangeLog | 5 +++++ 2 files changed, 16 insertions(+), 2 deletions(-) ------------------------------ Message: 4 Date: Mon, 20 Feb 2017 17:16:52 +0000 From: cli...@li... Subject: clisp: Fix build failure on Linux with musl libc. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/13538543e272 changeset: 15723:13538543e272a82375dc43aee744975dd940b654 user: Bruno Haible <br...@cl...> date: 2017-02-19 13:44:10 +0100 description: Fix build failure on Linux with musl libc. diffstat: src/ChangeLog | 6 ++++++ src/unix.d | 3 --- 2 files changed, 6 insertions(+), 3 deletions(-) ------------------------------ Message: 5 Date: Mon, 20 Feb 2017 17:16:53 +0000 From: cli...@li... Subject: clisp: maint: Fix conflict between fix-perms.sh and gnulib import. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/3d89bf950165 changeset: 15724:3d89bf950165dc93afdac15237b490b04b7db9b3 user: Bruno Haible <br...@cl...> date: 2017-02-19 15:53:07 +0100 description: maint: Fix conflict between fix-perms.sh and gnulib import. diffstat: src/ChangeLog | 6 ++++++ utils/fix-perms.sh | 2 +- 2 files changed, 7 insertions(+), 1 deletions(-) ------------------------------ Message: 6 Date: Mon, 20 Feb 2017 17:16:56 +0000 From: cli...@li... Subject: clisp: Modernize: Really update to the newest gnulib. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/4c9d0558e61e changeset: 15725:4c9d0558e61e57eff99ff744e9974dc56df20888 user: Bruno Haible <br...@cl...> date: 2017-02-19 16:45:35 +0100 description: Modernize: Really update to the newest gnulib. diffstat: Makefile.devel | 4 +- modules/berkeley-db/config.h.in | 82 +- modules/berkeley-db/configure | 296 +- modules/clx/new-clx/config.h.in | 88 +- modules/clx/new-clx/configure | 194 +- modules/dbus/config.h.in | 62 +- modules/dbus/configure | 158 +- modules/dirkey/config.h.in | 62 +- modules/dirkey/configure | 158 +- modules/fastcgi/config.h.in | 62 +- modules/fastcgi/configure | 262 +- modules/gdbm/config.h.in | 62 +- modules/gdbm/configure | 260 +- modules/gtk2/config.h.in | 62 +- modules/gtk2/configure | 158 +- modules/i18n/config.h.in | 62 +- modules/i18n/configure | 158 +- modules/libsvm/config.h.in | 62 +- modules/libsvm/configure | 260 +- modules/oracle/config.h.in | 62 +- modules/oracle/configure | 158 +- modules/pari/config.h.in | 62 +- modules/pari/configure | 260 +- modules/pcre/config.h.in | 62 +- modules/pcre/configure | 260 +- modules/postgresql/config.h.in | 62 +- modules/postgresql/configure | 260 +- modules/rawsock/config.h.in | 62 +- modules/rawsock/configure | 158 +- modules/readline/config.h.in | 62 +- modules/readline/configure | 225 +- modules/regexp/config.h.in | 62 +- modules/regexp/configure | 175 +- modules/syscalls/config.h.in | 84 +- modules/syscalls/configure | 340 +- modules/zlib/config.h.in | 62 +- modules/zlib/configure | 260 +- src/ChangeLog | 24 + src/aclocal.m4 | 5215 +- src/build-aux/ar-lib | 270 + src/build-aux/compile | 2 +- src/build-aux/config.guess | 9 +- src/build-aux/config.rpath | 2 +- src/build-aux/config.sub | 16 +- src/build-aux/depcomp | 2 +- src/build-aux/missing | 2 +- src/build-aux/snippet/_Noreturn.h | 2 +- src/build-aux/snippet/arg-nonnull.h | 2 +- src/build-aux/snippet/c++defs.h | 89 +- src/build-aux/snippet/warn-on-use.h | 4 +- src/build-aux/ylwrap | 2 +- src/config.h.in | 478 +- src/configure | 9136 +- src/gllib/Makefile.am | 435 +- src/gllib/Makefile.in | 475 +- src/gllib/accept.c | 20 +- src/gllib/alignof.h | 53 - src/gllib/alloca.c | 2 +- src/gllib/alloca.in.h | 17 +- src/gllib/arpa_inet.in.h | 39 +- src/gllib/bind.c | 19 +- src/gllib/btowc.c | 2 +- src/gllib/c-ctype.c | 395 +- src/gllib/c-ctype.h | 455 +- src/gllib/close.c | 35 +- src/gllib/config.charset | 11 +- src/gllib/connect.c | 29 +- src/gllib/dosname.h | 2 +- src/gllib/dup2.c | 215 + src/gllib/errno.in.h | 168 +- src/gllib/fcntl.in.h | 363 + src/gllib/fd-hook.c | 2 +- src/gllib/fd-hook.h | 2 +- src/gllib/flexmember.h | 42 + src/gllib/fnmatch.c | 21 +- src/gllib/fnmatch.in.h | 17 +- src/gllib/fnmatch_loop.c | 24 +- src/gllib/gethostname.c | 2 +- src/gllib/getloadavg.c | 36 +- src/gllib/getpagesize.c | 4 +- src/gllib/getpeername.c | 19 +- src/gllib/getsockname.c | 19 +- src/gllib/getsockopt.c | 55 +- src/gllib/gettext.h | 22 +- src/gllib/gettimeofday.c | 16 +- src/gllib/glthread/lock.c | 195 +- src/gllib/glthread/lock.h | 80 +- src/gllib/glthread/threadlib.c | 5 +- src/gllib/hard-locale.c | 72 + src/gllib/hard-locale.h | 25 + src/gllib/inet_ntop.c | 60 +- src/gllib/inet_pton.c | 51 +- src/gllib/intprops.h | 267 +- src/gllib/ioctl.c | 13 +- src/gllib/langinfo.in.h | 23 +- src/gllib/limits.in.h | 63 + src/gllib/listen.c | 19 +- src/gllib/localcharset.c | 120 +- src/gllib/localcharset.h | 5 +- src/gllib/locale.in.h | 216 + src/gllib/localeconv.c | 103 + src/gllib/lstat.c | 20 +- src/gllib/malloc.c | 57 - src/gllib/malloca.c | 40 +- src/gllib/malloca.h | 22 +- src/gllib/mbrtowc.c | 85 +- src/gllib/mbsinit.c | 2 +- src/gllib/mbsrtowcs-impl.h | 2 +- src/gllib/mbsrtowcs-state.c | 4 +- src/gllib/mbsrtowcs.c | 2 +- src/gllib/mbtowc-impl.h | 2 +- src/gllib/mbtowc.c | 2 +- src/gllib/memchr.c | 2 +- src/gllib/mkdtemp.c | 2 +- src/gllib/mkfifo.c | 2 +- src/gllib/mknod.c | 2 +- src/gllib/mkstemp.c | 2 +- src/gllib/mktime-internal.h | 35 +- src/gllib/mktime.c | 687 +- src/gllib/msvc-inval.c | 129 + src/gllib/msvc-inval.h | 222 + src/gllib/msvc-nothrow.c | 49 + src/gllib/msvc-nothrow.h | 43 + src/gllib/netinet_in.in.h | 5 +- src/gllib/nl_langinfo.c | 285 +- src/gllib/pathmax.h | 83 + src/gllib/readlink.c | 2 +- src/gllib/recv.c | 19 +- src/gllib/recvfrom.c | 30 +- src/gllib/ref-add.sin | 5 +- src/gllib/ref-del.sin | 5 +- src/gllib/regcomp.c | 555 +- src/gllib/regex.c | 37 +- src/gllib/regex.h | 296 +- src/gllib/regex_internal.c | 170 +- src/gllib/regex_internal.h | 221 +- src/gllib/regexec.c | 384 +- src/gllib/secure_getenv.c | 54 + src/gllib/select.c | 152 +- src/gllib/send.c | 19 +- src/gllib/sendto.c | 19 +- src/gllib/setenv.c | 20 +- src/gllib/setsockopt.c | 35 +- src/gllib/shutdown.c | 19 +- src/gllib/signal.in.h | 73 +- src/gllib/socket.c | 2 +- src/gllib/sockets.c | 10 +- src/gllib/sockets.h | 29 +- src/gllib/stat.c | 43 +- src/gllib/stdalign.in.h | 121 + src/gllib/stdbool.in.h | 56 +- src/gllib/stddef.in.h | 59 +- src/gllib/stdint.in.h | 785 +- src/gllib/stdlib.in.h | 266 +- src/gllib/strcasecmp.c | 62 + src/gllib/streq.h | 10 +- src/gllib/strerror-override.c | 117 +- src/gllib/strerror-override.h | 12 +- src/gllib/strerror_r.c | 52 +- src/gllib/strftime.c | 312 +- src/gllib/strftime.h | 9 +- src/gllib/string.in.h | 65 +- src/gllib/strings.in.h | 122 + src/gllib/strncasecmp.c | 62 + src/gllib/strnlen1.c | 2 +- src/gllib/strnlen1.h | 5 +- src/gllib/strptime.c | 42 +- src/gllib/strverscmp.c | 99 +- src/gllib/sys_ioctl.in.h | 5 +- src/gllib/sys_select.in.h | 93 +- src/gllib/sys_socket.c | 4 + src/gllib/sys_socket.in.h | 26 +- src/gllib/sys_stat.in.h | 108 +- src/gllib/sys_time.in.h | 195 +- src/gllib/sys_types.in.h | 53 + src/gllib/sys_uio.in.h | 7 +- src/gllib/sys_utsname.in.h | 5 +- src/gllib/sys_wait.in.h | 5 +- src/gllib/tempname.c | 129 +- src/gllib/tempname.h | 17 +- src/gllib/time-internal.h | 49 + src/gllib/time.in.h | 80 +- src/gllib/time_r.c | 5 +- src/gllib/time_rz.c | 322 + src/gllib/timegm.c | 40 + src/gllib/uname.c | 2 +- src/gllib/uniname.in.h | 5 +- src/gllib/uniname/gen-uninames.lisp | 139 +- src/gllib/uniname/uniname.c | 278 +- src/gllib/uniname/uninames.h | 143787 ++++++++++++++++++++------------ src/gllib/unistd.c | 4 + src/gllib/unistd.in.h | 315 +- src/gllib/unitypes.in.h | 24 +- src/gllib/uniwidth.in.h | 23 +- src/gllib/uniwidth/cjk.h | 18 +- src/gllib/uniwidth/width.c | 152 +- src/gllib/unsetenv.c | 8 +- src/gllib/verify.h | 157 +- src/gllib/w32sock.h | 89 +- src/gllib/wchar.in.h | 101 +- src/gllib/wcrtomb.c | 2 +- src/gllib/wctype-h.c | 4 + src/gllib/wctype.in.h | 82 +- src/gllib/xalloc-oversized.h | 60 + src/glm4/00gnulib.m4 | 22 +- src/glm4/absolute-header.m4 | 102 + src/glm4/alloca.m4 | 18 +- src/glm4/arpa_inet_h.m4 | 6 +- src/glm4/asm-underscore.m4 | 71 + src/glm4/btowc.m4 | 2 +- src/glm4/builtin-expect.m4 | 49 + src/glm4/close.m4 | 8 +- src/glm4/codeset.m4 | 3 +- src/glm4/configmake.m4 | 13 +- src/glm4/dup2.m4 | 117 + src/glm4/eealloc.m4 | 5 +- src/glm4/environ.m4 | 15 +- src/glm4/errno_h.m4 | 16 +- src/glm4/extensions.m4 | 88 +- src/glm4/extern-inline.m4 | 102 + src/glm4/fcntl-o.m4 | 30 +- src/glm4/fcntl_h.m4 | 50 + src/glm4/flexmember.m4 | 43 + src/glm4/fnmatch.m4 | 8 +- src/glm4/gethostname.m4 | 10 +- src/glm4/getloadavg.m4 | 18 +- src/glm4/getpagesize.m4 | 2 +- src/glm4/gettext.m4 | 43 +- src/glm4/gettimeofday.m4 | 57 +- src/glm4/glibc2.m4 | 2 +- src/glm4/glibc21.m4 | 2 +- src/glm4/gnu-make.m4 | 2 +- src/glm4/gnulib-cache.m4 | 26 +- src/glm4/gnulib-common.m4 | 216 +- src/glm4/gnulib-comp.m4 | 878 +- src/glm4/gnulib-tool.m4 | 2 +- src/glm4/hard-locale.m4 | 11 + src/glm4/host-cpu-c-abi.m4 | 136 +- src/glm4/iconv.m4 | 87 +- src/glm4/include_next.m4 | 35 +- src/glm4/inet_ntop.m4 | 73 +- src/glm4/inet_pton.m4 | 73 +- src/glm4/intdiv0.m4 | 8 +- src/glm4/intl.m4 | 82 +- src/glm4/intldir.m4 | 6 +- src/glm4/intlmacosx.m4 | 18 +- src/glm4/intmax.m4 | 2 +- src/glm4/inttypes-pri.m4 | 2 +- src/glm4/inttypes_h.m4 | 2 +- src/glm4/ioctl.m4 | 2 +- src/glm4/langinfo_h.m4 | 2 +- src/glm4/largefile.m4 | 88 +- src/glm4/lcmessage.m4 | 8 +- src/glm4/lib-ld.m4 | 60 +- src/glm4/lib-link.m4 | 2 +- src/glm4/lib-prefix.m4 | 2 +- src/glm4/libsigsegv.m4 | 2 +- src/glm4/libunistring-base.m4 | 2 +- src/glm4/limits-h.m4 | 31 + src/glm4/link-follow.m4 | 25 +- src/glm4/localcharset.m4 | 2 +- src/glm4/locale-fr.m4 | 28 +- src/glm4/locale-ja.m4 | 17 +- src/glm4/locale-zh.m4 | 14 +- src/glm4/locale_h.m4 | 122 + src/glm4/localeconv.m4 | 22 + src/glm4/lock.m4 | 22 +- src/glm4/longlong.m4 | 8 +- src/glm4/lstat.m4 | 73 +- src/glm4/malloc.m4 | 60 - src/glm4/malloca.m4 | 2 +- src/glm4/mbrtowc.m4 | 104 +- src/glm4/mbsinit.m4 | 2 +- src/glm4/mbsrtowcs.m4 | 2 +- src/glm4/mbstate_t.m4 | 2 +- src/glm4/mbtowc.m4 | 2 +- src/glm4/memchr.m4 | 2 +- src/glm4/mkdtemp.m4 | 2 +- src/glm4/mkfifo.m4 | 26 +- src/glm4/mknod.m4 | 36 +- src/glm4/mkstemp.m4 | 22 +- src/glm4/mktime.m4 | 64 +- src/glm4/mmap-anon.m4 | 14 +- src/glm4/msvc-inval.m4 | 19 + src/glm4/msvc-nothrow.m4 | 10 + src/glm4/multiarch.m4 | 6 +- src/glm4/netinet_in_h.m4 | 2 +- src/glm4/nl_langinfo.m4 | 2 +- src/glm4/nls.m4 | 8 +- src/glm4/no-c++.m4 | 2 +- src/glm4/nocrash.m4 | 37 +- src/glm4/off_t.m4 | 18 + src/glm4/pathmax.m4 | 42 + src/glm4/po.m4 | 25 +- src/glm4/printf-posix.m4 | 2 +- src/glm4/progtest.m4 | 2 +- src/glm4/pthread_rwlock_rdlock.m4 | 163 + src/glm4/readlink.m4 | 32 +- src/glm4/regex.m4 | 124 +- src/glm4/secure_getenv.m4 | 26 + src/glm4/select.m4 | 68 +- src/glm4/setenv.m4 | 44 +- src/glm4/signal_h.m4 | 10 +- src/glm4/size_max.m4 | 2 +- src/glm4/socketlib.m4 | 2 +- src/glm4/sockets.m4 | 2 +- src/glm4/socklen.m4 | 2 +- src/glm4/sockpfaf.m4 | 2 +- src/glm4/ssize_t.m4 | 2 +- src/glm4/stat.m4 | 23 +- src/glm4/stdalign.m4 | 57 + src/glm4/stdbool.m4 | 60 +- src/glm4/stddef_h.m4 | 10 +- src/glm4/stdint.m4 | 103 +- src/glm4/stdint_h.m4 | 2 +- src/glm4/stdlib_h.m4 | 27 +- src/glm4/strcase.m4 | 45 + src/glm4/strerror.m4 | 50 +- src/glm4/strerror_r.m4 | 31 +- src/glm4/strftime.m4 | 2 +- src/glm4/string_h.m4 | 2 +- src/glm4/strings_h.m4 | 52 + src/glm4/strptime.m4 | 2 +- src/glm4/strverscmp.m4 | 2 +- src/glm4/sys_ioctl_h.m4 | 2 +- src/glm4/sys_select_h.m4 | 2 +- src/glm4/sys_socket_h.m4 | 5 +- src/glm4/sys_stat_h.m4 | 26 +- src/glm4/sys_time_h.m4 | 45 +- src/glm4/sys_types_h.m4 | 49 + src/glm4/sys_uio_h.m4 | 2 +- src/glm4/sys_utsname_h.m4 | 2 +- src/glm4/sys_wait_h.m4 | 7 +- src/glm4/tempname.m4 | 2 +- src/glm4/threadlib.m4 | 124 +- src/glm4/time_h.m4 | 33 +- src/glm4/time_r.m4 | 4 +- src/glm4/time_rz.m4 | 21 + src/glm4/timegm.m4 | 26 + src/glm4/tm_gmtoff.m4 | 2 +- src/glm4/uintmax_t.m4 | 2 +- src/glm4/uname.m4 | 2 +- src/glm4/unistd_h.m4 | 45 +- src/glm4/visibility.m4 | 6 +- src/glm4/warn-on-use.m4 | 8 +- src/glm4/wchar_h.m4 | 16 +- src/glm4/wchar_t.m4 | 2 +- src/glm4/wcrtomb.m4 | 2 +- src/glm4/wctype_h.m4 | 18 +- src/glm4/wint_t.m4 | 36 +- src/glm4/xsize.m4 | 5 +- utils/txt2c.c | 12 +- 352 files changed, 115884 insertions(+), 66589 deletions(-) ------------------------------ Message: 7 Date: Mon, 20 Feb 2017 17:16:58 +0000 From: cli...@li... Subject: clisp: Make --with-{libsigsegv,libffcall}-prefix with clang on 6... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/0c830274edfc changeset: 15726:0c830274edfcfb435ba66b44ed107ffbe930afce user: Bruno Haible <br...@cl...> date: 2017-02-19 20:38:35 +0100 description: Make --with-{libsigsegv,libffcall}-prefix with clang on 64-bit Ubuntu. diffstat: modules/berkeley-db/configure | 89 +++++++++++++++++++++------------- modules/fastcgi/configure | 89 +++++++++++++++++++++------------- modules/gdbm/configure | 89 +++++++++++++++++++++------------- modules/libsvm/configure | 89 +++++++++++++++++++++------------- modules/pari/configure | 89 +++++++++++++++++++++------------- modules/pcre/configure | 89 +++++++++++++++++++++------------- modules/postgresql/configure | 89 +++++++++++++++++++++------------- modules/readline/configure | 89 +++++++++++++++++++++------------- modules/zlib/configure | 89 +++++++++++++++++++++------------- src/ChangeLog | 6 ++ src/aclocal.m4 | 107 ++++++++++++++++++++++++----------------- src/configure | 91 +++++++++++++++++++++-------------- src/glm4/lib-prefix.m4 | 107 ++++++++++++++++++++++++----------------- 13 files changed, 671 insertions(+), 441 deletions(-) ------------------------------ Message: 8 Date: Mon, 20 Feb 2017 17:17:00 +0000 From: cli...@li... Subject: clisp: Fix build failure with clang. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/d5fe594979f6 changeset: 15727:d5fe594979f6dc07f508521ca583206f3dc7846f user: Bruno Haible <br...@cl...> date: 2017-02-19 20:42:30 +0100 description: Fix build failure with clang. diffstat: src/ChangeLog | 7 +++++++ src/lispbibl.d | 9 +++++---- 2 files changed, 12 insertions(+), 4 deletions(-) ------------------------------ Message: 9 Date: Mon, 20 Feb 2017 17:17:01 +0000 From: cli...@li... Subject: clisp: Fix clang warning "flag '-falign-functions=4' is not supp... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/1888e7556016 changeset: 15728:1888e75560168646dfaaac8913f1a227ebb790b6 user: Bruno Haible <br...@cl...> date: 2017-02-20 01:13:28 +0100 description: Fix clang warning "flag '-falign-functions=4' is not supported". diffstat: src/ChangeLog | 6 ++++++ src/makemake.in | 14 +++++++++++--- 2 files changed, 17 insertions(+), 3 deletions(-) ------------------------------ Message: 10 Date: Mon, 20 Feb 2017 17:17:02 +0000 From: cli...@li... Subject: clisp: Fix collision between ASCII character names and Unicode c... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/ba38d2c655c7 changeset: 15729:ba38d2c655c7ae2af0a467295438ac2ff578d1db user: Bruno Haible <br...@cl...> date: 2017-02-20 02:28:32 +0100 description: Fix collision between ASCII character names and Unicode character names. diffstat: doc/impbody.xml | 15 +++++++++++++++ src/ChangeLog | 6 ++++++ src/charstrg.d | 30 ++++++++++++++++++++++++------ 3 files changed, 45 insertions(+), 6 deletions(-) ------------------------------ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ------------------------------ _______________________________________________ clisp-cvs mailing list cli...@li... https://lists.sourceforge.net/lists/listinfo/clisp-cvs End of clisp-cvs Digest, Vol 74, Issue 2 **************************************** |
|
From: <cli...@li...> - 2017-02-20 17:16:50
|
Send clisp-cvs mailing list submissions to cli...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/clisp-cvs or, via email, send a message with subject or body 'help' to cli...@li... You can reach the person managing the list at cli...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of clisp-cvs digest..." CLISP CVS commits for today Today's Topics: 1. clisp: Regenerated. (cli...@li...) 2. clisp: Modernize: Remove old GCC bug workaround. (cli...@li...) 3. clisp: Modernize: Remove old Linux workaround. (cli...@li...) 4. clisp: Prepare for ILP32 ABIs on 64-bit CPUs (x32 on x86_64, n32... (cli...@li...) 5. clisp: Add support for Linux/x32 ABI on x86_64. (cli...@li...) 6. clisp: Reduce portability effort for yet unknown 64-bit platforms. (cli...@li...) 7. clisp: Define known facts for more CPUs. (cli...@li...) 8. clisp: common-lisp-hyperspec: with prefix arg, insert the URL in... (cli...@li...) 9. clisp: common-lisp-hyperspec-root: default to http://clhs.lisp.s... (cli...@li...) 10. clisp: Use malloc instead of alloca for large number of sub expr... (cli...@li...) 11. clisp: SF mail archives use a completely new system; Gmane/HTTP ... (cli...@li...) 12. clisp: Fix build problem on 32-bit platforms, introduced on 2016... (cli...@li...) 13. clisp: common-lisp-hyperspec: with prefix arg, save URL in kill-... (cli...@li...) 14. clisp: fix hanging (disassemble 'car) on Mac OS X (cli...@li...) 15. clisp: Support the standard way of building GNU packages. (cli...@li...) 16. clisp: Fix build failure when --with-libsigsegv-prefix option is... (cli...@li...) ---------------------------------------------------------------------- Message: 1 Date: Sat, 12 Nov 2016 15:31:45 +0000 From: cli...@li... Subject: clisp: Regenerated. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/d4d8263fc7e5 changeset: 15704:d4d8263fc7e542edf1681ebdb18b01c1ec227f6f user: Bruno Haible <br...@cl...> date: 2016-11-12 16:28:54 +0100 description: Regenerated. diffstat: modules/berkeley-db/config.h.in | 8 +- modules/berkeley-db/configure | 597 ++- modules/clx/new-clx/config.h.in | 2 +- modules/clx/new-clx/configure | 507 ++- modules/dbus/configure | 448 +- modules/dirkey/configure | 414 +- modules/fastcgi/configure | 446 +- modules/gdbm/configure | 438 +- modules/gtk2/configure | 788 +++-- modules/i18n/configure | 440 +- modules/libsvm/configure | 442 +- modules/oracle/configure | 432 +- modules/pari/configure | 442 +- modules/pcre/configure | 438 +- modules/postgresql/configure | 448 +- modules/rawsock/configure | 454 +- modules/readline/configure | 544 ++- modules/regexp/configure | 700 +++- modules/syscalls/config.h.in | 11 +- modules/syscalls/configure | 862 +++-- modules/zlib/configure | 444 +- src/ChangeLog | 6 + src/aclocal.m4 | 4635 +++++++++++++++++++------------ src/config.h.in | 17 +- src/configure | 5811 +++++++++++++++++++++++--------------- src/gllib/Makefile.in | 377 +- 26 files changed, 12279 insertions(+), 7872 deletions(-) ------------------------------ Message: 2 Date: Sat, 12 Nov 2016 19:42:21 +0000 From: cli...@li... Subject: clisp: Modernize: Remove old GCC bug workaround. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/0b432db27af1 changeset: 15705:0b432db27af1a33f02237063f8f684886a73cedd user: Bruno Haible <br...@cl...> date: 2016-11-12 20:23:02 +0100 description: Modernize: Remove old GCC bug workaround. diffstat: src/ChangeLog | 5 +++++ src/lispbibl.d | 5 ----- 2 files changed, 5 insertions(+), 5 deletions(-) ------------------------------ Message: 3 Date: Sat, 12 Nov 2016 19:42:23 +0000 From: cli...@li... Subject: clisp: Modernize: Remove old Linux workaround. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/4963c84a8f6d changeset: 15706:4963c84a8f6d6cac3dd188c5bea426e781a15d3a user: Bruno Haible <br...@cl...> date: 2016-11-12 20:41:46 +0100 description: Modernize: Remove old Linux workaround. diffstat: src/ChangeLog | 5 +++++ src/makemake.in | 8 -------- 2 files changed, 5 insertions(+), 8 deletions(-) ------------------------------ Message: 4 Date: Sun, 13 Nov 2016 21:45:35 +0000 From: cli...@li... Subject: clisp: Prepare for ILP32 ABIs on 64-bit CPUs (x32 on x86_64, n32... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/4e7379e94894 changeset: 15707:4e7379e94894c4434688ff2f09a10dd38cef07e2 user: Bruno Haible <br...@cl...> date: 2016-11-13 22:10:24 +0100 description: Prepare for ILP32 ABIs on 64-bit CPUs (x32 on x86_64, n32 on MIPS64). diffstat: src/ChangeLog | 16 ++++ src/dfloat.d | 184 ++++++++++++++++++++++++++++---------------------------- src/flo_konv.d | 24 +++--- src/flo_rest.d | 4 +- src/intsqrt.d | 2 +- src/lisparit.d | 12 +- src/lispbibl.d | 16 ++++- 7 files changed, 143 insertions(+), 115 deletions(-) ------------------------------ Message: 5 Date: Sun, 13 Nov 2016 21:45:37 +0000 From: cli...@li... Subject: clisp: Add support for Linux/x32 ABI on x86_64. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/261f6593085b changeset: 15708:261f6593085bdc9d4912fc8e50cfcb23375329a8 user: Bruno Haible <br...@cl...> date: 2016-11-13 22:21:21 +0100 description: Add support for Linux/x32 ABI on x86_64. diffstat: src/ChangeLog | 8 ++++++++ src/lispbibl.d | 25 ++++++++++++++++++------- 2 files changed, 26 insertions(+), 7 deletions(-) ------------------------------ Message: 6 Date: Sun, 13 Nov 2016 21:45:38 +0000 From: cli...@li... Subject: clisp: Reduce portability effort for yet unknown 64-bit platforms. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/1997fe33b144 changeset: 15709:1997fe33b14482eb4ccc238539938f88b39a92be user: Bruno Haible <br...@cl...> date: 2016-11-13 22:33:02 +0100 description: Reduce portability effort for yet unknown 64-bit platforms. diffstat: src/ChangeLog | 8 ++++++++ src/lispbibl.d | 11 ++++++++--- 2 files changed, 16 insertions(+), 3 deletions(-) ------------------------------ Message: 7 Date: Sun, 13 Nov 2016 21:45:40 +0000 From: cli...@li... Subject: clisp: Define known facts for more CPUs. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/536a48a91754 changeset: 15710:536a48a91754ec1c9339f1da3b88e9dbd48af6e9 user: Bruno Haible <br...@cl...> date: 2016-11-13 22:42:40 +0100 description: Define known facts for more CPUs. diffstat: src/ChangeLog | 8 +++++ src/lispbibl.d | 81 +++++++++++++++++++++++++++++++++------------------------ 2 files changed, 55 insertions(+), 34 deletions(-) ------------------------------ Message: 8 Date: Sun, 29 Jan 2017 19:15:11 +0000 From: cli...@li... Subject: clisp: common-lisp-hyperspec: with prefix arg, insert the URL in... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/2e56ecbfd823 changeset: 15711:2e56ecbfd8238769f6efd81b7c26a760e3f7baf0 user: Sam Steingold <sd...@gn...> date: 2017-01-29 14:01:07 -0500 description: common-lisp-hyperspec: with prefix arg, insert the URL instead of visiting it diffstat: emacs/clhs.el | 12 ++++++++---- 1 files changed, 8 insertions(+), 4 deletions(-) ------------------------------ Message: 9 Date: Sun, 29 Jan 2017 19:15:12 +0000 From: cli...@li... Subject: clisp: common-lisp-hyperspec-root: default to http://clhs.lisp.s... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/cf881ba831cd changeset: 15712:cf881ba831cd82f9f69c089920e2f13c8d66029c user: Sam Steingold <sd...@gn...> date: 2017-01-29 14:01:40 -0500 description: common-lisp-hyperspec-root: default to http://clhs.lisp.se/ instead of LW diffstat: emacs/clhs.el | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) ------------------------------ Message: 10 Date: Sun, 29 Jan 2017 19:15:13 +0000 From: cli...@li... Subject: clisp: Use malloc instead of alloca for large number of sub expr... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/d7d370401772 changeset: 15713:d7d370401772fb4f86b89f4125625048080dcea6 user: Daniel Jour <dan...@gm...> date: 2017-01-29 14:14:53 -0500 description: Use malloc instead of alloca for large number of sub expressions in regex pattern to avoid stack overflow diffstat: modules/regexp/regexi.c | 21 +++++++++++++++++---- 1 files changed, 17 insertions(+), 4 deletions(-) ------------------------------ Message: 11 Date: Sun, 29 Jan 2017 22:35:56 +0000 From: cli...@li... Subject: clisp: SF mail archives use a completely new system; Gmane/HTTP ... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/0ec9f64a48e7 changeset: 15714:0ec9f64a48e75843e488f195d0ac98efb06dafa0 user: Sam Steingold <sd...@gn...> date: 2017-01-29 17:35:38 -0500 description: SF mail archives use a completely new system; Gmane/HTTP is dead Add elisp functions clisp-goto-gmane-url and clisp-get-gmane-article to get the archives from Gmane/NNTP. Remove the sfmail transformation (maybe replace with another in the future?) Add an explicit link to archive for every dead Gmane/HTTP link (and kill the links which are also dead in Gmane/NNTP). diffstat: doc/clisp.xml.in | 3 +-- doc/common.xsl | 24 +++++------------------- doc/faq.xml | 20 +++++++++----------- doc/impext.xml | 10 +++++----- doc/impnotes.xml.in | 3 +-- doc/man.xsl | 2 -- emacs/misc.el | 25 +++++++++++++++++++++++++ 7 files changed, 46 insertions(+), 41 deletions(-) ------------------------------ Message: 12 Date: Mon, 30 Jan 2017 00:30:05 +0000 From: cli...@li... Subject: clisp: Fix build problem on 32-bit platforms, introduced on 2016... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/130e74c8ea17 changeset: 15715:130e74c8ea17815e9194ad08ecfa0c4d7c63116a user: Bruno Haible <br...@cl...> date: 2017-01-30 01:29:38 +0100 description: Fix build problem on 32-bit platforms, introduced on 2016-11-13. diffstat: src/ChangeLog | 7 +++++++ src/dfloat.d | 2 +- 2 files changed, 8 insertions(+), 1 deletions(-) ------------------------------ Message: 13 Date: Wed, 08 Feb 2017 17:53:34 +0000 From: cli...@li... Subject: clisp: common-lisp-hyperspec: with prefix arg, save URL in kill-... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/3ebf2a75684a changeset: 15716:3ebf2a75684a34fad8488b6fc465b7f18c2f2760 user: Sam Steingold <sd...@po...> date: 2017-02-08 12:52:49 -0500 description: common-lisp-hyperspec: with prefix arg, save URL in kill-ring diffstat: emacs/clhs.el | 11 ++++++----- 1 files changed, 6 insertions(+), 5 deletions(-) ------------------------------ Message: 14 Date: Wed, 08 Feb 2017 17:53:36 +0000 From: cli...@li... Subject: clisp: fix hanging (disassemble 'car) on Mac OS X To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/e3f660ae8fca changeset: 15717:e3f660ae8fcabbbdedbd6fa4ca879998c3228185 user: Sam Steingold <sd...@po...> date: 2017-02-08 12:53:17 -0500 description: fix hanging (disassemble 'car) on Mac OS X * src/spvw.d (init_symbol_values) [UNIX_MACOSX]: Set SYS::*DISASSEMBLE-USE-LIVE-PROCESS* to NIL because otherwise DISASSEMBLE hangs CLISP. diffstat: src/ChangeLog | 8 +++++++- src/spvw.d | 4 ++-- 2 files changed, 9 insertions(+), 3 deletions(-) ------------------------------ Message: 15 Date: Mon, 20 Feb 2017 17:16:45 +0000 From: cli...@li... Subject: clisp: Support the standard way of building GNU packages. To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/3c97f324ee39 changeset: 15718:3c97f324ee39df357cf9fb7a3f7d6ee68bc17898 user: Bruno Haible <br...@cl...> date: 2017-02-19 11:25:42 +0100 description: Support the standard way of building GNU packages. diffstat: Makefile.devel | 2 +- Makefile.in | 44 ++++++++++++++++++++++++++++++++++++++++++++ src/ChangeLog | 8 ++++++++ src/configure | 37 ++++++++++++++++++++++++++++++++++++- src/configure.in | 4 ++++ 5 files changed, 93 insertions(+), 2 deletions(-) ------------------------------ Message: 16 Date: Mon, 20 Feb 2017 17:16:46 +0000 From: cli...@li... Subject: clisp: Fix build failure when --with-libsigsegv-prefix option is... To: cli...@li... Message-ID: <hg....@sf...> Content-Type: text/plain; charset="us-ascii" details: http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/9233681ce078 changeset: 15719:9233681ce0789c04f912c0629192b37144859ee0 user: Bruno Haible <br...@cl...> date: 2017-02-19 12:05:57 +0100 description: Fix build failure when --with-libsigsegv-prefix option is used. diffstat: src/ChangeLog | 8 ++++++++ src/makemake.in | 2 +- 2 files changed, 9 insertions(+), 1 deletions(-) ------------------------------ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ------------------------------ _______________________________________________ clisp-cvs mailing list cli...@li... https://lists.sourceforge.net/lists/listinfo/clisp-cvs End of clisp-cvs Digest, Vol 74, Issue 1 **************************************** |
|
From: Bruno H. <br...@cl...> - 2017-02-08 21:41:45
|
> clang: warning: optimization flag '-falign-functions=4' is not supported Now, this could cause verify_code_alignment() to fail. If it doesn't fail, clang probably puts functions at 4-bytes boundaries anyway. Bruno |
|
From: Bruno H. <br...@cl...> - 2017-02-08 21:38:12
|
Hi Sam, > ../src/debug.d:571:7: warning: shifting a negative signed value is undefined > [-Wshift-negative-value] > > $ gcc --version > Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/c++/4.2.1 > Apple LLVM version 8.0.0 (clang-800.0.42.1) http://stackoverflow.com/questions/3784996/why-does-left-shift-operation-invoke-undefined-behaviour-when-the-left-side-oper does not give me any insight about the real reasons of the warning. Generally, some operations on signed integers now give undefined behaviour, and some compilers like GCC exploit this. So, it is nowadays generally wiser to do bit manipulations only on unsigned integers. I guess it will be a lot of work to revisit clisp's code in this direction. The first step towards this is to pick the relevant warnings. So far, I'd guess that -Wshift-negative-value is not among the relevant warnings. Bruno |
|
From: Sam S. <sd...@gn...> - 2017-02-08 18:50:59
|
also clang: warning: optimization flag '-falign-functions=4' is not supported On Wed, Feb 8, 2017 at 1:28 PM, Sam Steingold <sd...@gn...> wrote: > Hi Bruno, > > is this benign? > > --8<---------------cut here---------------start------------->8--- > ../src/debug.d:571:7: warning: shifting a negative signed value is undefined > [-Wshift-negative-value] > dynamic_unbind(S(standard_input)); > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ../src/lispbibl.d:12811:5: note: expanded from macro 'dynamic_unbind' > dynamic_unbind_g(); \ > ^~~~~~~~~~~~~~~~~~ > ../src/lispbibl.d:12804:3: note: expanded from macro 'dynamic_unbind_g' > CHECK_DYNBIND; \ > ^~~~~~~~~~~~~ > ../src/lispbibl.d:12798:53: note: expanded from macro 'CHECK_DYNBIND' > if (!((as_oint(STACK_0) & wbit(frame_bit_o)) && framecode(STACK_0))) \ > ^~~~~~~~~~~~~~~~~~ > ../src/lispbibl.d:12318:59: note: expanded from macro 'framecode' > #define framecode(bottomword) (as_oint(bottomword) & minus_wbit(FB1)) > ^~~~~~~~~~~~~~~ > ../src/lispbibl.d:3042:23: note: expanded from macro 'minus_wbit' > #define minus_wbit minus_bit > ^ > ../src/lispbibl.d:1195:27: note: expanded from macro 'minus_bit' > #define minus_bit(n) (-1L<<(n)) > ~~~^ > --8<---------------cut here---------------end--------------->8--- > > Darwin 16.4.0 Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64 x86_64 > > $ gcc --version > Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/c++/4.2.1 > Apple LLVM version 8.0.0 (clang-800.0.42.1) > Target: x86_64-apple-darwin16.4.0 > Thread model: posix > InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin > > > > -- > Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504 > http://steingoldpsychology.com http://www.childpsy.net https://ffii.org > http://iris.org.il http://islamexposedonline.com http://memri.org > Shady characters are often very bright. -- Sam Steingold <http://sds.podval.org> <http://www.childpsy.net> <http://steingoldpsychology.com> |
|
From: Sam S. <sd...@gn...> - 2017-02-08 18:28:49
|
Hi Bruno,
is this benign?
--8<---------------cut here---------------start------------->8---
../src/debug.d:571:7: warning: shifting a negative signed value is undefined
[-Wshift-negative-value]
dynamic_unbind(S(standard_input));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/lispbibl.d:12811:5: note: expanded from macro 'dynamic_unbind'
dynamic_unbind_g(); \
^~~~~~~~~~~~~~~~~~
../src/lispbibl.d:12804:3: note: expanded from macro 'dynamic_unbind_g'
CHECK_DYNBIND; \
^~~~~~~~~~~~~
../src/lispbibl.d:12798:53: note: expanded from macro 'CHECK_DYNBIND'
if (!((as_oint(STACK_0) & wbit(frame_bit_o)) && framecode(STACK_0))) \
^~~~~~~~~~~~~~~~~~
../src/lispbibl.d:12318:59: note: expanded from macro 'framecode'
#define framecode(bottomword) (as_oint(bottomword) & minus_wbit(FB1))
^~~~~~~~~~~~~~~
../src/lispbibl.d:3042:23: note: expanded from macro 'minus_wbit'
#define minus_wbit minus_bit
^
../src/lispbibl.d:1195:27: note: expanded from macro 'minus_bit'
#define minus_bit(n) (-1L<<(n))
~~~^
--8<---------------cut here---------------end--------------->8---
Darwin 16.4.0 Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64 x86_64
$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/c++/4.2.1
Apple LLVM version 8.0.0 (clang-800.0.42.1)
Target: x86_64-apple-darwin16.4.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net https://ffii.org
http://iris.org.il http://islamexposedonline.com http://memri.org
Shady characters are often very bright.
|
|
From: Bruno H. <br...@cl...> - 2017-01-30 00:48:58
|
Hi Jerry, > I just attempted to update the Fedora clisp package to mercurial head > and found that 32-bit platforms fail to compile. When attempting to > link lisp.run, this error occurs: > > lisparit.o: In function `DF_DF_mult_DF': > /builddir/build/BUILD/clisp-2.49/build/../src/dfloat.d:926: undefined > reference to `bitQ' > lisparit.o: In function `DF_DF_mult_DF': > lisparit.c:(.text+0x65f3): undefined reference to `bitQ' > lisparit.c:(.text+0x6627): undefined reference to `bitQ' > lisparit.c:(.text+0x66d1): undefined reference to `bitQ' > lisparit.c:(.text+0x6701): undefined reference to `bitQ' > collect2: error: ld returned 1 exit status > make: *** [Makefile:1405: lisp.run] Error 1 Oops. Thanks for reporting this. I have now pushed the (tiny) fix. > This error appears to have been introduced with this commit: > > changeset: 15707:4e7379e94894 > user: Bruno Haible <br...@cl...> > date: Sun Nov 13 22:10:24 2016 +0100 > summary: Prepare for ILP32 ABIs on 64-bit CPUs (x32 on x86_64, n32 > on MIPS64). Yes, this is correct. It was me. > It looks like bitQ is defined as a macro inside lispbibl.d, but only inside: > > #if (long_bitsize==64) || defined(DECALPHA) || defined(MIPS64) || defined(SPARC6 > 4) || defined(IA64) || defined(AMD64) > > Note that there is no corresponding definition inside the #else part. > Note also, though, that many 32-bit platforms do have a 64-bit type, > but it may be long long, instead of long. Yes, the intQ stuff is only meant to be used on 64-bit platforms. It _could_ maybe compile on 32-bit platforms with 'long long' support (which by now nearly every compiler has, except Microsoft of course), but I guess that the hand-written code which uses only intD or intL is more efficient for the 32-bit platforms. Bruno |
|
From: Jerry J. <log...@gm...> - 2017-01-28 21:56:14
|
Greetings, I just attempted to update the Fedora clisp package to mercurial head and found that 32-bit platforms fail to compile. When attempting to link lisp.run, this error occurs: lisparit.o: In function `DF_DF_mult_DF': /builddir/build/BUILD/clisp-2.49/build/../src/dfloat.d:926: undefined reference to `bitQ' lisparit.o: In function `DF_DF_mult_DF': lisparit.c:(.text+0x65f3): undefined reference to `bitQ' lisparit.c:(.text+0x6627): undefined reference to `bitQ' lisparit.c:(.text+0x66d1): undefined reference to `bitQ' lisparit.c:(.text+0x6701): undefined reference to `bitQ' collect2: error: ld returned 1 exit status make: *** [Makefile:1405: lisp.run] Error 1 This error appears to have been introduced with this commit: changeset: 15707:4e7379e94894 user: Bruno Haible <br...@cl...> date: Sun Nov 13 22:10:24 2016 +0100 summary: Prepare for ILP32 ABIs on 64-bit CPUs (x32 on x86_64, n32 on MIPS64). It looks like bitQ is defined as a macro inside lispbibl.d, but only inside: #if (long_bitsize==64) || defined(DECALPHA) || defined(MIPS64) || defined(SPARC6 4) || defined(IA64) || defined(AMD64) Note that there is no corresponding definition inside the #else part. Note also, though, that many 32-bit platforms do have a 64-bit type, but it may be long long, instead of long. I tried adding "|| (longlong_bitsize==64)" to that #if, but it didn't work. I'm not sure why. In any case, all of Fedora's 32-bit architectures have a native 64-bit integer, so I'm removing the #if and the entire #else part as a workaround for now. Regards, -- Jerry James http://www.jamezone.org/ |
|
From: Blake M. <bl...@mc...> - 2017-01-23 11:14:39
|
On Tue, Jan 10, 2017 at 4:28 PM, Pascal Bourguignon <pj...@in...> wrote: > > On 10 Jan 2017, at 22:16, Sam Steingold <sd...@gn...> wrote: > > > You mean, "the problem is surface rather than content". > I agree. > > However, there is a Russian proverb: "One is greeted according to one's > dress, one is sent off according to one's intelligence". > Yes, intelligence (=="substance") is more important, but if you wear > rugs, people won't even talk to you and will never discover your > intelligence. > > I think we need to drop the gratuitous preprocessors (varbrace & > comment5) and rename all files to *.c. > We need to preprocess them into *.m.c behind the scenes. > lisbpbibl.d should be lisbpbibl.h and not preprocessed. > &c. > > > Well, I both agree and disagree. > > > Pure C code is good, and it would be great for portability, if one could > write 100% purely standard C11 code. > Like, no trick like libsigsegv, or worse ffcall/avcall which can never be > compiled on new or exotic systems. > Just pure standard entirely defined behavior C11 code. > > I’d like that. > Making the base source straight C is the first step IMO. Having a version that is straight C11 is the second step! Having system specific code to add facilities and speed is fine so long as it is ifdef'ed so as not required. > > You’d not like it at all, because it might imply a performance hit. > (Probably a serious performance hit > even, if you want to implement all the features we have). > > > > > On the other hand, I’m not sure the solution is to go toward C. Why not > write lisp code, and have a > translator that generates some throw away intermediary C code, that can be > compiled anywhere? > That would be great. > > > Recently compiled a project that was build this way: > https://github.com/aoh/radamsa > It’s actually written in Scheme, and it uses OL ( > https://github.com/aoh/owl-lisp/files/449350) a scheme to C translator, > to generate the C code that is then compiled. Since OL itself is written > in scheme, and applied on itself to produce the C sources > that are distributed. So you have a 100% C bootstrap path. > > On the other hand, you can implement the software in a high level > programming language. > Either of these is fine, but I fear we are beginning to talk about a whole new version. Not needed. Blake |
|
From: Blake M. <bl...@mc...> - 2017-01-23 11:07:39
|
On Tue, Jan 10, 2017 at 3:16 PM, Sam Steingold <sd...@gn...> wrote: > > > What exactly is the problem with the .d files? > > They scare and confuse a newcomer. > Exactly. Regardless of what I *can* do, I, like most, have limited time to work on non-work/fun stuff. The .d file syntax represents a barrier to entry, if you will. > > Compare them with the C files in Emacs. > > They also have crazy DEFUN and DEFVAR macros (CLISP has LISPFUN* in core > and DEFUN in modules), but the simple fact that they are called *.c and > do not use gratuitous syntax alterations like "#" comments and "var" > prefixes makes them much more palatable. > > I bet that if we rename *.d to *.c and remove varbrace and comment5 > preprocessors, the whole conversation will go away. > Yes, indeed. > > ... > > > CLISP is not the only project that puts the preprocessor to fancy uses. > > Yes, but CLISP is the only project which does gratuitous syntax > modifications. > Yes, and that's the problem. > ..... > > I think we need to drop the gratuitous preprocessors (varbrace & > comment5) and rename all files to *.c. > We need to preprocess them into *.m.c behind the scenes. > lisbpbibl.d should be lisbpbibl.h and not preprocessed. > &c. > Making it look like straight C would help a lot, IMO. Thank you. Blake McBride |
|
From: Vladimir T. <vtz...@gm...> - 2017-01-17 20:42:55
|
Thanks for the report. Will have a look into this soon. -- vlad On Tue, Jan 17, 2017 at 5:45 PM, Don Cohen <don...@is...> wrote: > > > [1]> (defun f()(f)) > F > [2]> (f) > > *** - Lisp stack overflow. RESET > [3]> (mt:make-thread (lambda()(sleep 99)) :name "wait") > #<THREAD "wait"> > [4]> (f) > > *** - Lisp stack overflow. RESET > [5]> (mt::list-threads) > (#<THREAD "wait"> #<THREAD "main thread">) > [6]> (mt:make-thread (lambda()(f) "done") :name "wait") > #<THREAD "wait"> > [7]> Segmentation fault > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > clisp-devel mailing list > cli...@li... > https://lists.sourceforge.net/lists/listinfo/clisp-devel |
|
From: <don...@is...> - 2017-01-17 16:02:22
|
[1]> (defun f()(f)) F [2]> (f) *** - Lisp stack overflow. RESET [3]> (mt:make-thread (lambda()(sleep 99)) :name "wait") #<THREAD "wait"> [4]> (f) *** - Lisp stack overflow. RESET [5]> (mt::list-threads) (#<THREAD "wait"> #<THREAD "main thread">) [6]> (mt:make-thread (lambda()(f) "done") :name "wait") #<THREAD "wait"> [7]> Segmentation fault |
|
From: Sam S. <sd...@gn...> - 2017-01-12 15:28:59
|
> * Pascal Bourguignon <cwo@vasbezngvzntb.pbz> [2017-01-10 23:28:25 +0100]: > >> On 10 Jan 2017, at 22:16, Sam Steingold <sd...@gn...> wrote: >> >> I think we need to drop the gratuitous preprocessors (varbrace & >> comment5) and rename all files to *.c. >> We need to preprocess them into *.m.c behind the scenes. >> lisbpbibl.d should be lisbpbibl.h and not preprocessed. >> &c. > > Well, I both agree and disagree. > > > Pure C code is good, and it would be great for portability, if one could > write 100% purely standard C11 code. I never proposed removing assembly &c. > Like, no trick like libsigsegv, or worse ffcall/avcall which can never > be compiled on new or exotic systems. > Just pure standard entirely defined behavior C11 code. I am certainly not proposing that. If you look at a previous message, I explain the gctrigger preprocessor and why it is desirable. What I am opposed to is "gratuitous syntax modifications". -- Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504 http://steingoldpsychology.com http://www.childpsy.net https://jihadwatch.org http://camera.org http://www.dhimmitude.org http://iris.org.il Do not worry about which side your bread is buttered on: you eat BOTH sides. |
|
From: Pascal B. <pj...@in...> - 2017-01-10 22:28:36
|
> On 10 Jan 2017, at 22:16, Sam Steingold <sd...@gn...> wrote: > > > You mean, "the problem is surface rather than content". > I agree. > > However, there is a Russian proverb: "One is greeted according to one's > dress, one is sent off according to one's intelligence". > Yes, intelligence (=="substance") is more important, but if you wear > rugs, people won't even talk to you and will never discover your > intelligence. > > I think we need to drop the gratuitous preprocessors (varbrace & > comment5) and rename all files to *.c. > We need to preprocess them into *.m.c behind the scenes. > lisbpbibl.d should be lisbpbibl.h and not preprocessed. > &c. Well, I both agree and disagree. Pure C code is good, and it would be great for portability, if one could write 100% purely standard C11 code. Like, no trick like libsigsegv, or worse ffcall/avcall which can never be compiled on new or exotic systems. Just pure standard entirely defined behavior C11 code. I’d like that. You’d not like it at all, because it might imply a performance hit. (Probably a serious performance hit even, if you want to implement all the features we have). On the other hand, I’m not sure the solution is to go toward C. Why not write lisp code, and have a translator that generates some throw away intermediary C code, that can be compiled anywhere? Recently compiled a project that was build this way: https://github.com/aoh/radamsa <https://github.com/aoh/radamsa> It’s actually written in Scheme, and it uses OL (https://github.com/aoh/owl-lisp/files/449350 <https://github.com/aoh/owl-lisp/files/449350>) a scheme to C translator, to generate the C code that is then compiled. Since OL itself is written in scheme, and applied on itself to produce the C sources that are distributed. So you have a 100% C bootstrap path. On the other hand, you can implement the software in a high level programming language. -- __Pascal J. Bourguignon__ |
|
From: Sam S. <sd...@gn...> - 2017-01-10 21:16:08
|
> * <Wbret-Plevy.Ubruyr@g-flfgrzf.pbz> [2017-01-10 12:48:40 +0000]: > > Blake McBride wrote: > >>As a person with more than 25 years C experience, approaching the .d files >>is an unnecessary barrier. When a C programmer wants to look at CLISP, the >>first thing he sees is this wacko, foreign .d stuff. I'd say: > >>Use as many macros as needed, but don't use .d files and processors. > Python and Java have annotations which are truly a means to preprocess the > code before it goes through the regular, old fashioned compiler. and OCaml too. > Why not do the same with C? Because nobody else does it? yep. > What exactly is the problem with the .d files? They scare and confuse a newcomer. Compare them with the C files in Emacs. They also have crazy DEFUN and DEFVAR macros (CLISP has LISPFUN* in core and DEFUN in modules), but the simple fact that they are called *.c and do not use gratuitous syntax alterations like "#" comments and "var" prefixes makes them much more palatable. I bet that if we rename *.d to *.c and remove varbrace and comment5 preprocessors, the whole conversation will go away. > Is it a matter of tool support, e.g. your favourite editor not able to > perform syntax highlighting? clisp comes with https://sourceforge.net/p/clisp/clisp/ci/tip/tree/emacs/d-mode.el > CLISP is not the only project that puts the preprocessor to fancy uses. Yes, but CLISP is the only project which does gratuitous syntax modifications. > IOW, the problem is not surface rather than content. You mean, "the problem is surface rather than content". I agree. However, there is a Russian proverb: "One is greeted according to one's dress, one is sent off according to one's intelligence". Yes, intelligence (=="substance") is more important, but if you wear rugs, people won't even talk to you and will never discover your intelligence. I think we need to drop the gratuitous preprocessors (varbrace & comment5) and rename all files to *.c. We need to preprocess them into *.m.c behind the scenes. lisbpbibl.d should be lisbpbibl.h and not preprocessed. &c. -- Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504 http://steingoldpsychology.com http://www.childpsy.net https://ffii.org http://www.memritv.org http://www.dhimmitude.org http://islamexposedonline.com Someone has changed your life. Save? (y/n) |
|
From: <Joe...@t-...> - 2017-01-10 12:48:50
|
Hi, Blake McBride wrote: >As a person with more than 25 years C experience, approaching the .d files >is an unnecessary barrier. When a C programmer wants to look at CLISP, the >first thing he sees is this wacko, foreign .d stuff. I'd say: >Use as many macros as needed, but don't use .d files and processors. Python and Java have annotations which are truly a means to preprocess the code before it goes through the regular, old fashioned compiler. Why not do the same with C? Because nobody else does it? What exactly is the problem with the .d files? Is it a matter of tool support, e.g. your favourite editor not able to perform syntax highlighting? Would it be better if // was used to introduce line comments? Then rename the files to .c (still preprocessing them)? CLISP is not the only project that puts the preprocessor to fancy uses. >It's like having to learn a new language. I fail to see the problem. As you have 25 years of experience with C, I'd guess you have learned a gazillion many languages since then (e.g. Makefile, configure, whatever). Isn't the problem, fundamentally, not the suffix .c or .d but rather the unusual job of programming a stack machine, i.e. program a little Forth, while within the syntax of C? My feeling has always been that what makes writing C code in CLISP difficult is to get the pushSTACK() and pops right, and never spill a value. Like with Forth, what becomes important to document in comments is the state of the stack (esp. ToS) before and after execution of a function. (other things are: understand the different stack frames and learn when to use which one, understand the dozen different array formats and how to dispatch them correctly based on a discrimination tree, etc.) IOW, the problem is not surface rather than content. Regards, Jörg Höhle |
|
From: Blake M. <bl...@mc...> - 2017-01-04 01:46:20
|
On Tue, Jan 3, 2017 at 9:20 AM, Sam Steingold <sd...@gn...> wrote: > > * Blake McBride [2017-01-01 11:19:41 -0600]: > ..... > > > > 2. With macros, clean up the .c files so that they are more reasonable. > > Easier said than done. > I mean, I would love to see that happen (and I have argued for that for > years), but it is harder than it seems at the first glance. > ....... > We welcome your contributions. > I am surprised by the positive feedback. I may do it. --blake |
|
From: Sam S. <sd...@gn...> - 2017-01-03 15:20:56
|
> * Blake McBride <oy...@zp...zr> [2017-01-01 11:19:41 -0600]:
>
> I think step 1 is as follows. Get rid of the .d files! Start with .c
> files. Use as many macros as needed, but don't use .d files and
> processors. As a person with more than 25 years C experience, approaching
> the .d files is an unnecessary barrier. When a C programmer wants to look
> at CLISP, the first thing he sees is this wacko, foreign .d stuff. It's
> like having to learn a new language. I'd say:
>
> 1. Run it through all of the preprocessors to convert all of the .d files
> to .c files
>
> 2. With macros, clean up the .c files so that they are more reasonable.
Easier said than done.
I mean, I would love to see that happen (and I have argued for that for
years), but it is harder than it seems at the first glance.
CLISP has several pre-processors, and, while converting "# " comments is
trivial and inserting "{}" for "var" marker is no longer necessary,
"gctrigger" is different.
When a function is marked "maygc" in foo.d (i.e., it can trigger GC),
the foo.c will contain code to invalidate all data:
--8<---------------cut here---------------start------------->8---
maygc void foo (int x, object a, float y, object b) {
...
}
--8<---------------cut here---------------end--------------->8---
turns into
--8<---------------cut here---------------start------------->8---
maygc void foo (int x, object a, float y, object b) {
GCTRIGGER2(a,b);
...
}
--8<---------------cut here---------------end--------------->8---
Do we really want to make the programmer write GCTRIGGERx(...) instead
of maygc?
It's not just the number of characters to type.
It's having to list `object` arguments _twice_.
This redundancy is, IMO, a strong argument in favor of a pre-processor.
However, the question is more of http://www.cygwin.com/acronyms/#SHTDI,
compounded by this trajectory:
* Obviously, we cannot give Bob (who just volunteered to rid us of the
pre-processors) write access to the repo - he doesn't know what he is
doing, he is likely to mess up things and leave them broken &c.
* We ask Bob to prove that he is actually committed to CLISP - by doing
some minor work, which will also ensure that he understands the code
base and will not make trivial mistakes.
* Now that he proved himself, we might actually give him free hand - but
Bob now has more interesting CLISP stuff in mind, he is no longer
excited by the perspective of hand-editing 100+ *.d files.
I do not mean to discourage you though.
We welcome your contributions.
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net
http://mideasttruth.com http://thereligionofpeace.com http://no2bds.org
Don't be afraid of happiness. It does not exist.
|
32 messages has been excluded from this view by a project administrator.
