Where's the beef?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

AVee - 01 Sep 2005 16:29 GMT

I posted this question on 8-23, and await a "managed" response:

Is it possible to define a macro substitution in the C++ preprocessor so
that it will be replaced "as if" it were defined within the source code?

In other words, I would like the preprocessor to expand this:

#include "..\_MYPATH_\myfile.h"

to this:

#include "..\MySpecificPath\myfile.h"

without having to include this line of code in each file

#define _MYPATH_ MySpecificPath

The reason that this is so important to me is because our company has become
heavily invested in MFC, and certain capabilities (Class Wizard & Browser
features) essential to efficiently maintain large MFC projects have been
dropped in VS.NET - AND, once project files are converted to VS.NET, they are
no longer usable under previous development systems. Also, it is impossible
to turn off deprecated warning C4996 - making portability harder yet to
manage ... and suggested replacements for deprecated functions are not easily
linked into the older development system (VC6).

Since portability to VS.NET has proved to be extensive, we need to maintain
production source files under VC++ during the process. The only method that I
see is viable is by accommodating the compiler differences in compiler
dependent headers, and calling the appropriate header by means of a
predefined macro in the project.

So - in order to reliably port large amounts of (tested and reliable) code,
I need to be able to call in different header files depending on the version
of compiler that I am using - at least until Microsoft reintroduces MFC
maintenance features that were dropped. I am hoping NOT to have to introduce
gazillions of #ifdef's, only needing to remove them once porting is complete.

And by the way - it's my opinion that developers would be MORE inclined to
migrate to newer MS technologies (managed code) if MFC support were enhanced,
not diminished (so as to force our hand). On what basis can developers be
assured that their investment in the new technology will be preserved?

Anyway - when I purchased MSDN I was assured of 48 hour managed response.
It's been eight days now. Can someone answer my simple question? "Can macro
substitutions be made by the project's preprocessor or not?". If not - fine,
#ifdef's it is. If so, how?

- otherwise please suggest or point me to information on the "suggested"
method of maintaining large MFC projects while porting to emerging MS
development systems.

Reply to this Message

Mikhail Arkhipov (Microsoft) - 02 Sep 2005 03:45 GMT

On 9/1/05 8:29, in article
102E3388-8481-49AB-A779-1822EC518114@microsoft.com, "AVee"

> I posted this question on 8-23, and await a "managed" response:
>
[quoted text clipped - 47 lines]
> method of maintaining large MFC projects while porting to emerging MS
> development systems.

Don't get me wrong, please, but I don't think newsgroups is the place where
you can expect "managed" response :-). I don't think our PSS monitors them,
newsgroups are mostly for peer help and sometimes you can also meet some
Microsoft developers here, but it is really a community service :-). If you
want timed response, please contact PSS directly either my phone or e-mail.
I am not in a tech support, for example, I am actually a developer in the VS
HTML editor team and typing this response from home.

Anyway, back you your question. Since you use different versions of the
compiler I assume you are using external make files. In this case you can
change you code to simply

#include "myfile.h"

And specify location of the header files using -include compiler option. If
you prefer to have include statement unchanged, you can define MYPATH in the
compiler options using -DMYPATH=whatever. This way you don't have to specify
MYPATH in sources. Yet another way is to specify MYPATH in a single header
that you include in the beginning of all the file. This way you only have to
change a single file between different versions of the compiler.

Thanks
Mikhail Arkhipov (Microsoft)
-- This post is provided 'AS IS' with no warranties and confers no rights

Reply to this Message

- 03 Sep 2005 08:28 GMT

MA- [Thu, 01 Sep 2005 19:45:04 -0700]:

>Don't get me wrong, please, but I don't think newsgroups is the place where
>you can expect "managed" response :-). I don't think our PSS monitors them,
>newsgroups are mostly for peer help and sometimes you can also meet some

For four, or maybe five years, this is what has been going on:

MSDN Managed Newsgroups

To start using the Managed Newsgroup service, choose an available
newsgroup from the list of newsgroups below. You can select with your
Web browser or with a Network News Transfer Protocol (NNTP)-based
newsreader such as Microsoft Outlook Express.

For more information on configuring and reading newsgroups using a
newsreader, see Welcome to the MSDN Managed Newsgroups. Once you have
configured your NNTP newsreader, you can access the support newsgroups
listed below on this page via your NNTP newsreader client.

If you cannot find an appropriate newsgroup in the list below, please
contact us to let us know of other developer-focused newsgroups you'd
like to see added to the list of Managed Newsgroups.

There are about a hundred, maybe even two hundred,
microsoft.public.* NGs. Sure enough, this

microsoft.public.vsnet.ide

in the list

http://msdn.microsoft.com/subscriptions/managednewsgroups/list.aspx

