This section outlines some of the ways in which various versions of sccs differ from each other and therefore sometimes from cssc.
The various versions of sccs differ in their level of support for binary files (see Binary File Support), and in the maximum line length that they will support (see Maximum Line Length.
There are some small variations in the way that the several versions
sccsdiff behave. These are outlined in the table below :-
diffoutput for each s-file. This separator is output before the first set of diff output, even if only one s-file has been named on the command line.
There are a few differences in the behaviour of the
command across the various SCCS Implementations :-
admin. See Binary File Support, for more information.
xflag, which turns on the executable bits of the mode of the g-file when it is created. Other versions of sccs do not have this feature. While csssc provides this feature also, its use is not recommended. The
prt -fcommand does not indicate the value of the
adminallows this usage but issues a warning message. If the -r option is used to specify a non-trunk sid (that is, a sid with more than two components), this is allowed but some of the other tools in the cssc suite will not work correctly on the resulting file.
If the “encoded” flag is set, some versions of
prt (but not
the cssc version) omit a newline in the output and so the next
thing follows immediately on the same line.
Sun Solaris 8 features a
y flag. If the
y flag is set
in the sccs file, only the specified sccs keywords will be
expanded in the gotten file (assuming that the -k and
-e options are not used).
get command on SCO OpenServer honours the setting of the
x flag. This is described above.
For a discussion of the interoperability of cssc with other
sccs implementations, see Interoperability. For a
description of the
y flags, see Flags.