>
As others have already pointed out, you grossly overbloated the "minimum" C# class declaration syntax and presented an inaccurate comparison.
>

It was not *that* over-bloated. I took what VS .NET gives you by default. The central thesis of my issue rests with curly braces, case sensitivity, and semi-colon line termination.

In the end, the *minor* issue with my example is not material and does not impair my basic argument.

>I know you've stated you don't know anything about C#, C++, etc, but this sort of technically inaccurate post...something you've slammed many others for in the past...is irresponsible.
>

Kevin, you should know by now that it is never a good idea to put words in my mouth. I never said I did not know anything about C#. I did say that my knowledge of C++ and C was limited. I did say I had zero experience with Java.
As for using etc...be careful there because that is open ended. Bottom line, if you cannot quote me directly and accurately, don't quote me...

I went on to say that the fact that my C++/C knowledge was limited, it did not impair my ability to grasp C#. This was presented to counter your implication that somehow, a C++/C/Java background was necessary to quickly grasp C#.

Having said all that, if I have to choose between

public class Class1
	{
		public Class1()
		{
		}
	}

or

Public Class Class1
    
End Class

I'll choose the latter because IMO, it is more straightforward. I'll choose it because I prefer the syntax. Somebody else will choose C# for the same reason.
The important issue is that for the most part, .NET is a language agnostic environment...

The POINT of the comparision was in the context of the THREE issues I put forth as reasons why I don't PREFER C#. In other words, the issue had nothing to do with the class definitions per se, but rather the syntactical differences between the language that IMO, make C# less readable. I could have extended this comparison with code with variable declarations, etc. Of course, you can see some practical examples in my upcoming Code Magazine article on COM Interop in which I use both VB and C# < vbg >...

Kevin, if you are going to throw words back at me that I allegedely used, be sure they are words that I actually said. Again, if you are going to quote and/or paraphrase, get it right...

By now, you should know that I choose my words carefully and I know what I say and when I say it. There is a long history here of people mis quoting me only to realize that they grossly incorrect.

Kevin, I respect your right to run and operate your business as you see fit. However, when you come up here and fashion psuedo-technical arguments and further, use this medium for advertising, I reserve the right to respond in kind. As for being irresponsible, I am not sure that is a glass house you want to be throwing stones in...< s >...

In the end, you are basically taking the action I have advocated for the past several months. I take a certain satisfaction in that because you are the first VFP vendor to essentially validate my point. < bg > You may not have intended to do this - but nonetheless, this is exactly what you have done.

The only thing I disagree with is the way you are couching your choice of C# - not the fact that you have chosen C#. As long as you stress that language choice in this environment is largely one of pure preference, you will have no beef with me.

I seem to recall that you are pretty thin-skinned when it comes to critisim. If I recall correctly, you were pretty upset with the commentary I posted about your "events" article in FPA a few years ago. Like then, none of this is personal.