|
You know, they could fix it pretty easily if they allowed the format name to be the same as the file name. Assuming that you never want to use multi-format files (never saw a reason for these anyways). It seems that, on certain operations where either format name or filename is allowed (CHAIN, READE, SETLL, etc.), the compiler uses different methodology to perform the action, based on the choice to use filename or format name. Either way works 99% of the time, but sometimes, for some mysterious, behind the scenes reason, one must be used rather than the other. If they allowed the same name for both filename and format name (without having to RENAME), then the compiler could deal with these 'mysterious' decisions behind the scenes, which is where they should be dealt with anyways. In my opinion, the decision boils down to, "do I want to chain to the file, or the format", and with no real reason to go either way, what am I left to do, flip a coin? -- "Enter any 11-digit prime number to continue..."
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.