|
-
Mar 23rd, 2000, 06:00 AM
#1
Is there any difference between the two?
Thanks in advance
-
Mar 23rd, 2000, 06:19 AM
#2
Member
VC++ is Microsoft's compiler for the C++ language. It stands for Visual C++ just like how VB stands for Visual Basic. There are other C++ compilers such as Borland's C++Builder. C++ is a programming language.
-
Mar 23rd, 2000, 09:53 AM
#3
So I guess that general method of making programs is the same. Am I correct?
-
Mar 23rd, 2000, 12:02 PM
#4
Member
I think it's generally the same. There might be some extra functions or tools in addition to the C++ language. I have the Borland compiler so I don't know much about VC++. I heard that it's better than Borland though.
-
Mar 23rd, 2000, 01:16 PM
#5
Lively Member
for me, VC++ is better...
GUI applications are easier to make
(I think of it as one of the reason
why the language was prefixed with
"Visual"... )
-
Mar 23rd, 2000, 01:20 PM
#6
Fanatic Member
I have both VC++ and the borland C++ builder 4, the VC++ is more powerful but you have to know MFC backword in order to get your productivity above zero so I don't use it.
BCB 4.0 is easier to use (a RAD a bit like VB) but not really much more powerful than VB and with shocking DB support.
I always wanted to move to C++ because I like some parts of the language better but after using those compilers and seeing VB NextGen... I'm in VB to stay. The speed differences are minimal really, don't let a C++ programmer tell you otherwise. ANSI C is quite fast though, but good program design is faster.
-
Mar 23rd, 2000, 01:22 PM
#7
Fanatic Member
for me, VC++ is better...
GUI applications are easier to make
(I think of it as one of the reason
why the language was prefixed with
"Visual"... )
Are you serious ???????? Everyone I talk to says, "Why is the word 'Visual' in VC++ ??"
Try it for yourself, after using VB... you'll hate it.
-
Mar 23rd, 2000, 02:31 PM
#8
Hyperactive Member
I think the only reason why they called it Visual C++ is because it comes with a nice editor (which supports macro's woohoo!), but it sucks creating a nice interface, most of the stuff has to be done in code instead of Visually creating the whole stuff. Borland's C++ Builder is much better then that.
Although it's called Visual C++ it's actually Visual (?) MFC I think, since you'll write MFC code most of the time.
And what I've heard and seen, Borland is more Ansi compliant then M$ is...
-
Mar 23rd, 2000, 04:49 PM
#9
Fanatic Member
I agree absolutely
Borland is MUCH easier to use but some of the components are old. It uses VCL instead of activeX (which is supported though) but the RTFBox control is a LOT slower than VBs and almost stalls the system in a resize of a 3 mb document.
VC++ has a few RAD features but on large projects you can pretty much forget them.
The thing I don't like about both of them though is that they force you to write Object Oriented code which sux the big one for quick tools and what not. Sometimes having to write 10 new Classes is an overkill. I like straight C though, but in C for windows programming is just API calls all the way, YUK.
Why do VB programmers have this inferiority complex??? try Borland C++ builder! which is C++ with a RAD, you'll be back I guarentee it, the performance difference is often hard to spot and sometimes not even there.
Get over it guys, VB kicks butt.
-
Mar 23rd, 2000, 05:06 PM
#10
Hyperactive Member
I agree, most of the times you won't even notice a performance difference, since most of the apps are waiting for user input, so if the user types faster, the app goes faster :-)
But seriously, only a very few ocassion really require some heavy stuff you can do with C++ and not with VB. Especially file i/o and drawing operations.
The only huge advantages with C++ is that you have the option to link static, so for a little tool, for someone of which you're not sure if he/she has the VB runtime stuff, that's a huge advantage. BUT, once the person has the VB runtime, a VB app is smaller then a static linked C++ app...
For me, the only real reason for using C++ is that I like the language...
-
Mar 23rd, 2000, 08:51 PM
#11
Fanatic Member
I agree with the graphics porcessing but file I/O no way. If you use byte arrays with binary get/put you have heaps of power. I was so happy I wrote an ActiveX control to look after all my data management (I/O) even if your after text strings try this ( I copied it from my control) you pass it a file path and a 'pointer' to an array
Code:
Public Property Get TextFromBinary(bBytes() As Byte) As String
If UBound(bBytes) < 1 Then
TextFromFile = StrConv(bBytes, vbUnicode)
Else
Err.Raise 2, , "pointer to Empty Byte Array Passed"
End If
End Property
Public Function LoadFile(ByVal Pathname As String, bBytes() As Byte) As Integer
On Error GoTo ERROR
txtPath = Pathname
lgFileLength = FileLen(txtPath)
dtLastModified = FileDateTime(txtPath)
ReDim bBytes(lgFileLength)
Open txtPath For Binary As 1
Get #1, 1, bBytes
Close
bFileLoaded = True
RaiseEvent CopyComplete
LoadFile = 1
Exit Function
ERROR:
LoadFile = 0
End Function
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|