Comments for The Future of the Delphi Compiler

The Future of the Delphi Compiler

2010-03-03T08:17:09-08:00

thanks sohbet cinsel sohbet sohbet kanallari sohbet muhabbet

re: The Future of the Delphi Compiler

2010-02-03T14:29:51-08:00

This is why I always use // for programming comments -- so that I can use { } to comment out blocks of code.

re: The Future of the Delphi Compiler, 64 bit

2009-10-05T23:19:08-07:00

They've changed their goals. 64 bit compiler is now not that important...

The Future of the Delphi Compiler, 64 bit

2009-09-28T06:38:01-07:00

Nick Hodges wrote:Because the compiler is the first step in a complete 64-bit product, we are planning to release a preview of the 64-bit compiler in mid-2009 so that those of you who are extremely eager to see a 64-bit Delphi can get started early. Mid-2009 was three months ago. What's happening?

The Future of the Delphi Compiler

2009-09-27T06:45:07-07:00

You have my support on this one.To be quite honest, this is the only article I have read in the past few years on the future of Delphi that makes proper sense to me!Here is my preferences:- Leading edge stuff, it's why I chose this compiler many years ago.- Support 64 bit platforms, both Itanium, Nehalem Ex, and IBM Power- Support for hardware parallelism- support for computational nodes (NVIDA GPUs an multicore CPUs)Extensive components suites out of the Box:- Who said Borland should not be in the component business,- Dev Express, TeeChartPro, TMS controls, ReportBuilder, IntraWeb, SpreadsheetGear like components. Some improvements to DBExpress (learn from DOA) - Vector and image Graphic Component Kits.- 3D and visualisation technologiesSupport for High performance BI environments- ETL, and Data Migration Coding components and tools.- many many many tools possible here!More more Application Wizards:- Get going faster with any app.I don't want the Microsoft stuff, I want to productively create high performance applications. No the dotNet bloatware way?

The Future of the Delphi Compiler

2009-08-05T06:58:26-07:00

OMG, please do NOT remove the support for (* *) style comments! These are very very useful for differentiating between different types of comments. For example, we use { } comments for 'real', documenting comments, and (* *) for temporarily or permanently commenting out code blocks.

The Future of the Delphi Compiler

2009-06-26T04:27:06-07:00

I'm a Delphi fan since the version 1.0. I really think that Object Pascal is working well. However, I think there was two much time spent into catching up with the growth of the MS stuff like .NET and C++ and all these are slowing down the development of Delphi itself.The hardware had changed a lot in recent years but the Delphi team has just finished the unicode compiler and template support (I don't mean that they are not good), it is just too slow. Delphi needs to make a revolution to keep its glory!Some ideas are listed below:1. Multi-Threading support and optimization in grammatic level2. High level UI interaction framework using action driven model based on current message driven model. The future is not only mouse and key board, not only clicking and draging, but also drawing and writing.3. 3D UI framework. At least it shall be placed in the plan. The 3D world may come sooner as anyone thought.At last, CodeGear should learn from MS for its strategies by attracting young peoples and student to learn and use Delphi by releasing a free limited version. Today young Delphi developers (at least in Berlin) are rarer than pandas and vast Delphi workplace are going lost.

The Future of the Delphi Compiler

2009-02-16T03:42:06-08:00

That is a GOOD NEW you have decided to take the needed time to do everything well. mid 2010 seems reasonable. more than 64 bits alone, having a better interoperability between C++ and Delphi Pascal is a must-have, as well as multiplatform support.

re: The Future of the Delphi Compiler

2009-02-14T22:08:03-08:00

1. How about the "Delphi++" (incompatible) version being PRISM? That way we have our choice (just as C++ users choose between incompatibility with the C standard and C#). Delphi's original success was a then-state-of-the-art compiler IDE with much faster and easier development cycle (I migrated off Apple's pascal). 2. And while you're at it, please consider compatibility with the newest official "Pascal++" standards (the language variants supporting parallel processing, high level development, array processing hardware, etc.). These have limited commercial support but would be a major incentive for the European community and power users.3. In the same vein, a MS C# to "Delphi++" conversion would attract even more people fed up with MS but wanting the best technology. True, Delphi can't compete with doing "Visual C++ me too", bec. the latter is far too difficult to become proficient with, so people who have made that commitment will _not_ switch to Delphi. Developers who want better productivity are trying C#. By providing similar state of the art (C#) features with ("Delphi++/Prism") in a productivity-oriented, bug-prevention environment, CodeGear could be very attractive alternative to the people who are considering making the switch to C#. 4. Keep up the good work: this topic was TABOO on the Borland DN ("we cannot discuss our development plans at this time")

re: The Future of the Delphi Compiler

2009-02-14T20:56:54-08:00

AGREE, we would rather see 64-bit "compatiblity" at this stage, then add 64-bit "optimization/features". At least we can deliver software on these platforms instead of resorting to MS.