http://dn.codegear.com/article/20481 2008-10-06T22:53:39-07:00 demian diaz http://threads.codegear.com/threads/threads.exe/userall?commentid=39554 http://threads.codegear.com/threads/threads.exe/view?commentid=39554 2006-10-24T00:29:12-07:00 2006-10-24T00:29:12-07:00

re: Some updates

sorry bud... are you some kind of vb shit adict? cut that histeria and learn this great language...How can you compare that vb crap with this professional language? rudi vdm http://threads.codegear.com/threads/threads.exe/userall?commentid=37801 http://threads.codegear.com/threads/threads.exe/view?commentid=37801 2004-11-05T04:14:56-07:00 2004-11-05T04:14:56-07:00

1 thing I hate about Delphi

It's the market placing. I believe Delphi, in a localised sense, is a great tool. Great object model etc, but exactly what good is all this if there is no support for it? By this I mean relatively no support. When I decide what platform to build my technology on I need it to be maintainable. And though Delphi provides one of the most robust,comprehensive structures available, how do I promote it when I'm faced with oppositioan such as MS Visual Studio? Even with .NET framework integration being promoted by myself, my suggestions for using Delphi are still met with monotonous responses that linger from the gigantic differences in market share between Delhpi 3/4/5/6/7 and VB6(yuk). But perhaps I'm trying to fulfill a role that shouldn't even be mine, maybe Borland's marketing strategy needs to be more effective. Surely that's why I am paying huge amounts more for a single product than an MCP pays for a whole suite of software. I'm looking for a approach to enable my support of this Borland product, a strategy based purely on the technology's mechanics and technically perceived advantages just doesn't work. Craven Weasel http://threads.codegear.com/threads/threads.exe/userall?commentid=37151 http://threads.codegear.com/threads/threads.exe/view?commentid=37151 2004-06-21T13:03:11-07:00 2004-06-21T13:03:11-07:00

Some updates

First of all, Delphi is a VB clone, so what are we talking about? Delphi was created as a response to Microsoft campaing. VB was released in 1987, at this time Borland was still selling his old TurboPascal. A few years later, Borland realised that nobody wanted to develop new applications for their historic compilers... and 7 years after VB was on the market, Delphi was born...>1. It has a beautiful object model. Delphi fully supports polymorphism, encapsulation, and true inheritance. It's a matter of taste. I cannot say I love Delphi's object model.>polymorphism, encapsulation, and true inheritance. These are not Delphi inventions, of course...> It has full support for interfaces. These are not Delphi inventions, of course...> It produces small, fast executables. It does not produce small, nor fast executables. Delphi exe has over 400 kB! Linking run-time library together with main exe is something which belongs to history and not to modern high level programming tools.> It has sophisticated, low level support for COMIt's not sophisticated. There is even no way to erase type library in Delphi once you've included it in your project. There are some mistakes in help regarding COM.> Delphi has no black boxes. With a few minor exceptions, you get the source to ...Yes, I like this.> Delphi is written in itselfI'm not sure if it's COMPLETLY written in itself, I'd bet it'sn not...> Delphi will soon be cross platform.Nobody uses Kylix...> Delphi has a small, flexible component model. You can create OCX components if you want, but Delphi has a better alternative for most of your needs. Why it's a better alternative? I can't listen any arguments. Why then nobody uses 'Borland Components'?> Object Pascal is an easy to use and strongly typed languageYes, it's good for teaching.> Delphi fully supports the operating systems on which it runs. If you can do something in Windows, then you can do it in Delphi.Yes, but sometimes you must touch your left ear with your right hand... :-) Craven Weasel http://threads.codegear.com/threads/threads.exe/userall?commentid=31997 http://threads.codegear.com/threads/threads.exe/view?commentid=31997 2002-04-08T08:13:50-07:00 2002-04-08T08:13:50-07:00

How to check to see if a drive is ready. <-- WHAT?!? How did this get here?!

