Code: Select all
var Ptr: ^byte;
...
Ptr := nil; // error
...Isn't it written in help:zristic wrote:How would you translate that code in ASM for PIC?
That fits nil definition as pointer's value that doesn't reference anything. Ptr:=nil should in effect mean Ptr:=0.You can also compare pointers to zero value – testing in that way if the pointer actually points to anything.
shouldn't it be possible to perform such assignment without compiler warning 'Implicit typecast of integral value to pointer'? Or maybe it's better to reserve the keyword 'nil' for such operations?Assigning the integer constant 0 to a pointer assigns a null pointer value to it.
No worries, it is only a minor issue. I do check all my own remarks every time a new compiler version comes out, and report the status of my remarks...ranko.rankovic wrote:Hello Dany,
I'm sorry for this, our developers will intensely fix this little issue.
Best regards
, though the warning, 'Implicit typecast of integral value to pointer', issued when nil is assigned, is really unnecessary.Indeed...janni wrote:... though the warning, 'Implicit typecast of integral value to pointer', issued when nil is assigned, is really unnecessary.
