×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Bob cozzi wrote:
Joe,
I hate the over use of semicolons too but find working around the MOVE is
relatively easy.
/FREE
Eval x= a+b/c;
/END-FREE
C MOVEL ACTNBR OLDACTH
/FREE
Eval msg = OldActH + 'Here ya go!';
/end-fREE
<TIC> :)
Well as I said before, I did suggest adopting Python syntax rules for
free-form calcs, but no one else would agree to that. ;-)
So, we're now stuck with the semi-colons.
Anyways, I know you're only kidding.
But in my opinion, if any RPG programmer still thinks they need the old
MOVE opcodes, I *strongly* suggest they continue coding in fixed-form
calcs, and try not to bother those who want to use free-form calcs.
I've said this before, (and I hope I don't have to say it again) but in
my opinion, free-form calcs should be used for *new* code only. Support
for fixed-form calcs won't go away. And if that's what your existing
code uses, and you're unwilling to do whole-scale modernization of that
code, then stick with it.
Cheers! Hans
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.
midrange.com