Anyway, I do love delphi, and I use it for all my casual programming, and most of the serious stuff I do too, but...I hate the case statement.I hate the way that it seems so non-conformant - it needs an end; yet there is no begin. I hate the way it looks untidy, since although there may a set way of laying it out, this just looks a little odd. And also, I hate the way that it'll only handle types with limited set, forcing me to use a big long stream of if else if else if else if else. Yep, I hate it when I have to use it, and I hate it when I can't. There's just no pleasing some people!But, other that than D4 and above are fantastic. Craven Weasel http://threads.codegear.com/threads/threads.exe/userall?commentid=29108 http://threads.codegear.com/threads/threads.exe/view?commentid=29108 2001-06-06T02:45:05-07:00 2001-06-06T02:45:05-07:00

How to check to see if a drive is ready.

Well I agree with Charlie Calvert... those are the same for me too...:-). Randy Trexler http://threads.codegear.com/threads/threads.exe/userall?commentid=27686 http://threads.codegear.com/threads/threads.exe/view?commentid=27686 2001-01-25T08:18:22-08:00 2001-01-25T08:18:22-08:00

All Ten Things I Love About Delphi but one

[A Copy of what I sent to the original author]I do love Delphi, since it’s inception. I love almost everything about it b/c it’s just so elegant. The syntax, the object/component model, the data structures, and the composition of a unit with its interface and implementation separated out. It’s all so logical and elegant.But there’s one item missing from your list that I believe would be at position #3: an elegant persistent model. You’re a leading developer, obviously close to the Borland folks. Why is there no ‘object database’ component model? If your response is “Borland is leaving that to a third Party”, that’s unacceptable. Only a few have tried in the past 8 years and all have failed. That should be a sign that there must be a true Object-Oriented Database System built by Borland (or it's subsidiary) with an elegant, native interface to it. Incorporate it into Delphi, the Enterprises need it badly. I tell you we are tired of Relational Databases in an elegant object-oriented world. I have looked at many development platforms and languages. After Delphi 1.0, I tried, just for kicks, looking back at other compilers, other languages, and new languages. But none of them sized up to Object Pascal and I knew it when I first learned OP. Java came close but it’s just not nearly as elegant. Only one of them is very near to pulling me away from Delphi. A product called JADE from Aroaki Corporation out of New Zealand. It is a purely, object-oriented system. Everything. The second you log in, you are working and creating objects. It’s a high-end database for Object Developers. And the JADE language is syntactically similar to Pascal. It has many other attributes I don’t want to waste your time with but it is as elegant as Object Pascal and it is Persistent. I’m telling you…this is what we need. Every day, I spend a little more time learning JADE. The excitement I get from it is similar to the excitement I got in 1993 when Delphi came out. And this worries me, because I honestly don’t want to divorce myself from Delphi. It’s just way too cool. So, do me a favor, tell the folks at Borland we need this persistent mechanism. I harp about it on the newsgroups about every six months but nothing indicates there is any effort. As I’m sure you’re aware, most who have tried this are still trying to store objects in relational tables (although I really shouldn’t care how an object is stored). These attempts are not good enough for Delphi b/c Delphi is top-notch so anything less is unacceptable. Persuade Borland to look at JADE and design an elegant persistent side to Delphi. Henk van Heun http://threads.codegear.com/threads/threads.exe/userall?commentid=26028 http://threads.codegear.com/threads/threads.exe/view?commentid=26028 2000-08-16T02:36:14-07:00 2000-08-16T02:36:14-07:00

re: Extra Delphi/VB comment

It is so TRUE!!!VB may be visual, but it is also ugly to see. Sven Opitz http://threads.codegear.com/threads/threads.exe/userall?commentid=25926 http://threads.codegear.com/threads/threads.exe/view?commentid=25926 2000-08-09T06:00:30-07:00 2000-08-09T06:00:30-07:00

One missing "VB-Feature"

