«

FYI.

Microsoft Visual C++ Toolkit 2003

The Microsoft Visual C++ Toolkit 2003 includes the core tools
developers need to compile and link C++-based applications for Windows
and the .NET Common Language Runtime:

Microsoft C/C++ Optimizing Compiler and Linker. These are the same
compiler and linker that ship with Visual Studio .NET 2003
Professional!

C Runtime Library and the C++ Standard Library, including the Standard
Template Library. These are the same static-link libraries included
with Visual Studio.

Microsoft .NET Framework Common Language Runtime. Visual C++ can
optionally build applications that target the Common Language Runtime
(CLR).

Sample code. The toolkit includes four samples designed to showcase
the powerful new features of the 2003 version, including new
optimization capabilities, features to improve code-security and
robustness, enhanced ISO C++ standards support, and the ability to use
the .NET Framework library and target the CLR.

[Download the Visual C++ Toolkit 2003:
http://www.microsoft.com/downloads/d...isplaylang=en]

[From http://msdn.microsoft.com/visualc/vctoolkit2003/]

v4vijayakumar wrote:
> FYI.
>
> Microsoft Visual C++ Toolkit 2003

<snip>

Now tell me why it should be of interest? Apart from the fact that most
of my current development is for Linux and AIX, these groups are not for
specific tools but the language itself.

In any case, we (on comp.lang.c) already have a far longer list of
freely available compilers at http://clc-wiki.net/wiki/C_Compilers which
will show that you are advertising an old version rather than the
current version.
--
Flash Gordon, living in interesting times.
Web site - http://home.flash-gordon.me.uk/
comp.lang.c posting guidelines and intro:
http://clc-wiki.net/wiki/Intro_to_clc

v4vijayakumar wrote:
> FYI.
>
> Microsoft Visual C++ Toolkit 2003
>
> The Microsoft Visual C++ Toolkit 2003 includes the core tools
> developers need to compile and link C++-based applications for Windows
> and the .NET Common Language Runtime:
>
> Microsoft C/C++ Optimizing Compiler and Linker. These are the same
> compiler and linker that ship with Visual Studio .NET 2003
> Professional!
>
> C Runtime Library and the C++ Standard Library, including the Standard
> Template Library. These are the same static-link libraries included
> with Visual Studio.
>
> Microsoft .NET Framework Common Language Runtime. Visual C++ can
> optionally build applications that target the Common Language Runtime
> (CLR).
>
> Sample code. The toolkit includes four samples designed to showcase
> the powerful new features of the 2003 version, including new
> optimization capabilities, features to improve code-security and
> robustness, enhanced ISO C++ standards support, and the ability to use
> the .NET Framework library and target the CLR.
>
> [Download the Visual C++ Toolkit 2003:
> http://www.microsoft.com/downloads/d...isplaylang=en]
>
> [From http://msdn.microsoft.com/visualc/vctoolkit2003/]

I think you have come to the wrong place.
This group is meant for "Discussion about C" as the group description
says.
Why are you posting the advertisement for such tools in this group ?

> Now tell me why it should be of interest? Apart from the fact that
> most
> of my current development is for Linux and AIX, these groups are not
> for specific tools but the language itself.

I _am_ interested, since I finally can replace my VC7.1 GERMAN
compiler with an ENGLISH one!!! Now I can understand my error messages
better, because a translation made things worse (Siemens Syndrome).

-Gernot

Gernot Frisch wrote:
> > Now tell me why it should be of interest? Apart from the fact that
> > most
> > of my current development is for Linux and AIX, these groups are not
> > for specific tools but the language itself.
>
> I _am_ interested, since I finally can replace my VC7.1 GERMAN
> compiler with an ENGLISH one!!! Now I can understand my error messages
> better, because a translation made things worse (Siemens Syndrome).

I'm happy for you.

That, however, still does not make c.l.c a place to exchange this sort
fo information.

"Vladimir Oka" <> schrieb im Newsbeitrag
news: ups.com...
>
> Gernot Frisch wrote:
>> > Now tell me why it should be of interest? Apart from the fact
>> > that
>> > most
>> > of my current development is for Linux and AIX, these groups are
>> > not
>> > for specific tools but the language itself.
>>
>> I _am_ interested, since I finally can replace my VC7.1 GERMAN
>> compiler with an ENGLISH one!!! Now I can understand my error
>> messages
>> better, because a translation made things worse (Siemens Syndrome).
>
> I'm happy for you.
>
> That, however, still does not make c.l.c a place to exchange this
> sort
> fo information.

OK. You're right.
</Thread>

"Gernot Frisch" <> wrote in message
news:
>> Now tell me why it should be of interest? Apart from the fact that
>> most
>> of my current development is for Linux and AIX, these groups are not
>> for specific tools but the language itself.
>
> I _am_ interested, since I finally can replace my VC7.1 GERMAN
> compiler with an ENGLISH one!!! Now I can understand my error messages
> better, because a translation made things worse (Siemens Syndrome).
>
> -Gernot


Get the current version. Then you don't have to suffer a command line
interface.

http://msdn.microsoft.com/vstudio/ex...c/default.aspx


--
John Carson

John Carson wrote:
> "Gernot Frisch" <> wrote in message
>
>>> Now tell me why it should be of interest? Apart from the fact
>>> that most of my current development is for Linux and AIX, these
>>> groups are not for specific tools but the language itself.
>>
>> I _am_ interested, since I finally can replace my VC7.1 GERMAN
>> compiler with an ENGLISH one!!! Now I can understand my error
>> messages better, because a translation made things worse
>> (Siemens Syndrome).
>
> Get the current version. Then you don't have to suffer a command
> line interface.
>
> http://msdn.microsoft.com/vstudio/ex...c/default.aspx

Why do you want him to suffer from a GUI interface? How cruel.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
More details at: <http://cfaj.freeshell.org/google/>
Also see <http://www.safalra.com/special/googlegroupsreply/>

"CBFalconer" <> wrote in message
news:
> John Carson wrote:
>> "Gernot Frisch" <> wrote in message
>>
>>>> Now tell me why it should be of interest? Apart from the fact
>>>> that most of my current development is for Linux and AIX, these
>>>> groups are not for specific tools but the language itself.
>>>
>>> I _am_ interested, since I finally can replace my VC7.1 GERMAN
>>> compiler with an ENGLISH one!!! Now I can understand my error
>>> messages better, because a translation made things worse
>>> (Siemens Syndrome).
>>
>> Get the current version. Then you don't have to suffer a command
>> line interface.
>>
>> http://msdn.microsoft.com/vstudio/ex...c/default.aspx
>
> Why do you want him to suffer from a GUI interface? How cruel.


People with normal emotional adjustment (and people interested in maximizing
productivity) prefer GUI interfaces.

This of course raises the question of the best way to respond to people with
abnormal emotional adjustment who prefer command line interfaces. This takes
us into ethical deep waters. I am reminded of a discussion among some
friends a while ago about whether there should be intervention in a
(hypothetical) relationship in which one partner likes to be beaten. One
view was that the person's preferences should be respected. Another was that
those preferences were likely the result of mistreatment in the past and
thus to treat the preferences as sacrosanct would just perpetuate a pattern
of abuse.

Opinions differ on this. I'm inclined to be interventionist myself --- while
acknowledging that these matters need to be handled with sensitivity.

--
John Carson

John Carson wrote:
> "CBFalconer" <> wrote in message
> news:
> > John Carson wrote:
> >>
> >> Get the current version. Then you don't have to suffer a command
> >> line interface.
> >
> > Why do you want him to suffer from a GUI interface? How cruel.
>
> People with normal emotional adjustment (and people interested in maximizing
> productivity) prefer GUI interfaces.

You make yourself look ridiculous.