2020/08/07 20:03 ... Thorsten Glaser:
Using (char *)-1 can cause traps on some platforms, or
the compiler to replace the entire codepath (including
backwards!) with nōnsense.
And if the platform is x86, what of long and short pointers? Or do all
the C-compilers use only the longest?
If pointer
2020/08/08 17:43 ... Steffen Nurpmeso:
Being all in favour of
keeping UTC aligned with the sun, whatever this means.
I suspect that it is time to detach the physical second, that physicists
use, from the second that is one 86400th of a day, and find a definition
of "day" that depends on our e
Thorsten Glaser wrote in
:
|Steffen Nurpmeso dixit:
|
||>> socks5_proxy = &magic_value;
|
|Just use that; the file already has a magic value
|you can use (hostname).
Whereas this is true, i still do not see the problem here really.
lynx uses (PTR)-1 itself, at least in src/tidy_tls.c, and i
[...(char *)-1...]
> You know -- i for one do not care about the issue,
Ah. Then, goodbye. If you don't even care about portability issues in
lynx, there I have nothing more of value to contribute to this thread.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Again
Steffen Nurpmeso dixit:
|>> socks5_proxy = &magic_value;
Just use that; the file already has a magic value
you can use (hostname).
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the number of
seconds between the refe
Mouse wrote in
<202008081942.paa25...@stone.rodents-montreal.org>:
|>> So, in summary, except for the null-pointer-constant special case,
|>> converting integers to pointers is intended to be useful in
|>> machine-dependent code, but is not portable beyond that.
|> ISO C99 specifies intptr_t a
>> So, in summary, except for the null-pointer-constant special case,
>> converting integers to pointers is intended to be useful in
>> machine-dependent code, but is not portable beyond that.
> ISO C99 specifies intptr_t and uintptr_t though,
Yes - but there is no promise that an intptr_t or uint
Mouse wrote in
<202008080031.uaa13...@stone.rodents-montreal.org>:
|>>> + socks5_proxy =3D (char*)-1;
|>> Don=E2=80=99t do that, that is not portable.
|> Really?? This i do not understand.
|
|Casting an integer, other than a compile-time constant expression with
|value 0, to a pointer?
Hello.
Thorsten Glaser wrote in
:
|Steffen Nurpmeso dixit:
|
|>Really?? This i do not understand.
|
|You’re only allowed to take pointers to actual objects.
|It should probably be possible to use NULL somewhere,
|but you can use &hostname as magic pointer.
|
|Using (char *)-1 can cause