one thing noone yet said is that VB sticks to the all so slow and bulky variants. if you say"private MyVar1, MyVar2 as String"MyVar1 is a string, but MyVar2 is a variant.Does that mean, that MS doesn't think I am able to decide, when I need a variable of a specific type? Tom van der Vlugt http://threads.codegear.com/threads/threads.exe/userall?commentid=24923 http://threads.codegear.com/threads/threads.exe/view?commentid=24923 2000-04-18T05:31:10-07:00 2000-04-18T05:31:10-07:00

Ten Things I Love About Delphi (and Hate about VB)

Hi, I have another extra hate/love comment about the use of VBA in applications.MICROSOFTACCESS------At work I am forced to use Access'97 because a customer uses it. Although VBA 5 is sufficient to me, it suffers with many (fatal) bugs. In Access 2K the bugs are gone. Here are they:repeatedly modyfying VBA modules especially when there are a lot of them causes a loss of stability with VBA 5. Some characteristuics are:A) opening/running the module causes a crash (ipf) in Kernel32. This looks like a serious damage in the database itself!B) the modules get "decompiled" (the binary code has expired, due to changes in the sources) when the database is opened, although I did not make any changes in the source. The compiled version should be contained when the source is unaffected.C) I have seen error 49 'Illegal calling convention in DLL', although I did not call any "Declare"d function.Strange huh, isn't it??These fake error messages and odd behaviour show that VBA 5 still has bugs, despite of the fact that Servive Pack 2 has been applied!When I repair/compact the database the code in the VBA modules do not get affected by these corrective actions, because the problems still remain! Ugh!The only possibility is to create a new blank database and open 2 sessions of Access: the faulty database and the new one. Dragging the objects from the faulty database and dropping them on the new one is a well-working solution, but is is a tedious job and forgetting one object might be fatal (run-time error)!BORLANDINTERBASE---------Interbase does not have this problem, because everything can be written in SQL even functions and real processing procedures. Dragging and dropping is not necessary, because the is a possibility to make REAL backups from the metadata and the normal actual data! It is even possible to generate a script containg the SQL for creating a database from scratch! Tom van der Vlugt http://threads.codegear.com/threads/threads.exe/userall?commentid=24922 http://threads.codegear.com/threads/threads.exe/view?commentid=24922 2000-04-18T05:25:20-07:00 2000-04-18T05:25:20-07:00

Ten Things I Love About Delphi (and Hate about VB)

Hi, I have another extra hate/love comment about the use of VBA in applications.MICROSOFTACCESS------At work I am forced to use Access'97 because a customer uses it. Although VBA 5 is sufficient to me, it suffers with many (fatal) bugs. In Access 2K the bugs are gone. Here are they:repeatedly modyfying VBA modules especially when there are a lot of them causes a loss of stability with VBA 5. Some characteristuics are:A) opening/running the module causes a crash (ipf) in Kernel32. This looks like a serious damage in the database itself!B) the modules get "decompiled" (the binary code has expired, due to changes in the sources) when the database is opened, although I did not make any changes in the source. The compiled version should be contained when the source is unaffected.C) I have seen error 49 'Illegal calling convention in DLL', although I did not call any "Declare"d function.Strange huh, isn't it??These fake error messages and odd behaviour show that VBA 5 still has bugs, despite of the fact that Servive Pack 2 has been applied!When I repair/compact the database the code in the VBA modules do not get affected by these corrective actions, because the problems still remain! Ugh!The only possibility is to create a new blank database and open 2 sessions of Access: the faulty database and the new one. Dragging the objects from the faulty database and dropping them on the new one is a well-working solution, but is is a tedious job and forgetting one object might be fatal (run-time error)!BORLANDINTERBASE---------Interbase does not have this problem, because everything can be written in SQL even functions and real processing procedures. Dragging and dropping is not necessary, because the is a possibility to make REAL backups from the metadata and the normal actual data! It is even possible to generate a script containg the SQL for creating a database from scratch!