Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!ForthNet From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie) Newsgroups: comp.lang.forth Subject: Blocks vs Text files Message-ID: <2246.UUL1.3#5129@willett.pgh.pa.us> Date: 20 Jan 91 15:25:20 GMT Organization: (n.) to be organized. But that's not important right now. Lines: 35 Date: 01-13-91 (22:17) Number: 880 of 891 (Echo) To: B.RODRIGUEZ2 [BRAD] Refer#: 829 From: STEVE WHEELER Read: NO Subj: SOURCE CODE CONTROL Status: PUBLIC MESSAGE Conf: FORTH (58) Read Type: GENERAL (+) Here at Vesta we have been using Polytron's version control system (PVCS is a commercial product) for a few projects. We have used it for Forth source in both block files and text files. I like it much, and intend to start using RCS on our non-Messy-Dos systems, but there are a few caveats ... With block files, you can't take advantage of the capabilities to time/date/etc. stamp the files as to when they were taken from the archive, nor can you maintain in the source the revision comments maintained by the version control system. With text files, this may not be a problem (PVCS allows you to specify the comment prefix based on file extension, so "\ " for *.4TH works nicely. We're moving to using it for maintaining revision control on code, documentation, and anything else we keep around and revise. Sometimes, being able to recover a previous version of something (prior to improvements and enhancements which failed) can save a project (or an ass ...) - Wheels NET/Mail : RCFB Golden, CO (303) 278-0364 VESTA & Denver FIG for Forth! <<<>>> ----- This message came from GEnie via willett. You cannot Reply to the author using email. Please post a follow-up article, or use any instructions the author may have included (USMail addresses, telephone #, whatever). Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp