Re: "pointers" in /clr

The frustrating part is that articles from Microsoft do not designate they
are for managed code only. There are many C++ articles out there and if
they are for Managed code then they need to state so. "MC++" would be VERY
acceptable! Please !!

Persons that have been developing in VC++ for many years might run into the
same issues that I do with my teams. If MS knows that the classes are
collected then the syntax should not matter. There should be no reason for
^ instead of * or % instead of &. Just stick to what's already trained into
people so we don't need to keep rewritting things but use all the tools.

If not, then at least really embrace the __gc and such because that looks
and feels more standard.

Personally, I feel that Microsoft did a great job with .NET and C++.NET/MC++
is awesome. It's not for all tasks but it's something to be very proud of
in the end. It will be more impressive when the Phoenix compiler is
complete and we can actually compile to native with all of these "cool
helper classes".

>> Syntax like this in anything that's called C++ is so frustrating. What
>> you have below is just garbage ... and I wish Microsoft would collect it.
>
> That's one opinion. Here is another:
>
> If one's goal is to develop a native application in standard C++ then the
> new syntax is beside the point as it will not be present.
>
> On the other hand, if one targets a platform whose objects are allowed to
> move around in memory without the knowledge or consent of the developer or
> his language, then it is unreasonable to assume that the standard
> language, which makes no provision for such movement, will be expressive
> enough without changes.
>
> Regards,
> Will

--
new
.

Relevant Pages

  • Re: CUJ and Microsoft C++
    ... neither CUJ nor Microsoft has more weight than anyone ... else on the standard committee. ... standard than abdications that lead to a bastardization of the language. ... > they have achieved 100% Standards Compliance?" ...
    (comp.lang.cpp)
  • Re: PL/I, COBOL, Advantages, Equivalence, et al
    ... And speaking of standards where is the standard for Java, ... The C# language, the existence of which may have been motivated ... by the evil intent of Microsoft policy, ... I will admit that the reason for creating C# in the first ...
    (comp.lang.pl1)
  • Re: Compiling code at runtime
    ... >>Microsoft specific implementations of languages. ... VB isn't a language either, the language behind it is BASIC, but it's ... .NET is not a standard, no matter how much Microsoft's prophet William ... work with other programming languages to do this kind of thing. ...
    (comp.lang.java)
  • Re: Operator overloading in C
    ... hearing if couched in less inflammatory language. ... done till now in the standard. ... Microsoft both leaving the implementation of C99 to ... studying any proposals. ...
    (comp.std.c)
  • Re: Disadvantages of C#??? just curious
    ... the next Microsoft "flavor of the decade". ... very stable language that has been around for about 30 years and has ... now an open standard, ...
    (microsoft.public.dotnet.languages.csharp)