What would be the consequence of implementing interfaces as fat pointers ?

Manu turkeyman at gmail.com
Tue Apr 1 07:13:48 PDT 2014


On 1 April 2014 21:50, Michel Fortin <michel.fortin at michelf.ca> wrote:

> On 2014-04-01 05:39:04 +0000, Manu <turkeyman at gmail.com> said:
>
>  The point is, it's impossible to bank on pointers being either 32 or 64
>> bit. This leads to #ifdef's at the top of classes in my experience. D is
>> not exempt.
>>
>
> Doesn't align(n) work for class members? If it does not, it doesn't seem
> it'd be hard to implement.


The point is to eliminate the wasted padding by rearranging structure
members appropriately. Since the amount of padding may be different between
arch's, the layout often needs tweaking.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20140402/e9463177/attachment-0001.html>


More information about the Digitalmars-d mailing list