Thomas Heller <theller@python.net> writes: > > Why is that? Why does it add a danger that would not be there without > > it. > > Because you would pass the integer to a function expecting a pointer, > store it in a structure as a pointer, or something like that - what > else? The danger is in the function, of course, but the integer > address probably encourages to implement those functions. But the functions are alreay there and implemented; as I said, I'm concerned with the fcntl/ioctl family of functions. If "I can get the address" would be encouraging to write functions that take arbitrary integers as pointers, we would already have tons of such functions, since the id() builtin also gives you an address. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4