Re: Peter_Carlson asked for a project-specific " includes " path.
Jeff???Relf wrote:
Peter_Carlson asked for a project-specific " includes " path,
not a solution-specific one, much less IDE-specific.
Suppose someone links to a .CPP file... which SDK was he using ?
Suppose you've downloaded multiple SDKs,
which one do you want with which projects ?
e.g., from " www.Cotse.NET/users/jeffrelf/Games.CPP ":
#define DD_Path( __X ) Quote_It( \
C:\\Program Files\\Microsoft DirectX SDK (December 2005)\\__X )
#include DD_Path( Include\\DDraw.H )
#pragma comment( lib , DD_Path( Lib\\x86\\DDraw.LIB ) )
#pragma comment( lib , DD_Path( Lib\\x86\\DXguid.LIB ) )
#include DD_Path( Include\\DInput.H )
#pragma comment( lib , DD_Path( Lib\\x86\\DInput8.LIB ) )
#include DD_Path( Include\\Dxerr8.H )
#pragma comment( lib , DD_Path( Lib\\x86\\Dxerr8.LIB ) )
I'm glad you don't like the way I change titles, David_Wilkinson,
because I don't like the way you fail to make the title relevent
to the body of the post. This is called " cascading ":
> >>> >
> >>> > >>
> >>> > >> >
> >>> > >> > >>
> >>> > >> > >> >>>
> >>> > >> > >>
> >>> > >>
> >>>
Cascaders are several notches below those who are
either too lazy to too ignorant to post relevent titles,
as users " SHOULD " [ sic ] according to RFC 1036.
Do you also slur your speach when talking ? I have to wonder.
I expect this from Google Groups newbies,
not from a " Visual C++ MVP ".
From " www.FAQs.ORG/rfcs/rfc1036.html
" 2.1.4. Subject
The " Subject " line ( formerly " Title " )
tells what the message is about.
It SHOULD be suggestive enough of
the contents of the message to enable a reader
to make a decision whether to read the message
based on the subject alone. "
From " www.Usenet-Fr.NET/fr-chartes/son-of-rfc1036.2.html
" If the poster determines that
the topic of the followup differs significantly
from what is described in the subject,
a new, more descriptive, subject SHOULD be substituted... ".
Jeff:
Maybe your method works for you, but for me having code that can be
moved between different machines, and between different versions of the
compiler, is more important than having different SDK's for different
projects.
As to changing the subject line, it would seem from your recent posts
that you do this routinely, which is certainly not the usenet norm.
Maybe there might be exceptions in very long threads, but for me, either
a response is relevant (keep the title) or it isn't (start a new
thread). In this case, your response to Peter Carlson was hardly
relevant, because you considered external SDK paths rather than paths to
files within the project. I read these groups several times a day, and
when I see an unread response post, I look at the subject and say to
myself "Ah yes, that is the thread about ...". Constant changing of the
subject line breaks that association.
Just my opinions...
--
David Wilkinson
Visual C++ MVP