coates@uc780.umd.edu (06/26/91)
I take it by now you've read that my code listing was an accident. The reason I wrote to the issue of identifiers and their declaration and definition was to respond to said issue in the Visual Basic thread in this group. I had second thoughts about persuing the issue and did not intend to send the fragment in the listing relevant to my point, but I accidentally sent not just the fragment but the whole listing. Upon discovering that I had sent the listing I sent another message with reference to the above issue. (Making lemonade out of lemons.) On second thought I don't think it's a bad idea to persue issues seemingly tangential to a group if in some way the issue has some value to the group. I feel the thread ref. Visual Basic has value to comp.windows.ms.programmer in that I think its good for Windoiws programmers to think about why we use the tools we do, who exactly is involved in Windows programming, what fellow programmers want to do with their programs and what methods and issues are involved in programming for Windows. I don't think comp.windows.ms.programmer should be solely about the technical aspects of Windows programming, but about Windows programming's place, space and approach in terms of the world generally and programming specifically. The discuusion about the langauges and the nature of the langauges used in Windows programming is apropo in comp.windows.ms.programmer. Again, it isn't the whole or primary ball of wax with regard to the group's title, but it is a very relevant part. Cheers! ************************************************************************** * Elliott Coates, washington dc * * coates@uc780.umd.edu * * coates@uc780.bitnet * **************************************************************************