vb 6 is too slow to handle string array, c # is same as vb or its faster? forget about c++ because i can't program in c++ i hope c# is easier.
thanz in advance
Printable View
vb 6 is too slow to handle string array, c # is same as vb or its faster? forget about c++ because i can't program in c++ i hope c# is easier.
thanz in advance
I think C# string functions will be as lame as vbs
Why do you say that VB string functions are lame? They are the only reason I still use VB for anything.
Z.
vb's string functions are very slow. And I'm wondering C# will have the same problem.
You'd be a lot better off in C++ if you're only concerned for speed, and I agree with Zaei, the power in VB is it's strings and a range of other RAD tools that speeds up developement.
c++ difficulttttttttt to write in. I'm strugling with c++ for about a month and nothing happening. If c# allow me to build stand alone programs then i'll probably move to c#.
c# and the other .net apps will be stuck with their fat runtime
c++ 7.0 would need runtime too?
There's no such thing as 'C++ 7.0', C++ is a language, and I think you're talking about Visual C++, which is Microsoft's IDE and C++ compiler.
C++ is never going to need runtimes other than those you make your apps rely on.
C++ is just in a completely different league, playing a different game to C#. C# is a lot like Java in its principles; it's run in a virtual machine using the Common Language Runtime. C++ is compiled code, not interpreted.
If speed of execution is your primary concern then use C or C++. If you are more interested in speed of development, then use something higher-level like Java, VB, C# or Python.
It should be clear which is more appropriate for your situation because the languages are meant for very different purposes.
You can compile C++ down to the CLR as well, in which case you'd need .NET as well.
As it goes, I'm using beta 1 (not got anything else) of vc++7 as my normal development compiler - if I don't use the runtime DLLs then nobody need notice, and it makes my life easier.
You can compile C++ down to the CLR as well, in which case you'd need .NET as well.
As it goes, I'm using beta 1 (not got anything else) of vc++7 as my normal development compiler - if I don't use the runtime DLLs then nobody need notice, and it makes my life easier.
But I still use VB for databases or if I really need a windows program out fast - I usually just knock up a console-mode program in C++ for anything like that.
For string handling, I'd take Perl any time though :cool:
Console programs rock... brings back memories =).
I usually only use VB if I want to test something graphical out quickly, or if I need to do some text file parsing.
Z.
text file parsing, thats what i used VB for some months ago, other than that i can't remember. I've been using console apps all the time, testings and more testings, asm listings and testing again... :p
I use console when I want to test something of the language itself, GUI when testing something API and MFC for the real apps.
The only contact with VB (the one that brought me here) was when I translated a VB algorithm to C (10-30 times faster :) )
I'm going to start getting nightmares about those sodding VC++ asm listings, I've seen so many :eek:Quote:
Originally posted by kedaman
text file parsing, thats what i used VB for some months ago, other than that i can't remember. I've been using console apps all the time, testings and more testings, asm listings and testing again... :p
ARGHHH! inline you bastard inline! :DQuote:
Originally posted by parksie
I'm going to start getting nightmares about those sodding VC++ asm listings, I've seen so many :eek:
:DQuote:
Originally posted by kedaman
ARGHHH! inline you bastard inline! :D
But they won't :rolleyes: :p