RE: why doesn't vpath %.c subdir// work?

[Mark Galeck (CW)]

>No, that's not obvious at all.  I've seen plenty of questions that
were asked out of pure curiosity.

Fine, have it your way.  

>  If there's another way to solve
your problem that doesn't involve using double-slashes in vpaths are
you *really* going to ignore it because you've decided that the only
acceptable solution is one that uses double-slashes?

Right, there is another solution, but it involves more markers, like I said, I 
am now using .\.\.\ because I can't use \\ (or //).  But I don't like it 
because it creates more clutter on already busy compile lines.  So I would 
prefer if // worked.  


> (just the output of 'make'?  auto-dependency files too?)
to determine when and where the paths were used in their tagged forms?
 Tagging would be done inside the source files (the #include lines,
presumably) only?  Or also in the -I options passed to the compiler?


Thank you Philip, you are very graciously trying to solve my problem.  It is 
very nice of you, no sarcasm, but that is not what I want.  I apologize if it 
sounds arrogant.  I come to this group usually because of some small sticky 
point, which I boil down as much as possible;  the big problem which contains 
several such sticky points, I will solve myself (actually already have).  I 
would not want to busy anybody with thinking about my big problems.  

Mark