[cvsnt] Re: Keyword 'properties' breaks rcs keyword ordering

Bertho Stultiens bertho at akhphd.au.dk
Mon Jun 13 22:20:44 BST 2005


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


> Tony Hoyle wrote:
> The syntax of 'properties' is such that it cannot be parsed by the old 
> RCS executables *at all* so you must use the cvsnt RCS wrappers.  You 
> could get away with it before... you can't any more.

Well, I do not know why this is done, but it is not a smart move IMO. It is
so simple to adhere to the rcsfile(5) format, so that other applications can
read the content without being broken.

Why should you want to require the cvsnt RCS wrappers? I can see no other
reason than deliberate breakage of other applications. There is no
functional reason to place the properties before the next keyword. So why
not keep all legacy apps happy and place the properties keyword after the
next keyword?

If you want to improve on the fileformat, then, I guess, you should redesign
all ambiguities in the definitions of rcsfile(5) and move to a completely
_new_ format. That would be understandable for outside developers (and
easier to work with).

-- 
Greetings Bertho

NOTE: Dear Outlook users: Please remove me from your address books.
      Read this article and you know why:
      http://newsforge.com/article.pl?sid=03/08/21/143258


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook