From: Hannah Schroeter
Subject: Hyperspec issue/contact
Date: 
Message-ID: <ah6gop$nmt$2@c3po.schlund.de>
Hello!

On page http://www.xanalys.com/software_tools/reference/HyperSpec/Front/Help.htm,
towards the end, there is the following:

  Reports of discrepancies between the Common Lisp HyperSpec and the
  hardcopy form may be sent to Kent Pitman < k m p -at- xanalys -dot- com >.

(Mailadress slightly modified to render it less readable for robots)

I just tried to mail something there, but got a delivery report saying
"User unknown".

Here's the text of the mail, it was a HyperSpec issue. Maybe here is
someone who can forward the text appropriately and/or handle it.

Kind regards,

Hannah.

From: Hannah Schroeter <······@schlund.de>
To: k m p -at- xanalys -dot- com
Date: Thu, 18 Jul 2002 15:36:30 +0200
Subject: Hyperspec issue: http://www.xanalys.com/software_tools/reference/HyperSpec/Body/22_cba.htm

Hello!

On the page
  http://www.xanalys.com/software_tools/reference/HyperSpec/Body/22_cba.htm
there's an example:
  (format nil "~19,0,' ,4:B" 3333) =>  "0000 1101 0000 0101"

AFAIK, the second arg to the ~B directive must be a character,
and AFAIK, character format arguments must always be initiated
by an apostroph.

I.e. the example should read:
  (format nil "~19,'0,' ,4:B" 3333) =>  "0000 1101 0000 0101"

Also, I'm asking myself whether CMUCL 18d+ 2002-05-06's behaviour
is correct instead:
* (format nil "~19,'0,' ,4:B" 3333)

"000001101 0000 0101"

SBCL 0.7.5.6 and clisp 2.27 behave identically (i.e. no space "comma"
character used in the left padding).

Kind regards,

Hannah.
--
  Hannah Schr�ter                Entwicklung          ······@schlund.de
  Bei Schlund + Partner AG       Erbprinzenstr. 4-12  D-76133 Karlsruhe
This specification allows any of these approaches.  Solving the
Halting Problem is considered extra credit. (draft-showalter-sieve-12.txt)

From: Raymond Toy
Subject: Re: Hyperspec issue/contact
Date: 
Message-ID: <4n65zdm6ke.fsf@edgedsp4.rtp.ericsson.se>
>>>>> "Hannah" == Hannah Schroeter <······@schlund.de> writes:

    Hannah> I.e. the example should read:
    Hannah>   (format nil "~19,'0,' ,4:B" 3333) =>  "0000 1101 0000 0101"

    Hannah> Also, I'm asking myself whether CMUCL 18d+ 2002-05-06's behaviour
    Hannah> is correct instead:
    Hannah> * (format nil "~19,'0,' ,4:B" 3333)

    Hannah> "000001101 0000 0101"

    Hannah> SBCL 0.7.5.6 and clisp 2.27 behave identically (i.e. no space "comma"
    Hannah> character used in the left padding).

This has been discussed here before.  I think the conclusion that both
outputs are ok, mainly because it's not clear what is wanted.  Say the
fill character was '* instead.  Do you want spaces around "*"?  

I think I wrote a small function to format padded numbers this way,
but I can't find it right now.

Ray
From: Carl Shapiro
Subject: Re: Hyperspec issue/contact
Date: 
Message-ID: <ouyk7ntqah2.fsf@panix3.panix.com>
······@schlund.de (Hannah Schroeter) writes:

> Hello!
> 
> On page http://www.xanalys.com/software_tools/reference/HyperSpec/Front/Help.htm,
> towards the end, there is the following:
> 
>   Reports of discrepancies between the Common Lisp HyperSpec and the
>   hardcopy form may be sent to Kent Pitman < k m p -at- xanalys -dot- com >.

You shouldn't have to worry about contacting anybody at that address
as the problem you are describing is not a discrepancy between the
HyperSpec and the hardcopy form of the Common Lisp standard.
From: Barry Margolin
Subject: Re: Hyperspec issue/contact
Date: 
Message-ID: <GeDZ8.17$ox1.1036@paloalto-snr1.gtei.net>
In article <···············@panix3.panix.com>,
Carl Shapiro  <·············@panix.com> wrote:
>······@schlund.de (Hannah Schroeter) writes:
>
>> Hello!
>> 
>> On page
>http://www.xanalys.com/software_tools/reference/HyperSpec/Front/Help.htm,
>> towards the end, there is the following:
>> 
>>   Reports of discrepancies between the Common Lisp HyperSpec and the
>>   hardcopy form may be sent to Kent Pitman < k m p -at- xanalys -dot- com >.
>
>You shouldn't have to worry about contacting anybody at that address
>as the problem you are describing is not a discrepancy between the
>HyperSpec and the hardcopy form of the Common Lisp standard.

Right, the bug is in the standard itself, and the Hyperspec faithfully
preserves it.

Problems in the standard should be reported via whatever ANSI's defect
report procedure is (it's presumably described somewhere at www.ansi.org).
But since J13 has been moribund for quite some time, and it doesn't look
like a revision of the standard is in the works, don't expect much to come
of it.

-- 
Barry Margolin, ······@genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
From: Rolf Mach
Subject: Re: Hyperspec issue/contact
Date: 
Message-ID: <3D37D0CC.C753980B@xanalys.com>
Hannah Schroeter wrote:

> Hello!
>
> On page http://www.xanalys.com/software_tools/reference/HyperSpec/Front/Help.htm,
> towards the end, there is the following:
>
>   Reports of discrepancies between the Common Lisp HyperSpec and the
>   hardcopy form may be sent to Kent Pitman < k m p -at- xanalys -dot- com >.
>
> (Mailadress slightly modified to render it less readable for robots)
>
> I just tried to mail something there, but got a delivery report saying
> "User unknown".
>
> Here's the text of the mail, it was a HyperSpec issue. Maybe here is
> someone who can forward the text appropriately and/or handle it.
>
> Kind regards,
>
> Hannah.

Hannah,

Kent Pitman can be reached at ···@hypermeta.com.

We will change this on our website. Thanks for letting us know.


Regards

Rolf Mach
Xanalys LispWorks Business Development & Sales Manager, Europe

An der Schaafhansenwiese 6, D-65428 Ruesselsheim, Germany
·····@xanalys.com, www.xanalys.com, Phone ++49 +6142 938197, Fax 938199