VBGamer

Yes, you are missing the major importance of pointers. They do reference memory addresses, correct, but just using them as variables is not the point. First case in point. VB can't directly make a pointer to a function in memory. There are, according to what I have tried, about four different ways to do this in VB, however, all four are volitile for and OS of the M$ variety (window procedures, direct vtable calls, etx.) Second case, usually the major reason to use them in the first place, passing variables by reference to functions in C/C++. They don't have a transparent layer like in VB (with a simple BYREF command). Third, you can manage the free store (the memory pool) directly. Basically, use Java and you get the automatic garbage collection, so this is really old school stuff. Fourth, OOP !! Direct access to class member data and functions (as pointed -- np pun intended -- out in #1) I usually stay away from pointers, cause references in C++ are 10000% easier to track bugs in, and just look prettier. However, if you need to switch one reference for another, you have to use pointers. All in all, I have not accomplished one thing in C/C++ that I can not do in VB. And the speed really doesn't bother me (course the athlon 800 I dev on might have something to do with that). But seriously, VB is an excellent tool. Don't be afraid of C/C++ though. It is worth the effort, as you can port just the majorly bad things (memory managers for instance) into it, since it is constructed for that type of work. Wait for the OOP in VB7, don't let that decide for you. A lot of C++ newbies think this is the greatest thing since the wheel, and quite honestly, they couldn't code their way out of a paper bag using it. I have seen sooooooo much sloppy code written by those who have no basic understanding of code flow, just cause they learned how to use the OOP features. DOH.