"Nick Sabalausky" <a@a.a> wrote in message
news:gj1olu$1390$1@digitalmars.com...
> "Walter Bright" <newshound1@digitalmars.com> wrote in message
> news:gj0qht$2lc1$1@digitalmars.com...
>> What platforms for dmd would you be most interested in using?
>>
>> .net
>> jvm
>> mac osx 32 bit intel
>> mac osx 64 bit intel
>> linux 64 bit
>> windows 64 bit
>> freebsd 32 bit
>> netbsd 32 bit
>>
>> other?
>
> - ARM7/ARM9
> - Other misc microcontrollers, like Parallax's Propeller
> - Mac osx 32 bit intel
> - *maybe* bsd 32-bit, .net and jvm (and with .net and jvm I'd want to
> still be able to use tango and phobos, and not be forced to switch to the
> .net and jvm standard libs)
To elaborate:
1. A "systems language" that doesn't compile to any embedded microcontroller
seems more than a little bit silly to me. (Sad as it is to say, I don't
think GDC counts anymore.)
2. I have absolutely zero interest in 64-bit. To the people annoyed at the
limitations of the 32-bit address space: What in the world are you working
on? Non-linear video editors and 3D modeling packages?
I should also add near the top of my list, "the CPUs of all major game
consoles". I think console game programmers are very much in need of a
language that doesn't suck as horribly as C++, and D is the only one out
there that doesn't contain fundamental deal-breakers for modern console game
dev.

"Chad J" <gamerchad@__spam.is.bad__gmail.com> wrote in message
news:gj1p0l$13pv$1@digitalmars.com...
> Walter Bright wrote:
>> What platforms for dmd would you be most interested in using?
>>
> Or, better yet:
> Cross-platform C code.
> Get me that and I have a lot less reason to even care about the others.
Yes. This. Perfectly stated. Anyone that puts out a CPU makes a C compiler
for it, sometimes C++, but rarely any other non-proprietary language, and
(unfortunately) especially not D.

"Walter Bright" <newshound1@digitalmars.com> wrote in message
news:gj1psc$14q2$1@digitalmars.com...
> Chad J wrote:
>> Or, better yet:
>> Cross-platform C code.
>> Get me that and I have a lot less reason to even care about the others.
>
> The problem with generating C code is: exception handling
Can't the normal exception handling boilerplating just be placed explicity
in the functions? Or, I guess maybe that would require code that was
specific to C-compiler/CPU combination?

Reply to Nick,
> 2. I have absolutely zero interest in 64-bit. To the people annoyed at
> the limitations of the 32-bit address space: What in the world are you
> working on? Non-linear video editors and 3D modeling packages?
how about DBs? Or most anything that uses more than about 2GB of data.