bug-cssc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-cssc] Test binary/auto.sh fa11


From: Joerg Schilling
Subject: Re: [Bug-cssc] Test binary/auto.sh fa11
Date: Sat, 21 May 2011 11:26:41 +0200
User-agent: nail 11.22 3/20/05

James Youngman <address@hidden> wrote:

> On Fri, May 20, 2011 at 10:52 PM, Joerg Schilling
> <address@hidden> wrote:
> > Hi,
> >
> > it seems that you asume that
> >
> >        admin -ifile s.file
> >
> > does not automatically switch into binary (encoded) mode.
> > Is there any reason for this decision?
>
> I only assume that for non-CSSC implementations.

I did test this with the original SCCS and it failed.
I did not test it with CSSC.

> Some SCCS implementations do or did fail to detect files which are, at
> least as we would understand it, binary files, but which happen not to
> contain start-of-file or character 10 (i.e. \n), followed by character
> 1 (i.e. \001).  GNU CSSC does detect these files and automatically
> turns on uuencoding.   Hence the test you named verifies this
> behaviour for CSSC in order to detect any potential regression, but
> doesn't require that behaviour of non-CSSC implementations of SCCS,
> since they don't all provide it.

SCCS correctly detects the null byte that the test file from test fa11 inserts.

The test is then considered as failed by your script and this is why I am 
asking.


BTW: I verified that SunOS-3.5 does not support encoded files, so this seems to 
be a feature from SunOS-4 (most likely as a result of the efforts for NSE that 
contained the first project oriented SCM [based on SCCS] and that came up to 
the end of the SunOS-3.5 period shortly before SunOS-4.0 came out).

So the question is:

fa11 fails with the original SCCS, does it fail with CSSC too?

It is intended that this test should fail?

BTW: When I should discuss the behavior of SCCS, I would like to be able to 
tell SCCS not to automatically switch to binary mode (e.g. via an environment 
varibale to catch the case where the only reason for bein "binary" is a missing
new-line character at the end of the file.



Jörg

-- 
 EMail:address@hidden (home) Jörg Schilling D-13353 Berlin
       address@hidden                (uni)  
       address@hidden (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily



reply via email to

[Prev in Thread] Current Thread [Next in Thread]