You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In other words it internally already uses "MemSet()" but with a fixed byte value of 0.
I would kindly request to expose "MemSet" too (so bbMemSet or so).
As this is only for "bytes" ("char") I think we would need (most often) a 32bit version too ... or also 64bit?
Inside of BlitzMax we could expose it overloaded
but would need to care for "left over" bytes (a size which is not a multiple of the value size)
(for now I would prefer a "if it does not fit into anymore, keep it untouched")
The current implementation of
MemClear()
isblitz.mod/blitz.bmx
blitz.mod/blitz_memory.c:
In other words it internally already uses "MemSet()" but with a fixed byte value of 0.
I would kindly request to expose "MemSet" too (so
bbMemSet
or so).As this is only for "bytes" ("char") I think we would need (most often) a 32bit version too ... or also 64bit?
Inside of BlitzMax we could expose it overloaded
but would need to care for "left over" bytes (a size which is not a multiple of the value size)
(for now I would prefer a "if it does not fit into anymore, keep it untouched")
Approaches:
https://stackoverflow.com/questions/108866/is-there-memset-that-accepts-integers-larger-than-char
The idea is to allow speeding up eg. "writepixel"-blocks in TPixmap objects.
https://www.syntaxbomb.com/blitzmax-blitzmax-ng/faster-pixmap/new/#new
The text was updated successfully, but these errors were encountered: