and am finding it has a nice set of features. But,
>>> what is the best way handle memory mapped IO? I don't see volatile
>>> like in C. Is writing asm {} the best way to ensure memory access?
>>>
>>> Thanks,
>>> Dan Olson
>>
>> Would std.m
"Lars T. Kyllingstad" writes:
> On Sun, 09 Jan 2011 22:44:44 -0800, Dan Olson wrote:
>
>> I'm exploring D for embedded work as a nice alternative to C/C++ for the
>> 32-bitters and am finding it has a nice set of features. But, what is
>> the best wa
On Sun, 09 Jan 2011 22:44:44 -0800, Dan Olson wrote:
> I'm exploring D for embedded work as a nice alternative to C/C++ for the
> 32-bitters and am finding it has a nice set of features. But, what is
> the best way handle memory mapped IO? I don't see volatile like in C.
>
I'm exploring D for embedded work as a nice alternative to C/C++ for the
32-bitters and am finding it has a nice set of features. But, what is
the best way handle memory mapped IO? I don't see volatile like in C.
Is writing asm {} the best way to ensure memory access?
Thanks,
Dan Olson
