There are some respects in which cssc behaves unlike other versions of sccs. These differences mainly relate to the removal of arbitrary limits or problems, and generally do not pose an interoperability problem. The most important extensions are listed below.
getsupports four-digit years. See The Good News.
admin -i, the
admincommand will automatically determine if the file needs to be encoded. Other versions of sccs which do this rely on being able to seek in the input file specified as the argument to the -i option, which means that this is not possible if the initial file body is being read by a pipe. The cssc implementation of
admindoes not have this limitation, since it seeks on the file being created instead. See Unemulated Features.
yflags and binary file encoding). The cssc suite attempts to honour all of these extensions, and is probably the only implementation which has all these features. If you try to use a feature which is specific to only one implementation of sccs, cssc will issue a warning that what you are doing is not portable.
If you use features of cssc which are extensions originating in
more than one other sccs implementation, for example both the
x and the
y flags, you have effectively tied yourself to
cssc. Once you are in that position, you are no longer able to
interoperate with any other version of sccs (since, in this
example, any other version of sccs will fail to understand either
x or the
y flag). If interoperability with other
versions of sccs is no longer an issue, you might as well bite
the bullet and migrate to a more modern configuration control system
entirely. See Overview.
valimplements some checks that other implementations lack. Howver, it is not complete, and so there are also checks that other implementations make that cssc does not.
getwill still work).
diffand the MR-validator specified by the
vflag. However, with the exception of the
sccsdiffshell script, the tools within the cssc suite do not invoke each other. For example,
deltadoes not invoke
get. This behaviour is different to the traditional architecture of sccs and might introduce subtle differences of behaviour. Any such differences are bugs; see Reporting Bugs.
See also Missing Features and other Problems.