The procedure Move (originated from Borland Pascal) copies data from one location in memory to another.
Unlike the name suggests, no data is “lost” at the source.
Its signature reads:
procedure Move(const source; var destination; count: sizeInt)
Note that source and destination do not have a data type, thus specifying an Identifier without (necessarily) applying the address‑operator is sufficient.
Application
editMove can be considered a very “low-level” routine.
It was originally developed to copy char values within the same string, but has ever since been (ab‑)used for other purposes, too:
- If Pascal’s strong data type system imposes (too many) restrictions that need to be circumvented for hardware-close programming and typecasting does not resolve the task’s problem or is too cumbersome.
- For circumventing Pascal’s restrictions in a very “hacky” nature: E. g. copying a
filevariable (there are good reasons you cannot simply:=to afile). - For performance reasons: Copying huge blocks of memory with
movecould be faster than an equivalentfor‑loop. For instance the fpc/source/blob/release_3_2_0/rtl/x86_64/x86_64.inc#L75-351 x86‑64 implementation takes advantage of architecture-specific circumstances.
Using move often makes your code very unportable since it often makes assumptions about endianness, internal structures or similar things.
A quick demo should not be missing.
Nevertheless, this example is bad in nature.
A plain := assignment would have been sufficient.
Note, using move possibly prevents the compiler from performing certain optimizations.
program moveDemo(input, output, stdErr);
var
x, y: integer;
begin
x := 42;
move(x, y, sizeOf(x));
writeLn(y);
end.