Hi Jim,
Well, if we are talking Visual Basic 6 that's true, but you need to understand that Visual Basic 6 is not 100% a procedural language nor was object oriented programming fully implemented either. The public and private declarations for subs, functions, and variables in Visual Basic 6 are borrowed from object oriented programming. No, what I was actually refering to is the difference between standard C and object oriented C++. Where the origeons of object oriented programming and design started. Although, object oriented C++ is based on standard C there were a lot of new concepts introduced in to C++ that C simply didn't have such as classes, public and private data types, objects, inheritance, pollimorphism, etc. C, as in the original C language, was strictly a procedural programming language. The closest C ever got to anything like object oriented programming is structs and unions, and neither of them were able to do the things you could do in a C++ class. For example, everything in a struct is public, structs can not be inherited, and you can not declare two functions of the same name inside a struct like you can in classes. That's why in the late 90's when languages like Java were introduced to programmers it started out using a object oriented design platform rather than the older C-style procedural design. When Microsoft released their .NET Framework in 2002 allof their languaes such as C# .NET, Visual Basic .NET, J# .NET, etc all moved to a full object oriented design. The days for procedural programming is pretty much ancient history in the professional programming world. Even the new Cobol standards introduced in 2010 implements a new object oriented design. So procedural programming is definitely on its way out of the professional and private sector in a hurry. Smile. On 12/19/10, Jim Kitchen <j...@kitchensinc.net> wrote: > Hi Thomas, > > Just one little correction I think. In procedural programming you can have > public and private variables. That is you can do things at the beginning > such as > > public SpeechRate > > or > > dim PlayersNames(10) > > And those variables are then global throughout your entire program. But you > can also do the same in a sub and those variables are then only accessible > in that sub. I E you can use the same variable in other subs and the values > etc are not carried over from one sub to another. > > And then there is a bad programming practice that I do all of the time and > that is that I do not even declare variables. Just use them on the fly as > it were. But that is only if you do not need to declare them such as > dimensioned arrays or if you need them to be global. > > BFN > > Jim --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gamers@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.