However, I can see see from this, and have always
thought, it's not anything special, above or beyond
what one would get in any newsgroup (some get answers,
some don't).

Signature

40th Floor - Software @ http://40th.com/
iPlay : the ultimate audio player for mobiles
parametric eq, xfeed, reverb; all on a mobile

Reply to this Message

AVee - 15 Sep 2005 23:58 GMT

Naturally I greatly appreciate any technical help that I have and am
receiving, from Microsoft and others. Thank you.

Please consider these thoughts, however:

On the back of the retail box for my MSDN Professional Subscription, under
the Technical Support subtitle and listed together with the provision for
telephone support, it says, "MSDN Subscribers can post .NET product and
technology questions in more than 200 newsgroups and receive a response to
the post within two business days".

I believe that NOT providing a response within two business days is
tantamount to a advertising transportation passes for hourly bus service
along a route that the buses don't regularly run, under the auspices that
concerned motorists would be likely to pick up stranded travelers who have
the purchased pass within an hour or so. By listing two day response together
with the other paid features (that are not contingent on sources outside of
Microsoft) in the category of "MSDN Subscriptions Include", Microsoft
promised two day response. I thought I was paying for what was described, not
just a "better web log".

Being new to the service, I don't believe I could be expected to know what
was going on for the past four or five years - only what I read from the
advertisement on the most current MSDN retail box.

In the spirit of self improvement, I would hope that Microsoft would consult
with its staff to clarify the marketing promises it has made, change its
advertising as necessary (such as by saying "often receive response within
two days"), and make good on existing obligations.

Respectfully submitted.

> MA- [Thu, 01 Sep 2005 19:45:04 -0700]:
> >Don't get me wrong, please, but I don't think newsgroups is the place where
> >you can expect "managed" response :-). I don't think our PSS monitors them,
> >newsgroups are mostly for peer help and sometimes you can also meet some

...

> For four, or maybe five years, this is what has been going on:

...

> However, I can see see from this, and have always
> thought, it's not anything special, above or beyond
> what one would get in any newsgroup (some get answers,
> some don't).

Reply to this Message

Mikhail Arkhipov (Microsoft) - 18 Sep 2005 06:43 GMT

On 9/15/05 15:58, in article
AC42BF19-2858-4578-807F-6ED320A85D5E@microsoft.com, "AVee"

> Naturally I greatly appreciate any technical help that I have and am
> receiving, from Microsoft and others. Thank you.
[quoted text clipped - 43 lines]
>> what one would get in any newsgroup (some get answers,
>> some don't).

Interesting. Let me follow up internally on this. I honestly find
information on newsgroups somewhat confusing.

At http://msdn.microsoft.com/newsgroups/managed/ it indeed says
"A commitment to respond to your post within two business days"

However, at another page (click on the "Web based newsreader") it says

" Expectations of service
Microsoft's Role: Microsoft does not offer formal support for the
communities you'll find here. Instead, our role is to provide a platform for
people who want to take advantage of the global community of Microsoft
customers and product experts. Microsoft may monitor content to ensure the
accuracy of the information you'll find, but any information provided by
Microsoft staff is offered "AS IS" with no warranties, and no rights are
conferred. You assume all risk for your use"

There is an email address to complain to, listed at
http://msdn.microsoft.com/subscriptions/faq/default.aspx#support

"When can I expect a response to my managed newsgroup posting?
Microsoft guarantees a response (either from the community or by Microsoft)
with in two business days for qualifying Subscribers. If for some reason you
have not received a response within two business days, please contact MSDN
Managed Newsgroup Feedback ( ngmsdnfb@microsoft.com) for additional
assistance".

Try to send there an e-mail.

Thanks
Mikhail Arkhipov (Microsoft)
-- This post is provided 'AS IS' with no warranties and confers no rights

Reply to this Message

AVee - 30 Sep 2005 20:33 GMT

Dear Mikhail,

I will follow your suggestion and paste a portion of this thread to the
Email address you suggested.

I am hoping that my last message was received as I had intended, "in the
spirit of self improvement". As for the AS IS - everything in the software
world is "AS IS". Everyone expects that. What is not expected is the
necessity to sleuth out contradictory claims after the fact, being as it
were, on one page it says "this is what you are buying", but somewhere else
it says, "not exactly".

Thank you (personally) however, for your courteous response.

> On 9/15/05 15:58, in article
> AC42BF19-2858-4578-807F-6ED320A85D5E@microsoft.com, "AVee"
[quoted text clipped - 79 lines]
> Mikhail Arkhipov (Microsoft)
> -- This post is provided 'AS IS' with no warranties and confers no rights

Reply to this Message

Where's the beef?

Free Magazines