Re: What this mean for Borland?

"marc hoffman" <mh@xxxxxxxxxxxxxxx> wrote in message
news:442c552f$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Technically, Chrome is not the "Delphi Language" though. It is a variant
of Object Pascal. It is somewhat misleading to say that Visual Studio
supports "Object Oriented Pascal aka Delphi Language", since 1) there is
no support for either object pascal nor the Delphi language out of the
box in VS, and

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 you can use it
out of the box for the functionality it "supports", not that if you spend
additional money you can use an add-in that lets you use it. Otherwise, it
would be like saying that "D2006 supports CF", because you can use a
third-party add-in to create CF stuff. 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.


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.

So whether VS
would support Chrome, Delphi or FooBarPascal with Objects 3.0, it would
support Object Pascal. Since it does support ONE of them, it does support
OP. Simple really.

Well, as I pointed out above, it "supports" none of them. The situation is
that you can use a variant of Object Pascal with it if you spend additional
money. You can not use the language referred to as "aka Delphi language" no
matter what you do. Chrome is incompatible with the Delphi language, a
choice you made (and I disagreed with very strongly). 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".
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". That is a far cry from saying that "Visual Studio supports
Object Pascal".


.

Relevant Pages

  • Re: What this mean for Borland?
    ... 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. ...
    (borland.public.delphi.non-technical)
  • Re: What this mean for Borland?
    ... It is somewhat misleading to say that Visual Studio supports "Object Oriented Pascal aka Delphi Language", since 1) there is no support for either object pascal nor the Delphi language out of the box in VS, and ... Oriented Pascal aka Delphi Language", since obviously OP is not aka Delphi. ... So whether VS would support Chrome, Delphi or FooBarPascal with Objects 3.0, it would support Object Pascal. ...
    (borland.public.delphi.non-technical)
  • Re: Limited by Nonsense
    ... > That they most likely are working on implementing support for .Net v2 ... > That they most likely are working on generics syntax in Delphi language ... Lauchlan M ... Prev by Date: ...
    (borland.public.delphi.non-technical)