Board index » delphi » Delphi vs. Visual Basic, Microsoft downplays delphi

Delphi vs. Visual Basic, Microsoft downplays delphi

Quote
sc...@metropolis.nl (Scott Beltgens) writes:
>dbeu...@us.oracle.com (Don Beusee) wrote:

>>>>Finally he suggested that development time may be shorter for visual
>>>>basic in many applications.

>>This is definately true.  I have both and I can develop much faster in VB
>>because of its superior debugging and virtually no GPF's.

>Superior debugging?????? Come on, get serious.
>I'm an professional VB(4) and Delphi developer and VB doesn't even
>come close to Delphi's de{*word*81}. In fact, I can not say that the VB
>de{*word*81} even is a REAL one, the watcher functions (debug window) are
>very limited and do not (automaticly) update while stepping to the
>source.

I am [very] serious!!  What are you talking about?  MY watch window DOES
update when stepping through! And by superior debugging, I mean I can change
the code **AND CONTINUE** executing from that spot forward.. No recompile, no
re-enter app data to get to that point in code, no switch between app and
de{*word*81}..  Also, in VB I can set next statement and re-execute a code segment
if I missed the point I need to break at or re-run code after changing,
etc...  This is superior debugging.

Quote
>True, it takes some time to switch between app and de{*word*81} with
>Delphi, but only if you are 'low' on memory. On my 20MB and 24Mb
>machines the speed of Delphi's de{*word*81} beats VB4.

>From all true compilers/languages I've seen, Delphi has the fastes
>de{*word*81} of all.

Sorry, but Delphi de{*word*81} does not beat VB in features.  Can you set next
statement?  Of course not!  Can you change code and continue execution?  Nope!

Quote
>BTW: If you don't want to break on every GPF in Delphi, just turn that
>option off!

Huh?  My program DIES when I get a GPF!  In VB, I avoid the GPF game
altogether!!

Quote
>Bye,
>    Scott.

Regards,
Don.
 

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


VB's de{*word*81} definitely better.  The fact that you can change code and
continue executing your code is fabulous.

--
Alexander Medwedew
Computer Ventures, Inc.
compv...@tribeca.ios.com
http://tribeca.ios.com/~compvent/
CADVANCE LITE - Affordable CAD Software
http://tribeca.ios.com/~compvent/cadvlite.html

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


In article <4adndi$...@news2.ios.com>,
   Alexander Medwedew <compv...@tribeca.ios.com> wrote:

Quote
>VB's de{*word*81} definitely better.  The fact that you can change code and
>continue executing your code is fabulous.

Yes, but this is due to the fact that running a VB app uses an interpreter
against the code, instead of running the app as an executable.  It would be
extrememly difficult for Delphi to accomplish a similar feat (running without
recompiling the executable).

When given the choice of having this feature or being able to distribute my
apps as a single EXE, I would definitely take the latter.

----
Dean Tessman
Faculty of Business
University of Alberta
dtess...@gpu.srv.ualberta.ca

I love animals.  They're delicious.

Check out the SlipBar at www.ualberta.ca/~dtessman/programmer.html

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


On 10 Dec 1995, Alexander Medwedew wrote:

Quote
> VB's de{*word*81} definitely better.  The fact that you can change code and
> continue executing your code is fabulous.

But doesn't this ability allow errors to be introduced in the program
during the debugging session?  By forcing a compile due to any code
change is actually good, for me anyway, because it will uncover the
errors I have introduced to my code.

joseph

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


Quote
Joseph Laurino <bytew...@u.washington.edu> wrote:
>But doesn't this ability allow errors to be introduced in the program
>during the debugging session?  By forcing a compile due to any code
>change is actually good, for me anyway, because it will uncover the
>errors I have introduced to my code.

It is possible to create logical errors but syntax errors are checked as
you code.

--
Alexander Medwedew
Computer Ventures, Inc.
compv...@tribeca.ios.com
http://tribeca.ios.com/~compvent/
CADVANCE LITE - Affordable CAD Software
http://tribeca.ios.com/~compvent/cadvlite.html

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


If you are using VB 4.0 chances are that you would not get
GPFs because it is a Win 95 app.  Delphi 16 is a Win 3.x app
and can cause GPF's even in Win95.  Compare VB 4.0 and Delphi
32 and neither will cause GPFs.

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


