Now I can see how that can be very useful, and certainly a lot cleaner
and less error-prone. I do wonder what it will do in regards to
suppressing that annoying "uninitialized variable" warning though when
passing said variable into FillChar to, you know, actually initialise it!
Admittedly, the feature I'm looking forward to are assembly language
intrinsics, so I can finally optimise SwapBuffers on Intel systems to
directly call BSWAP without having to use some compiler-specific nodes,
although I sense that one will have to wait until the version after.
Gareth aka. Kit
On 31/05/2019 17:53, Marco van de Voort wrote:
Op 2019-05-31 om 18:36 schreef Alexander Grotewohl:
can't you just use an untyped parameter in a clearmem procedure you
make yourself?
procedure ClearMem(var m);
You don't get size that way, and you have to pass it separately (see
e.g. blockread/write).
It was one of the setbacks when I came back to TP/FPC from Modula2,
the latter which does have an open array type with size attached to it.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
