quote:
Originally posted by vikke
quote:
Originally posted by CookieRevised
quote:
Originally posted by vikke
VB6 is certainly a 'more unstable language'. It's not made to use Win32 APIs for example.
what has that got to do with "more unstable language". Also, since when is VB6 "not made to use APIs". That's quite frankly totally and utterly wrong. The method and function declarations are especailly made for that.
The "Define Function" statement was added in later versions, because they needed to use WIN32 API, therefore it's not "made" to use APIs.
Sorry, but that doesn't make much sense though. It is also not true (eg: since VB1 you could call APIs, heck even QB already supported APIs).
quote:
Originally posted by vikke
quote:
Originally posted by CookieRevised
quote:
Originally posted by vikke
It's not using original constants etc.
??? constants need to be declared, even in C!
I meant the constants declared in windows.h
Even those constants must be defined in C, hence the windows.h file. Don't import that file and your C program wouldn't have a clue either. Add those constants to a file in VB6 and it does support them too just as well.
quote:
Originally posted by vikke
but that is also why you shouldn't use it as a language.
and why not? because you hate it? If you recommend using C for this, fine and good. But do not use those arguments you used as those are iether your opinion (which isn't based upon facts) or wrong information.
quote:
Originally posted by vikke
Still only possible with another language ActiveX/DLL in VB6.
activex or external DLLs are more convenient, but you still can do without them.
I don't care if you hate VB6 or not, you can hate whatever you want. But please don't talk about stuff you don't know or let that hate dictate your judgement.