Re: What this mean for Borland?

Captain,

granted, then, the original poster was already wring with saying "Object Oriented Pascal aka Delphi Language", since obviously OP is not aka Delphi. That said, Object Pascal is available for Visual Studio, so my response was perfectly correct.

The phrase "Visual Studio supports" is what was used. I'm fairly certain that most people reading that phrase understand it to mean

ah, noticing that the "OP vs. Delphi" argument was a dead-end, already?

> So, even if you ignore the "aka
Delphi Language" part of the statement, it is still true that VS.NET does not support Object Pascal.

Nope, it's not.

2) the OP plug-in that is available for VS only supports a proprietary
variation of OP that is not compatible with the Delphi language.
Delphi too is a proprietary variation of Object Pascal.

Yep, but it is not incompatible with the language "aka as the Delphi language". That is the very important difference you seem to miss in this discussion. The OP did not simply use the phrase "Object Pascal" by itself.

Right, he wasn't. He was equating Object Pascal with Delphi. "aka" clearly implies identity, a different name for the same thing.

That means that the availability of the Chrome plug-in in no way,size, shape or form makes it true that Visual Studio "supports Object Pascal aka the Delphi language".

Yes. Going down to your level of nitpicking, that statement cannot possibly ever be correct, because the talked about entity ("Object Pascal aka the Delphi language" doesn't exist.

The most accurate way to describe the situation is to say that "with Visual Studio it is possible to use a variant of Object Pascal if you get the Chrome add-in".

It might be more accurate, but that doesn't make any of the two statements false.

Thanx for playing,

--
marc hoffman
Chief Architect, .NET
RemObjects Software
http://www.remobjects.com

and the fifty-two daughters of the revolution
turn the gold to chrome
.