Quote
Joseph Laurino (bytew...@u.washington.edu) wrote:

: On 10 Dec 1995, Alexander Medwedew wrote:

: > VB's de{*word*81} definitely better.  The fact that you can change code and
: > continue executing your code is fabulous.
: >

: But doesn't this ability allow errors to be introduced in the program
: during the debugging session?  By forcing a compile due to any code
: change is actually good, for me anyway, because it will uncover the
: errors I have introduced to my code.

: joseph

It is just a symptom of the fact that VB is a hacker's dream and a software
engineer's nightmare!  (Well, it is getting a bit cold round here - that should
turn up the flames :-)

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


Quote
In article <4adndi$...@news2.ios.com>, Alexander Medwedew (compv...@tribeca.ios.com) writes:
>VB's de{*word*81} definitely better.  The fact that you can change code and
>continue executing your code is fabulous.

Surely this is only possible beacuse VB is NOT a compiler but
really an interpreter. For a compiler to allow changes to code it
would need to unload the exe, recompile, reload the new exe and
somehow get you to the point you were previously at.
Sounds a bit of a tall order to me.

Alistair Cooper
Burgess Hill, West Sussex, England (acoo...@dolphan.win-uk.net)

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


Hello all!

I've tried to print graphics from a Delphi program and it seems that
it is impossible to print bitmaps to a PostScript printer. Everything
else on the page is fine but bitmaps are missing.  

I don't understand what could be wrong because one of the demo programs
(graphwin.pas) has the same problem. If you know the solution please
post it or e-mail it to me.

Thank you in advance.
Matti Aaltonen
VTT Information Technology
Finland

--
Matti Aaltonen                          VTT TTE / TJ / THTJ
p. (931) 3163 344

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


Quote
Annie Random <natio...@basil.stthom.edu> wrote:
>If you are using VB 4.0 chances are that you would not get
>GPFs because it is a Win 95 app.  Delphi 16 is a Win 3.x app
>and can cause GPF's even in Win95.  Compare VB 4.0 and Delphi
>32 and neither will cause GPFs.

Annie,

A General Protection Fault occurs when your program writes to
memory that has not been allocated to your app, that is what
protected memory is all about. Play with OLE automation in VB4
32 for any period of time and I bet you will see a GPF or 2 I
know I did, and come Feb I can guarantee if you want to you can
get a GPF or 2 in Delphi 32 also.

Regards Tim Jarvis.

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


In article <4adndi$...@news2.ios.com>,
   Alexander Medwedew <compv...@tribeca.ios.com> wrote:

Quote
>VB's de{*word*81} definitely better.  The fact that you can change code and
>continue executing your code is fabulous.

Isn't this a "feature" of an interpreted language (versus a compiled one), and
not a "feature" of the de{*word*81} in question?  You VB fanatics are cute, but
you need to get your facts straight.

Kendall

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


In article <4ai9hb$...@gryphon.phoenix.net>,
   Annie Random <natio...@basil.stthom.edu> wrote:

Quote
>and can cause GPF's even in Win95.  Compare VB 4.0 and Delphi
>32 and neither will cause GPFs.

You mean Microsoft renamed the Windows crash yet again?  What's it called in
Windows 95 when you crash?

Kendall

Re:Delphi vs. Visual Basic, Microsoft downplays delphi


kend...@his.com (Kendall P. Bullen) wrote:

Quote
>In article <4ai9hb$...@gryphon.phoenix.net>,
>   Annie Random <natio...@basil.stthom.edu> wrote:
>>and can cause GPF's even in Win95.  Compare VB 4.0 and Delphi
>>32 and neither will cause GPFs.
>You mean Microsoft renamed the Windows crash yet again?  What's it called in
>Windows 95 when you crash?

Wouldn't it be great...imagine no more crashes :)    Get real ! A lot
of the old code from windows 3.1 is still there in windows 95 and I
have managed to crash 95 quite a lot. You've still got to reboot if
your app crashes in order to be sure that the system is clean!

Shane Cunningham
Dublin, Ireland
shc...@iol.ie

Go to page: [1] [2]

Other Threads