|
> From: Buck Calabro > > People really are going to want to do the same with /free, > and for some reason refuse, absolutely refuse to switch between /free > and /end-free within the same block of code. Maybe some of those > folks can chip in with reasons why they won't do that. We might be > able to get a DCR out of it... I'm not going to bother with the MOVE argument; I'm reasonably sure everybody knows my stance on the issue <grin>. But I'll weigh in (once) on this issue: we don't like /free and /end-free because they aren't needed. By simply saying that a blank in position 6 makes the spec a free-form calculation, we wouldn't have an issue. But the compiler team decided it would be better for us if we had to code the bracketing statements. Heck if I know why. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.