|
Essentially that's true, although neither form of EVAL implement the
more obscure behaviour of MOVE operations nor does EVAL tolerate
numeric overflow by default.
But in Assembly Language the Assembler only does what you tell it to
do. If you didn't make use of a temporary then you changed the value
you are about to copy thus each element (byte) gets the same value.
With HLLs a reasonable compiler (i.e., not C and its ilk) will
generally do what is reasonably expected by the programmer.
Umm, memcpy() output is undefined when copying objects that overlap.
Not surprising you get unexpected behaviour. If you want predictable
behaviour for coincident operands you need to use memmove().
%SUBARR appears to give the behaviour you expect where:
%subarr(myNumbers: 2 ) = %subarr(mynumbers : 1 );
will fill the array with the value of the first element. However, this
behaviour seems to be a side-effect and cannot be relied upon (see my
previous e-mail for supporting documentation).
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.