tag:blogger.com,1999:blog-18241482.post8646897412226814041..comments2008-12-28T21:30:40.138-08:00The Free Memehttp://www.blogger.com/profile/08287129746971472910cristi.vlasceanu@gmail.comBlogger4125tag:blogger.com,1999:blog-18241482.post-85860955731996394042008-12-28T21:30:00.000-08:002008-12-28T21:30:00.000-08:00Derek,<BR/>if that turns out to be the case we'll have to add some unsafe { } hack to the front-end, C#-style. But for now I am focused on releasing a D.NET compiler as soon as possible and refine it later as requests from users come in.The Free Memehttp://www.blogger.com/profile/08287129746971472910noreply@blogger.comtag:blogger.com,1999:blog-18241482.post-22170010110673835422008-12-28T21:06:00.000-08:002008-12-28T21:06:00.000-08:00I guess it depends on the final application. I figure the majority of programs will benefit from elimination of pointers, by speeding development and eliminating some types of bugs. However if the application has to be as fast as possible, then pointers might be necessary.Dereknoreply@blogger.comtag:blogger.com,1999:blog-18241482.post-55946865402322711712008-12-28T20:48:00.000-08:002008-12-28T20:48:00.000-08:00Sure, but remember that in D you have things such as foreach (code can be generated under the hood to traverse arrays and tuples in the most optimal way) and array slices (you can work with array ranges in a bound-checked way, fast).The Free Memehttp://www.blogger.com/profile/08287129746971472910noreply@blogger.comtag:blogger.com,1999:blog-18241482.post-81581529755757801942008-12-28T19:35:00.000-08:002008-12-28T19:35:00.000-08:00They're fast!Dereknoreply@blogger.com