clisp-devel — closed list for developers and testers

Re: (sxhash (make-instance 'ext:standard-stablehash)) => 3614431684

[Bruno H. <br...@cl...>]

Hi Sam,

> I understand that SXHASH is not guaranteed to be different for different
> instances:
> 
> --8<---------------cut here---------------start------------->8---
> > (sxhash (make-instance 'ext:standard-stablehash))
> 3614431684
> > (sxhash (make-instance 'ext:standard-stablehash))
> 3614431684
> > (sxhash (make-instance 'ext:structure-stablehash))
> 83368493
> > (sxhash (make-instance 'ext:structure-stablehash))
> 83368493
> --8<---------------cut here---------------end--------------->8---
> 
> However, it seems like it _could_ do better.

Yes, it is conceivable that SXHASH looks into instances of
STANDARD-OBJECT or STRUCTURE-OBJECT, with a limited depth.

The depth limit should not be larger than 1, because when you have an object
with 100 slots, you don't want SXHASH to walk over 10000 objects.

And the recursion must be bounded, like we do in hashcode_tree, so that
we don't run into an endless recursion when given an object that contains
a reference to itself:   #1= #S(FOO #1#)
Or like this:            #1= #S(FOO (#1#))

> This brings another question:
> why is sxhash_atom different from hashcode3stable_atom?

SXHASH does not distribute the hash values well (i.e. it is of bad quality),
because of the requirement that it must not depend on the addresses of the
objects in memory. For example, the following pairs of objects have the
same SXHASH hash code:
  A::FOO  B::FOO
  (X)       (Y)             ; because of (SETF CDR)
  #(X)      #(Y)            ; because of (SETF AREF)
  #S(FOO X) #S(FOO Y)       ; because of (SETF SYS::%STRUCTURE-REF)

hashcode3stable_atom does not have this requirement and therefore can
produce better results, faster.

Bruno

(sxhash (make-instance 'ext:standard-stablehash)) => 3614431684

[Sam S. <sd...@gn...>]

Hi Bruno,

I understand that SXHASH is not guaranteed to be different for different
instances:

--8<---------------cut here---------------start------------->8---
> (sxhash (make-instance 'ext:standard-stablehash))
3614431684
> (sxhash (make-instance 'ext:standard-stablehash))
3614431684
> (sxhash (make-instance 'ext:structure-stablehash))
83368493
> (sxhash (make-instance 'ext:structure-stablehash))
83368493
--8<---------------cut here---------------end--------------->8---

However, it seems like it _could_ do better.

This brings another question:
why is sxhash_atom different from hashcode3stable_atom?

Thanks.

--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1561
http://steingoldpsychology.com http://www.childpsy.net https://ffii.org
http://thereligionofpeace.com http://honestreporting.com http://jij.org
If brute force does not work, you are not using enough.

Re: NEWS file format

[Bruno H. <br...@cl...>]

Sam wrote:
> > Should we convert the new part (2.50 and newer) of the NEWS file to this
> > format ...
> No.

OK.

Bruno

Re: make check fails

[<don...@is...>]

Under make check, I think all of this I've reported before.
The permission problems go away when run as root.
  $  cat /home/don/hg/clisp/build-dir/tests/*.erg
  Form: (HANDLER-CASE (LETF ((*CURRENT-LANGUAGE* 'FRENCH)) (LIST (STRING= "À bientôt!" (SYSTEM::TEXT "Bye.")) (STRING= *CURRENT-LANGUAGE* "FRANÇAIS"))) (ERROR (E) (PRINC-ERROR E) '(T T)))
  CORRECT: (T T)
  CLISP  : (NIL T)
  Differ at position 0: T vs NIL
  CORRECT: (T T)
  CLISP  : (NIL T)


  Form: (WITH-OPEN-FILE (COPY S) (STREAMP COPY))
  CORRECT: T
  CLISP  : ERROR
  OS-FILE-ERROR(13): Permission denied
  OUT:
  "[OS-FILE-ERROR]: OS-FILE-ERROR(13): Permission denied
  "


  Form: (LET ((*REOPEN-OPEN-FILE* NIL)) (WITH-OPEN-FILE (COPY S :DIRECTION :OUTPUT) (STREAMP COPY)))
  CORRECT: T
  CLISP  : ERROR
  OS-FILE-ERROR(13): Permission denied
  OUT:
  "[OS-FILE-ERROR]: OS-FILE-ERROR(13): Permission denied
  "


  [2018-01-12 07:46:39 don@number15 ~/hg/clisp/build-dir]
  $ 

However, mod-check ends with
finished   4 files:             298 errors out of     632 tests
  1             i18n/test.tst:    0 errors out of      11 tests
  2         syscalls/test.tst:    3 errors out of     264 tests
  3           regexp/test.tst:  295 errors out of     320 tests
  4         readline/test.tst:    0 errors out of      37 tests
Bye.
Makefile:2403: recipe for target 'base-mod-check' failed
make: *** [base-mod-check] Error 1

Most of the regexp errors seem to be
[SIMPLE-TYPE-ERROR]: FINALIZE: #<ADDRESS #x0000000000911C30> is not a function

  $ cat /home/don/hg/clisp/build-dir/syscalls/test.erg
  Form: (LET ((DIR "syscalls-tests-dir/") (DEST "qwer/adsf") COPY) (WHEN (NTH-VALUE 1 (ENSURE-DIRECTORIES-EXIST DIR :VERBOSE T)) (MAPC #'DELETE-FILE (DIRECTORY (CONCATENATE 'STRING DIR "**") :IF-DOES-NOT-EXIST :KEEP))) (SETQ COPY (COPY-FILE DEST DIR :METHOD :SYMLINK)) (LIST (STRING= DEST (CAAR COPY)) (STRING= (PATHNAME-NAME DEST) (PATHNAME-NAME (DELETE-FILE (CADAR COPY)))) (DELETE-DIRECTORY DIR) (PROBE-PATHNAME DIR)))
  CORRECT: (T T T NIL)
  CLISP  : ERROR
  OS-FILE-ERROR(ENOENT): No such file or directory
  OUT:
  "Creating directory: /home/don/hg/clisp/build-dir/syscalls-tests-dir/
  [OS-FILE-ERROR]: OS-FILE-ERROR(ENOENT): No such file or directory
  "


  Form: (LET ((DIR "syscalls-tests-dir/") (LINK #P"syscalls-tests-symlink/")) (LIST (MAKE-DIRECTORY DIR) (STRING= DIR (CAAR (COPY-FILE DIR LINK :METHOD :SYMLINK))) (DELETE-DIRECTORY DIR) (DELETE-DIRECTORY LINK)))
  CORRECT: (T T T T)
  CLISP  : ERROR
  OS-FILE-ERROR(EEXIST): File exists
  OUT:
  "[OS-FILE-ERROR]: OS-FILE-ERROR(EEXIST): File exists
  "


  Form: (LET ((DIR "syscalls-tests-dir/") (DEST "foo/bar")) (MAKE-DIRECTORY DIR) (COPY-FILE DEST DIR :METHOD :SYMLINK) (HANDLER-CASE (OR (DELETE-DIRECTORY DIR) (ERROR "deleted non-empty directory")) (OS-ERROR (E) (OR (EQ (OS-ERROR-CODE E) :ENOTEMPTY) (INTEGERP (OS-ERROR-CODE E)) (ERROR "wrong error code: ~s" (OS-ERROR-CODE E))))) (MAPC #'DELETE-FILE (DIRECTORY (CONCATENATE 'STRING DIR "**") :IF-DOES-NOT-EXIST :KEEP)) (DELETE-DIRECTORY DIR))
  CORRECT: T
  CLISP  : ERROR
  OS-FILE-ERROR(EEXIST): File exists
  OUT:
  "[OS-FILE-ERROR]: OS-FILE-ERROR(EEXIST): File exists
  "

Re: NEWS file format

[Sam S. <sd...@gn...>]

> * Bruno Haible <oe...@py...t> [2018-01-12 11:31:33 +0100]:
>
> Should we convert the new part (2.50 and newer) of the NEWS file to this
> format, and add a Makefile.devel rule that generates a NEWS-2.50.html file
> from it? (It's not worth spending time on the parts of this file that
> apply to 2.49 and older.)

No.
The benefit is marginal and the deviation from the common practice is
huge.
News files should be readable as is.
If the standard and simple outline/markdown format is not readable to
you, please do not exacerbate the situation by introducing
preprocessing.


-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1561
http://steingoldpsychology.com http://www.childpsy.net http://mideasttruth.com
http://islamexposedonline.com http://camera.org http://memri.org
Good judgment comes from experience and experience comes from bad judgment.

Re: NEWS file format

[Sam S. <sd...@gn...>]

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2018-01-12 08:53:35 +0100]:
>
>> markdown is widely supported.
>
> Markdown is something else: It's a *shorthand for writing* a text file
> with structure,

md/rst is just a simple next step to outline.

> when it is known that the file will *always be postprocessed*
> (through the Markdown processor) before being presented to user.

nope, I read md/rst in emacs all the time.

> It would be OK with me to have a NEWS.md (or NEWS.xml) in the
> repository,

we already have doc/history.xml.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1561
http://steingoldpsychology.com http://www.childpsy.net
http://think-israel.org http://thereligionofpeace.com http://iris.org.il
A good programmer: language change is easy, editor change is ... huh?!

Re: NEWS file format

[Jean L. <bu...@gn...>]

On Fri, Jan 12, 2018 at 08:53:35AM +0100, Bruno Haible wrote:
> Hi Sam,
> 
> > markdown is widely supported.
> 
> Markdown is something else: It's a *shorthand for writing* a text file
> with structure, when it is known that the file will *always be postprocessed*
> (through the Markdown processor) before being presented to user.
> Which is not the case here: The NEWS file is being included literally
> in the distribution.
> 
> It would be OK with me to have a NEWS.md (or NEWS.xml) in the repository, with
> a NEWS.html alongside it that is always automatically regenerated upon any
> modification of NEWS.{md,xml}.
> But that's probably overkill for 200 lines of text?
> 
> > At any rate, please do not introduce any new idiosyncratic markup there
> > as you did recently.
> 
> I did not introduce a markup. I introduced a kind of visual representation.
> Any other visual representation that satisfies the principle that section
> titles catch the eyes more easily than subsubsection titles would be OK.

Why not simple keep it in text format. If it is
necessary to be as HTML, it can be easily
converted.

One can also keep it in Org format, which is
similar to outline in Emacs, and gives visually
clear sectioning

* Section 1

Text

** Section 2

Text

And it can be converted on command line by using
Emacs to any other format. 

-- 
Jean Louis

Re: NEWS file format

[Bruno H. <br...@cl...>]

Pascal Bourguignon wrote:
> The reStructured Text (rst) format is more adapted for both human reader
> and machine processing.
> The various markdown formats are worse than reStructuredText.

Thanks for the pointer! Yes, I agree, this format is well adapted for
human reading.

Should we convert the new part (2.50 and newer) of the NEWS file to this
format, and add a Makefile.devel rule that generates a NEWS-2.50.html file
from it? (It's not worth spending time on the parts of this file that
apply to 2.49 and older.)

Bruno

Re: NEWS file format

[Pascal B. <pj...@in...>]

> On 11 Jan 2018, at 23:02, Bruno Haible <br...@cl...> wrote:
> 
> Hi Sam,
> 
>> CLISP NEWS file is fairly long (almost 5k lines).
> 
> People usually will want to ignore the news from 2010 and before.
> So, that makes only ca. 200 lines to read.
> 
>> It has "free text" format.
>> I want to convert it to the outline format
>> (https://www.gnu.org/software/emacs/manual/html_node/emacs/Outline-Format.html)
>> which will allow for an easier navigation in Emacs and VIM.
> 
> Please not! I object!
> 
> Rationale:
> 
> 1) This outline format is ill-conceived for reading without special tool
>   support. Namely, the subsubsections stand out brighter than the sections.
>   (The subsubsections have 3 asterisks, vs. 1 asterisk for the sections.)
>   This is just the opposite of what it ought to be. Section titles should
>   stand out more heavily than subsubsections.

I agree.

The reStructured Text (rst) format is more adapted for both human reader and machine processing.
The various markdown formats are worse than reStructuredText.





-- 
__Pascal J. Bourguignon__

Re: File permissions in modules

[Bruno H. <br...@cl...>]

Jean Louis wrote:
> > From development version, after "make install", I
> > get these permissions on files, which makes it
> > impossible to use the postgresql module, I get
> > file permission access.
> > 
> > total 452
> > -rw-r----- 1 root root    299 Jan 11 19:50 link.sh
> > -rw-r----- 1 root root   1120 Jan 11 19:50 Makefile
> > -rw-r----- 1 root root 247456 Jan 11 19:50 postgresql.fas
> > -rw-r--r-- 1 root root  25224 Jan 11 19:50 postgresql.lisp
> > -rw-r----- 1 root root 148808 Jan 11 19:50 postgresql.o
> > -rw-r--r-- 1 root root    528 Jan 11 19:50 README
> > -rw-r----- 1 root root  15492 Jan 11 19:50 sql.fas
> > -rw-r--r-- 1 root root   3197 Jan 11 19:50 sql.lisp
> 
> I found out, this is happening due to building as
> user with different umask, and installing with
> sudo make install.

Yes, "sudo make install" is supported by many GNU packages. Cf. the GNU
standards [1] "This is convenient for building the program under one
user name and installing it under another." But you are right, umask
is something to care about each time you use 'sudo' or 'su'.

Bruno

[1] https://www.gnu.org/prep/standards/html_node/Standard-Targets.html

Re: NEWS file format

[Bruno H. <br...@cl...>]

Hi Sam,

> markdown is widely supported.

Markdown is something else: It's a *shorthand for writing* a text file
with structure, when it is known that the file will *always be postprocessed*
(through the Markdown processor) before being presented to user.
Which is not the case here: The NEWS file is being included literally
in the distribution.

It would be OK with me to have a NEWS.md (or NEWS.xml) in the repository, with
a NEWS.html alongside it that is always automatically regenerated upon any
modification of NEWS.{md,xml}.
But that's probably overkill for 200 lines of text?

> At any rate, please do not introduce any new idiosyncratic markup there
> as you did recently.

I did not introduce a markup. I introduced a kind of visual representation.
Any other visual representation that satisfies the principle that section
titles catch the eyes more easily than subsubsection titles would be OK.

Bruno

Re: File permissions in modules

[Jean L. <bu...@gn...>]

On Fri, Jan 12, 2018 at 02:40:11AM +0300, Jean Louis wrote:
> Hello,
> 
> From development version, after "make install", I
> get these permissions on files, which makes it
> impossible to use the postgresql module, I get
> file permission access.
> 
> total 452
> -rw-r----- 1 root root    299 Jan 11 19:50 link.sh
> -rw-r----- 1 root root   1120 Jan 11 19:50 Makefile
> -rw-r----- 1 root root 247456 Jan 11 19:50 postgresql.fas
> -rw-r--r-- 1 root root  25224 Jan 11 19:50 postgresql.lisp
> -rw-r----- 1 root root 148808 Jan 11 19:50 postgresql.o
> -rw-r--r-- 1 root root    528 Jan 11 19:50 README
> -rw-r----- 1 root root  15492 Jan 11 19:50 sql.fas
> -rw-r--r-- 1 root root   3197 Jan 11 19:50 sql.lisp

I found out, this is happening due to building as
user with different umask, and installing with
sudo make install.

If I build as root, and install as root, or change
umask, this is not happening.


-- 
Jean Louis

File permissions in modules

[Jean L. <bu...@gn...>]

Hello,

>From development version, after "make install", I
get these permissions on files, which makes it
impossible to use the postgresql module, I get
file permission access.

total 452
-rw-r----- 1 root root    299 Jan 11 19:50 link.sh
-rw-r----- 1 root root   1120 Jan 11 19:50 Makefile
-rw-r----- 1 root root 247456 Jan 11 19:50 postgresql.fas
-rw-r--r-- 1 root root  25224 Jan 11 19:50 postgresql.lisp
-rw-r----- 1 root root 148808 Jan 11 19:50 postgresql.o
-rw-r--r-- 1 root root    528 Jan 11 19:50 README
-rw-r----- 1 root root  15492 Jan 11 19:50 sql.fas
-rw-r--r-- 1 root root   3197 Jan 11 19:50 sql.lisp

-- 
Jean Louis

Re: make check fails

[Blake M. <bl...@mc...>]

make check on 64 bit Linux give me:

.....
;; Wrote the memory image into base/lispinit.mem (3,868,368 bytes)
Bytes permanently allocated:            165,424
Bytes currently in use:               3,535,424
Bytes available until next GC:          879,746
3535424 ;
879746 ;
165424 ;
5 ;
1952680 ;
27781
IMPNOTES="http://clisp.org/beta/impnotes/" ./clisp  -E UTF-8 -Emisc 1:1
-Epathname 1:1 -norc -x '(sys::ensure-impnotes-map t)'
  i i i i i i i       ooooo    o        ooooooo   ooooo   ooooo
  I I I I I I I      8     8   8           8     8     o  8    8
  I  \ `+' /  I      8         8           8     8        8    8
   \  `-+-'  /       8         8           8      ooooo   8oooo
    `-__|__-'        8         8           8           8  8
        |            8     o   8           8     o     8  8
  ------+------       ooooo    8oooooo  ooo8ooo   ooooo   8

Welcome to GNU CLISP 2.49.60+ (2017-06-25) <http://clisp.org/>

Copyright (c) Bruno Haible, Michael Stoll 1992-1993
Copyright (c) Bruno Haible, Marcus Daniels 1994-1997
Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998
Copyright (c) Bruno Haible, Sam Steingold 1999-2000
Copyright (c) Sam Steingold, Bruno Haible 2001-2018

Type :h and hit Enter for context help.

;; connecting to
"http://clisp.org/beta/impnotes/id-href.map"...connected...HTTP/1.1
301 Moved Permanently --> "
https://clisp.sourceforge.io/beta/impnotes/id-href.map"
;; connecting to "http://clisp.orghttps://
clisp.sourceforge.io/beta/impnotes/id-href.map"...
*** - PARSE-INTEGER: substring "" does not have integer syntax at position 0

Bye.
make: *** [check-doc] Error 1



On Thu, Jan 11, 2018 at 3:19 PM, Sam Steingold <sd...@gn...> wrote:

> Hi Bruno,
>
> Are you aware that "make check" fails on "hg tip"?
>
> People running nightly builds, could you please add "make check
> extracheck mod-check" to your scripts.
>
> Thanks.
>
> --
> Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1561
> http://steingoldpsychology.com http://www.childpsy.net http://camera.org
> http://www.dhimmitude.org http://islamexposedonline.com
> http://mideasttruth.com
> What garlic is to food, insanity is to art.
>
> ------------------------------------------------------------
> ------------------
> 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
>

Re: NEWS file format

[Sam S. <sd...@gn...>]

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2018-01-11 23:02:02 +0100]:
>
> 1) This outline format is ill-conceived for reading without special
> tool support. Namely, the subsubsections stand out brighter than the
> sections.

This is pretty common, cf. markdown.

> 2) What Emacs and vim do with these files, does not matter. The user
> will want to view the NEWS file, not edit it.

"view" calls vim.
emacs has "view" mode too.

> ("firefox /usr/share/doc/clisp/NEWS")

markdown is widely supported.

However, this is not important enough for me to argue any further.
At any rate, please do not introduce any new idiosyncratic markup there
as you did recently.

Thanks.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1561
http://steingoldpsychology.com http://www.childpsy.net http://www.dhimmitude.org
https://ffii.org http://mideasttruth.com http://memri.org
Single tasking: Just Say No.

Re: make check fails

[Sam S. <sd...@gn...>]

Hi Bruno

> * Bruno Haible <oe...@py...t> [2018-01-11 23:20:20 +0100]:
>
>> Are you aware that "make check" fails on "hg tip"?
>
> On Linux/x86_64, I get this:
>
> $ make -f Makefile.devel build-porting64-gcc-safety0
> ...
> Test failed:
> -rw-r--r-- 1 bruno bruno 286 Jan 11 23:12 ext-clisp.erg
>
> $ cat build-porting64-gcc-safety0/tests/ext-clisp.erg
> Form: (HANDLER-CASE (LETF ((*CURRENT-LANGUAGE* 'FRENCH)) (LIST (STRING=
> "À bientôt!" (SYSTEM::TEXT "Bye.")) (STRING= *CURRENT-LANGUAGE*
> "FRANÇAIS"))) (ERROR (E) (PRINC-ERROR E) '(T T)))
> CORRECT: (T T)
> CLISP  : (NIL T)
> Differ at position 0: T vs NIL
> CORRECT: (T T)
> CLISP  : (NIL T)

Darwin Kernel Version 17.3.0
./configure --with-debug --without-dynamic-modules build-g-nodynmod

Re: make check fails

[Bruno H. <br...@cl...>]

Hi Sam,

> Are you aware that "make check" fails on "hg tip"?
> 
> People running nightly builds, could you please add "make check
> extracheck mod-check" to your scripts.

On Linux/x86_64, I get this:

$ make -f Makefile.devel build-porting64-gcc-safety0
...
Test failed:
-rw-r--r-- 1 bruno bruno 286 Jan 11 23:12 ext-clisp.erg

$ cat build-porting64-gcc-safety0/tests/ext-clisp.erg
Form: (HANDLER-CASE (LETF ((*CURRENT-LANGUAGE* 'FRENCH)) (LIST (STRING= "À bientôt!" (SYSTEM::TEXT "Bye.")) (STRING= *CURRENT-LANGUAGE* "FRANÇAIS"))) (ERROR (E) (PRINC-ERROR E) '(T T)))
CORRECT: (T T)
CLISP  : (NIL T)
Differ at position 0: T vs NIL
CORRECT: (T T)
CLISP  : (NIL T)

Is this what you mean? If you meant something else, please
state the platform and the Makefile.devel target that you used.

Bruno

Re: NEWS file format

[Bruno H. <br...@cl...>]

Hi Sam,

> CLISP NEWS file is fairly long (almost 5k lines).

People usually will want to ignore the news from 2010 and before.
So, that makes only ca. 200 lines to read.

> It has "free text" format.
> I want to convert it to the outline format
> (https://www.gnu.org/software/emacs/manual/html_node/emacs/Outline-Format.html)
> which will allow for an easier navigation in Emacs and VIM.

Please not! I object!

Rationale:

1) This outline format is ill-conceived for reading without special tool
   support. Namely, the subsubsections stand out brighter than the sections.
   (The subsubsections have 3 asterisks, vs. 1 asterisk for the sections.)
   This is just the opposite of what it ought to be. Section titles should
   stand out more heavily than subsubsections.

2) What Emacs and vim do with these files, does not matter. The user will
   want to view the NEWS file, not edit it. The common tool for viewing a
   text file is the browser ("firefox /usr/share/doc/clisp/NEWS") or, in
   a terminal emulator, the 'less' program. Neither the browser nor the
   'less' program have special support for the outline format. (I just
   verified this, on emacs/NEWS.)

Bruno

Re: postgresql/Makefile.in -- error where "force"?

[Jean L. <bu...@gn...>]

I have PostgreSQL 10.1 newest version, the CLISP
is not compiling with it for some reason.

On Thu, Jan 11, 2018 at 06:20:24PM +0300, Jean Louis wrote:
> Hello,
> 
> I could not build latest development from
> mercurial today, there was error in
> postgresql/Makefile, I simple deleted the last
> line where it is "force" and could compile it.
> 
> 
> -- 
> Jean Louis

-- 
Jean Louis

make check fails

[Sam S. <sd...@gn...>]

Hi Bruno,

Are you aware that "make check" fails on "hg tip"?

People running nightly builds, could you please add "make check
extracheck mod-check" to your scripts.

Thanks.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1561
http://steingoldpsychology.com http://www.childpsy.net http://camera.org
http://www.dhimmitude.org http://islamexposedonline.com http://mideasttruth.com
What garlic is to food, insanity is to art.

NEWS file format

[Sam S. <sd...@gn...>]

Hi

CLISP NEWS file is fairly long (almost 5k lines).
It has "free text" format.
I want to convert it to the outline format
(https://www.gnu.org/software/emacs/manual/html_node/emacs/Outline-Format.html)
which will allow for an easier navigation in Emacs and VIM.
(This is the format used by Emacs NEWS file and many others).

Is this a deal-breaker for anyone?

Thanks.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1561
http://steingoldpsychology.com http://www.childpsy.net
http://thereligionofpeace.com http://www.dhimmitude.org
recursion, n: See recursion.

postgresql/Makefile.in -- error where "force"?

[Jean L. <bu...@gn...>]

Hello,

I could not build latest development from
mercurial today, there was error in
postgresql/Makefile, I simple deleted the last
line where it is "force" and could compile it.


-- 
Jean Louis

Re: failure in nightly build

[Sam S. <sd...@gn...>]

> * Don Cohen <qba...@vf...3-vap.pbz> [2018-01-07 16:18:46 +0000]:
>
> ;; Compiling file /home/don/hg/clisp/modules/readline/readline.lisp ...
> *** - APPLY: too few arguments given to
>       #<COMPILED-FUNCTION SYSTEM::FINALIZE-COUTPUT-FILE-13>
>
> 0 errors, 0 warnings
> Makefile:24: recipe for target 'readline.c' failed
> make[1]: *** [readline.c] Error 1
> make[1]: Leaving directory '/home/don/hg/clisp/build-dir/readline'
> Makefile:2334: recipe for target 'readline' failed
> make: *** [readline] Error 2

sorry, fixed

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://mideasttruth.com
https://ffii.org http://thereligionofpeace.com http://americancensorship.org
There are 10 kinds of people: those who count in binary and those who do not.

failure in nightly build

[<don...@is...>]

;; Compiling file /home/don/hg/clisp/modules/readline/readline.lisp ...
*** - APPLY: too few arguments given to
      #<COMPILED-FUNCTION SYSTEM::FINALIZE-COUTPUT-FILE-13>

0 errors, 0 warnings
Makefile:24: recipe for target 'readline.c' failed
make[1]: *** [readline.c] Error 1
make[1]: Leaving directory '/home/don/hg/clisp/build-dir/readline'
Makefile:2334: recipe for target 'readline' failed
make: *** [readline] Error 2

Re: release plans and schedule

[Bruno H. <br...@cl...>]

> > Perhaps translate some of the remaining german comments, so Sam and
> > others can benefit.
> 
> That's always welcome ;-)

I translated the german comments in loop.lisp.

Bruno