Some general comments re. Delphi compared with Visual Studio and C#
...(These may be useful to someone? Any additional comments welcome ...)

Delphi has readable operators like "not", "and", "or" rather than ! &&
|| ...

Could argue that Pascal leads programmer to better organising their
code. i.e. Variable declarations are separated from program code.
Functions and procedures are catalogued upfront. Delphi is much more
likely to keep self generated code separate from user written code. C#
can jumble user written items in with designer written items.

Delphi IDE does more for the programmer in terms of component renames
and automatic code update to match renames. Delphi will remove empty
procedures that it has created. Visual Studio will leave empty event
handlers behind ..

It seems..Delphi online Help is more likely to show commonly required
functionality. It wasn't all that easy finding out how via online help
how to use C# to open and write to a file when you want to overwrite the
file contents if it already exists ...

Delphi has a freeware "delfor" code formatter that can be found on the
web that does a complete code check and performs indentation for you
(with preferences settings available). (Visual Studio will do some
indentation if you remove and re-add the final closing } )
Delphi has component help hints built in without requiring a tool-tips
add-in.
Delphi application security is not so complicated. i.e. you can run a
Delphi exe from a network drive.
Assignment with := and testing with = in pascal compared with = and ==
in C#
Delphi IDE doesn't have user battling quite so much with properties form
wanting to dock everywhere.
Delphi IDE allows forms to be designed to take up more of the screen,
guess you can switch to a higher resolution to do similar in Visual
Studio
Delphi IDE gives more precise control over windows form control
position, height, width ...
Delphi dates are less complicated to work with..
Delphi string lists have add("text")   (C# programs can be bogged down
as C# strings are immutable ..i.e. use string builder and append ...)
Delphi has support for ini files.   (you can find C# ini file examples
via google however.)
Delphi database result set lets you use fieldbyname("colname").AsString
fieldbyname("colname").AsDateTime fieldbyname("colname").AsFloat ...
which is less verbose in the code than C# calling the Convert class ...

Delphi has a TMemo component ... C# has textbox with multiline but then
you have to use string builder or otherwise strings are handled
inefficiently and your program response time really bogs down ..

cheers,
Allan Ford.


Santos Ltd A.B.N. 80 007 550 923
Disclaimer: The information contained in this email is intended only for the 
use of the
person(s) to whom it is addressed and may be confidential or contain
privileged information. If you are not the intended recipient you are hereby
notified that any perusal, use, distribution, copying or disclosure is strictly
prohibited.  If you have received this email in error please immediately
advise us by return email and delete the email without making a copy.
__________________________________________________
Delphi-Talk mailing list -> [email protected]
http://www.elists.org/mailman/listinfo/delphi-talk

Reply via email to