On Wed, 05 Dec 2007, Mindaugas Kavaliauskas wrote: > I can do it in C, so I've wrote a EMPTYPTR() function with > hb_retptr( NULL ); > but I'm asking about compiler based 0p0 (just like 0d0 or 0t0 for empty > date or timestamp) solution. Does such solution exist?
No. We can add literal pointer representation but I'd not like it. Empty pointer is OK for me so functions like EMPTYPTR() are fine but memory pointers are application instance dependent so I do not want to introduce any way to explicitly set their value other then null. If we add support for 0p0 then people will look for 0pDEADBEAF or other values and then for a way to store/retrieve pointers in MEMOs or other data files. I do not know if I want to implement it. At least as long as people will not use GC collectible pointers which can be validated in C code such extensions seems to be too danger. Best regards, Mindaugas _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
