Re: newcomers

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

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2017-05-27 23:27:39 +0200]:
>
> Possibly every module should be accompanied with unit tests?

Most modules already are.
See "make mod-check".

>> Normal users are also affected - people try something and submit bug
>> reports without reading http://www.clisp.org/impnotes/clisp.html#bugs and
>> following conversation is about 'clisp --version', build options, etc.
>> Probably having binary releases is the 'good enough' solution for this.
>
> I don't think one can do anything about this, other than to remind the
> users what information to provide.
> Different OSes have different support for mmap, __thread, system calls, etc.
> - therefore invariably the builds on different OSes will end up using
> different code paths.
>
> Or should we hook into 'apport', so that the details get collected
> automatically?

'clisp --version' is our apport.
It is supposed to print _everything_ you ever want to know.
If you find yourself asking for a bug reporter for extra info, you
should incorporate it into "clisp --version".
If you feel that its output is growing too huge, you can make "clisp -v"
print "short version" and "clisp --version" the long one.
And then you will find yourself telling every other bug reporter to
submit "clisp --version" in addition to "clisp -v". :-)

PS. I think your answer will be:
    "clisp --version" cannot print the whole "config.log"  :-)

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://mideasttruth.com
http://islamexposedonline.com http://www.memritv.org http://iris.org.il
MS Windows vs IBM OS/2: Why marketing matters more than technology...