Re: where is a copy of atlstr.h ??

Stephen Howe wrote:
> > It is NOT unreasonable to expect some kind of response to a search at
> > MS website for atlstr.h
> >
> > At least something like, "Glad you asked, but that only comes in
> > purchased software, and you'll really like it."
>
> That is not reasonable. There are 1000's of files that comes with Visual
> Studio or Visual C++, should every file be listed as to which product(s) it
> is available under? Just because you formulate a question, does not mean it
> is reasonable question, nor should MS spend time wrinting documents to
> answer it.

Why not? It's their product. They're trying to sell it. And google
certainly finds things quickly.

> And since I know what
>
> #include <stdio.h>
>
> does, I don't care where it is located. Futhermore, for some C and C++
> compilers, there is no reason, at all, for stdio.h to be a file. I remember
> with one previous version of Visual Studio, MFC and ATL headers were in
> separate directories. Now they are not.

First thing I did was a full search of the C: drive for the locations.
For other "hiding" headers several lines were added to the compile
batch file
Set INCLUDE=C:\lots of places;%INCLUDE%
....but have to have the file to use the file

> Yes but a quick file find should have established that none of the other MFC
> or ATL header files are present on your computer. Your next thought should
> have been "Does MFC or ATL come with any of the Microsoft products I have
> installed?", a quick Google and you would know the answer.

Actually, there are some 75 atl*.h files on the WinXP system, so I
thought this "key" one was there also.

> And it is not just headers but the associated libriares they pair with (and
> possible DLLs).
> Without those you are stuffed. A header is useless in isolation.
> And a header is useless if you don't have the correct matching libraries.
> You will run into "undefined symbols" on linking.

Good point, and probably likely. Again, being specific when I searched
would help.

> Not rhetorical. You wanted to use the C++ compiler => you should have read
> the FAQ on it.
> A few paragraphs ago you were grumbling about missing documentation, now you
> saying you don't need to read documentation that is available by Microsoft
> on the product you are trying to use. Seems inconsistent to me. The FAQ on
> any new product (and the README.TXT/README.HTM) are the first thing to read
> just in case there are last minute "gotchas" I need to know about. So 3 days
> to find out what you needed to know seems excessive.

I read, but then there's read. If what is written makes no/little
sense, reading more only exacerbates the problem.

In C++ Toolkit the README.txt does indeed say that MFC and ATL
libraries are not included. Ok. ...That's why, when I thought I found
them somewhere else I thoiught they were complete, since the
description said "everything you need to run..."

I just thought I had missed picking them up somewhere.

> Before you go, answer me 2 questions
>
> 1) If your position on missing header locations is so reasonable, how is it
> I can find no one else using Google Groups that has ever raised this as a
> question before? And I have looked.

Multiple choice:
a) People afraid to run a gauntlet of ridicule?
b) Robert's brain is not configured like a Programmer's brain.
c) Not a clue
d) All of these

> 2) And if the missing header locations is so reasonable, how is it I find
> not one auxilary web site that rushes to cover Microsofts "glaring omission"
> over the location of atlstr.h? Feel free to point them all out (or even
> one).

I can't find any, but then again we've already established I can't find
anything. :)

- Robert -

.

Relevant Pages

  • Re: Imagination
    ... I know of no reason I need to adjust my post to the level ... To limit spam harvesting it is not in the posting header. ... post exact recipes. ... But there is a real issue--- Diabetes has damaged my hands ...
    (alt.support.diabetes)
  • Re: Rejecting null sender from my clients
    ... As long as you put your real address in the From: header, ... The reason you'd want to use is if you want to avoid a bounce in ... correct DSN. ... blanket ban on as an envelope sender. ...
    (comp.mail.sendmail)
  • Re: One to One - Multilple tables for large field qty
    ... If I add the third one-to-one, the primary key ... If you were advised to normalize your data, there's a reason. ... On the header table there is a form ID (primary ... joining the same FormID. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Link Merge Fields in Header and Footer
    ... Is there some reason you can't use a CreateDate field? ... Word MVP FAQ site: http://word.mvps.org ... > have liked to tuck the ASK field away in the header, ... >> the header and the footer cannot talk to each other. ...
    (microsoft.public.word.docmanagement)
Quantcast