Future Proof File Designs/Methods

[Chris Sharman]

>A little tip. Permanent subfiles are OK.
>Remember only the *.SFD file is required for a compilation to take =
>place. Treat this like any other source code.

That's OK for compilation, but will be fatal at run-time. Also if the .SFD
changes, you have to rebuild it: in that respect it isn't source code, but is
generated from another source.

>We operate with VMS using a CMS library. The following technique allows =

Likewise.

>1. Fetch all the *.SFD files from the CMS library
>2. Create a logical for each *.SFD files
>     eg. FRED.SFD has a logical FRED pointing to (including location of) =
>the FRED.SFD file

OK if the names don't clash with source names, compiled module names, or
dictionary data files.

>No need for special compilation ordering to make sure that a subfile =
>definition is known for compilation to succeed.

Well, yes - we avoid special ordering - if a source module needs a subfile to
build, it has to be built earlier within that module, or in another module of
the same name, but different type.

The other problem occurs with cleaning up all the old instances of permanent
subfiles at run-time, if they're local to a user. If you just put deletes in
your script then you probably should have used a temporary subfile in the first
place.

Personally I feel temporary files are a good discipline, and there are very few
occasions where they're inadequate, but a dictionary datafile is inappropriate.
Usually just for write-only records for archival purposes.

Whatever works in your shop anyway.

Regards,
Chris
______________________________________________________________________
Chris Sharman			Chris.Sharman@CCAgroup.co.uk
CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.