On Dec 17, 2007 11:32 AM, Levi Pearson <[EMAIL PROTECTED]> wrote: > I have written a few programs in D, and it seems to be a pretty decent > language in the C family, though it was a bit of a moving target and > severely underdocumented when I used it. I used the gcc backend, so > theoretically it would be fairly easy to cross-compile with it, but > until recently I was targeting a poorly supported chip and couldn't > even get the C++ runtime to build for it. > > Probably the primary reason not to use D for embedded work is that the > development toolkits for embedded boards tend to be custom gcc setups, > and pulling them apart so you can use your own toolchain can be > perilous and time-consuming. Also, there aren't a lot of D > programmers around, and probably few of them are embedded systems > programmers. >
All this talk of C, D, Java, J2EE, Python, Ruby - can we take Perl out of the subject? I'd hate to take the name of Perl in vain. ;-) Jesse -- Jesse Stay Chief Social Officer SNAPlicate, Inc. http://www.snaplicate.com Cell: (801) 979-7576 Blog: http://www.jessestay.com /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
