Hello Gleason, Saturday, February 2, 2008, 12:06:19 AM, you wrote:
GP> Kyle, GP> GP>> The unhappy truth of programming is that functions are interrelated GP>> in ways that often baffle non-programmers. Is it necessary for a working GP>> function to no longer work simply because some change has been made? GP>> Such things do often happen. Guess I should have offered more credentials before speaking about programming/debug techniques to qualify my concerns. I am a retired IS professional who was a MCSE, and retired as a fully qualifed IBM Systems Programmer. I started in programming long before the PC was even a glimmer on the personal horizon as an assembler programmer. I worked on most of the Mini-computers of that era before entering the mainframe arena. I worked on development progjects like "sequential processing delivery" for Arpanet (what is now referred to as "The Internet"). I built my own 8080 personal computer, etiched my own motherboard for it (it worked!) and coded assembler routines(drivers) for that PC. I have programmed in many languages that most of you probably have never heard of or only read about in history books. (Algol,Lobol,Cobol,Fortan,Pascal,C,C++,etc) I have paid my dues and know a bit about how successful program development works. I understand the risks of using a development system, but as I stated before, even with a deveopment effort, there has to be structure to deveopment or you end up shooting yourself in the foot too many times (been there, done that). My point here is that to effectivey assist in deveopment, there needs(has to be) a base line of stability (regression style never works well) so that testers can effectively test new code paths. If the base changes with each feature inclusion, where is the base for metrics? Structure breeds structure. Take Open Source Programming as an example. With each OS project, there is a base line that everyone has to respect, deveopment is modular and adaptable. Where would linux be now if with every update the kernel was not kept static? Again, I am simply trying to understand the methodology of development and try to be a positive contributor to the deveopment. Right now, I can't see how to help as I don't know from one release to the next if the things that worked will still be working so that i can relate stability to instability. The core users here are positive, friendly and seem to know the product well. What say you fellows? Am I way off base here? Again, these comments are intended to be positive and constructive, I mean no harm and only wish to be of assistance. -- Best regards, Kyle mailto:[EMAIL PROTECTED] ________________________________________________________ Current beta is 4.0.0.17 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
