× 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.



On Thu, Sep 19, 2019 at 2:16 PM Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 9/19/2019 12:50 PM, John Yeung wrote:

If you find yourself dealing with a program which is chock full of
MOVE* and you need to add one line but you don't have time to
eradicate MOVE* from the whole program, in my book it is justified to
just use EVAL on that line you're adding and leave the rest of the
program as-is. Yeah, you're introducing an inconsistency in the style,
but at least you're not adding a new bug.

I think I had an easier time than most because of my background as an
assembly language hobbyist, but when working in one of these old
programs, I think of MOVE* as an overloaded operator and that keeps me
on the straight and narrow.

An easier time with what?

It sounds to me as though you're saying your assembly background helps
you use MOVE* "correctly".

My contention is that we're well past the time when there is such a
thing as using MOVE* correctly, other than *not* using it.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.