[Top][All Lists]

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

Re: [Bug-cssc] Test delta/errorcase.sh -> E30 .. E32

From: Joerg Schilling
Subject: Re: [Bug-cssc] Test delta/errorcase.sh -> E30 .. E32
Date: Sat, 21 May 2011 12:17:12 +0200
User-agent: nail 11.22 3/20/05

James Youngman <address@hidden> wrote:

> > be specified if an SCCS file is being
> > initialized.
> A rather odd explanation for this message; clearly, an SCCS file
> actually is being initialised.
> > SCCS on Solaris automatically assumes -n if you specify -i and it seems that
> > the warning above has been removed for unknown reason, but the encoding flag
> > is only added in case that you use -i.
> >
> > We should discuss which behavior should be expected here......
> I haven't had access to a 4.1 system for testing since around 1998.
>  In cases where SCCS implementations differ I normally select the
> behaviour that I think is most likely to reflect what the user expects
> (a notable exception here is where the user has essentially requested
> that this not happen, e.g. by setting $CSSC_MAX_LINE_LENGTH.

I would expect a modern SCCS implementation to match the "unlimited" line 
length as introduced aprox. 20 years ago by Sun. 

> The intent of the command "admin -n -b s.foo" is pretty clear, so I
> guess I simply implemented the user's likely intent.   As do later
> releases of SCCS.

I know of no SCCS implementation that will accept

                "admin -n -b s.foo"

_and_ create a binary "coded" s.foo

SVr4 and Solaris based SCCS implementations will however accept:

        "admin -n -b -i/dev/null s.foo"

and do what you expect.


 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]