Re: Ugly warnings under 64 bit compilation
Available news archives: comp.lang.tcl - comp.lang.python - comp.security.firewalls - sci.crypt - comp.lang.php - comp.lang.javascript
Google
 
Web news.hping.org


comp.lang.tcl archive

Re: Ugly warnings under 64 bit compilation

From: Andreas Leitgeb <avl@gamma.logic.tuwien.ac.at>
Date: Fri Mar 10 2006 - 10:58:07 CET

Robert Heller <heller@deepsoft.com> wrote:
> CN> #define TCL_VOLATILE ((Tcl_FreeProc *) (1+(char *)NULL))
> CN> #define TCL_VOLATILE ((Tcl_FreeProc *) 1)
> #define TCL_VOLATILE ((Tcl_FreeProc *) 1L)
> would also work (and be less 'strange' and 'convoluted').

Wouldn't it be just best to define a dummy-procedure whose
signature matches Tcl_FreeProc, which does either nothing,
or abort with trace, and use that dummy function's address
as a second "special" value (which appears to me to be the
whole point of TCL_VOLATILE)

Isn't that also, how default-signal handlers are specified
on C-level?
Received on Sun Apr 30 02:29:07 2006