• "Matthew Wilson" <matthew hat.stlsoft.dot.org> Dec 06 2007
• "Cláudio Albuquerque" <cláudio nowhere.com> Dec 07 2007
• "Matthew Wilson" <matthew hat.stlsoft.dot.org> Dec 07 2007

"Matthew Wilson" <matthew hat.stlsoft.dot.org> writes:

In order to accomodate one user's feature request, I need to know whether
the merged MFC/ATL headers, in particular atlstr.h, are bound to a
particular VC++ compiler version. Alternatively, whether they're bound to a
particular MFC version.

My working hypothesis is that if _MFC_VER >= 0x0700, then I can #include
atlstr.h with confidence

If anyone can shed any light on this, that'd be cool.

Thanks

Matt

"Cláudio Albuquerque" <cláudio nowhere.com> writes:

Hi Mathew,

Thanks for consider my request, that helps allot when compiling ATL 
projects.
To the best of my knowloge the atlstr.h / cstringt.h files where deployed 
with Visual Studio 2000 (aka 7.0)
So I have to agree with you that _MFC_VER will do the trick or you could go 
with compiler version.

Adicionally I attach files, are a request for you to consider a couple of 
"improvements" to stlsoft that I have been replicating them since the
day I made them, and cursing the bad idea ever since :-) .

static_string - line  346 and others - added method   void pop_back();

mfcstl - line 144 - changed include from afx.h to atlstr.h. You can also use 
cstringt.h (MFC dependent) atlstr.h (MFC independent)

Kind Regards
Cláudio Albuquerque



"Matthew Wilson" <matthew hat.stlsoft.dot.org> wrote in message 
news:fj9jul$1enj$1 digitalmars.com...
 In order to accomodate one user's feature request, I need to know whether
 the merged MFC/ATL headers, in particular atlstr.h, are bound to a
 particular VC++ compiler version. Alternatively, whether they're bound to 
 a
 particular MFC version.

 My working hypothesis is that if _MFC_VER >= 0x0700, then I can #include
 atlstr.h with confidence

 If anyone can shed any light on this, that'd be cool.

 Thanks

 Matt


 

"Matthew Wilson" <matthew hat.stlsoft.dot.org> writes:

Cláudio

My apologies

I've already incorporated these changes into the 1.9 trunk, just not yet had
time to release. I should have emailed you this to save you the effort. ;-/

Should be out this w/e, or early next week.

Matt

"Cláudio Albuquerque" <cláudio nowhere.com> wrote in message
news:fjcp5d$186k$1 digitalmars.com...
 Hi Mathew,

 Thanks for consider my request, that helps allot when compiling ATL
 projects.
 To the best of my knowloge the atlstr.h / cstringt.h files where deployed
 with Visual Studio 2000 (aka 7.0)
 So I have to agree with you that _MFC_VER will do the trick or you could


 with compiler version.

 Adicionally I attach files, are a request for you to consider a couple of
 "improvements" to stlsoft that I have been replicating them since the
 day I made them, and cursing the bad idea ever since :-) .

 static_string - line  346 and others - added method   void pop_back();

 mfcstl - line 144 - changed include from afx.h to atlstr.h. You can also


 cstringt.h (MFC dependent) atlstr.h (MFC independent)

 Kind Regards
 Cláudio Albuquerque



 "Matthew Wilson" <matthew hat.stlsoft.dot.org> wrote in message
 news:fj9jul$1enj$1 digitalmars.com...
 In order to accomodate one user's feature request, I need to know




 the merged MFC/ATL headers, in particular atlstr.h, are bound to a
 particular VC++ compiler version. Alternatively, whether they're bound




 a
 particular MFC version.

 My working hypothesis is that if _MFC_VER >= 0x0700, then I can #include
 atlstr.h with confidence

 If anyone can shed any light on this, that'd be cool.

 Thanks

 Matt