On 8/26/15 8:14 AM, John Burton wrote:
This would be undefined behavior in c++ due to aliasing rules on
pointers. It appears to work reliably in D when I try it, but that's
obviously no guarantee that it's correct or will continue to do so.
Is this correct code in D? And if not, what should I
On Wednesday, 26 August 2015 at 12:14:54 UTC, John Burton wrote:
This would be undefined behavior in c++ due to aliasing rules
on pointers. It appears to work reliably in D when I try it,
but that's obviously no guarantee that it's correct or will
continue to do so.
Is this correct code in
Ok thank you.
Seems to me that there is enough doubt that this is supported
that I'd be best to avoid relying on it, or at least ensure that
it's all encapsulated in something I can easily change.
This would be undefined behavior in c++ due to aliasing rules on
pointers. It appears to work reliably in D when I try it, but
that's obviously no guarantee that it's correct or will continue
to do so.
Is this correct code in D? And if not, what should I do instead
to cleanly and efficiently
On Wednesday 26 August 2015 14:14, John Burton wrote:
This would be undefined behavior in c++ due to aliasing rules on
pointers. It appears to work reliably in D when I try it, but
that's obviously no guarantee that it's correct or will continue
to do so.
Is this correct code in D? And if
