[Gcl-devel] Re: ANSI

[Camm Maguire]

Thank you, and my apologies for the question.  I'm trying to hurry
this summer, and am using your wonderful tet suite largely as a
replacement for me having to read and parse the spec in detail
myself.  I should have known that you'd get it right, but I just had
the nagging question that this might have been designed to fit other
complying implementations.

I hope you don't mind a little more email traffic this summer as we
work on things.  I'll try to be brief.

Is it true that your suite checks the integrity of the compiled or
interpreted functions as supplied in the image, and not the result of
any compiler inlining or replacement of such functions, except in the
random tester?  I'd like to deduce from the ansi test results if
possible that I haven't messed up compiler inlining of #'member
et.al. for example.

Take care,

"Paul F. Dietz" <address@hidden> writes:

> Camm Maguire wrote:
> 
> > 2) Paul, if *compile-verbose* defaults to t, must the output of 
> > compile-file have
> >    semi-colons?
> 
>  From COMPILE-FILE:
> 
>    "If verbose is true, compile-file prints a message in the form of a comment
>     (i.e., with a leading semicolon) to standard output indicating what
>     file is being compiled and other useful information. If verbose is false,
>     compile-file does not print this information."
> 
>       Paul
> 
> 
> 
> 
> 
> 

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah