Re: Need reviews of HLA Adventure

Jim Carlock wrote: 

Hey it's a text file! <g> Hmmm. Maybe the file format for the files
should include some header information such as for date/time stamps.

... I was thinking of it as an archive of files like a zipped file, where
the files keep their time and date stamps when packed and unpacked.
I think that should be the way it should be handled. Because in effect,
the .hla file is a container holding files, right? And ALL files have a time
and date stamp on them, right? And when extracting those files to their
actual source code files they should be dated and extracted with proper
date, time, (and version information if appropriate...) Something Randy
might want to consider.


That's what source code management systems are for.

Also, if that is the actual file that is used as the
assembly source, it should be able to create the appropriate date/time on
the assembled .exe.

It is less important to know when an object file was created than to know which versions of the source files it was built from. It is quite possible to build an object file tomorrow from source files older than the ones one used to build the object file today. Just storing the date the object was created on (which is kept track of by the file system anyway) will give misleading information in that case.

I also think that the other issue about overwriting a file warning would
be a nice issue to resolve.


Requiring manual intervention would make make useless.

There is also no point in saving generated files. They can simply be regenerated at any time.

--
Thomas M. Sommers -- tms@xxxxxx -- AB2SB

.