On 5/24/2013 12:00 PM, Warp wrote:
> Orchid Win7 v1 <voi### [at] devnull> wrote:
>> This would be acceptable if VC offered some how to find out WHAT
>> TEMPLATE it was attempting to expand when the error occurred. But no, it
>> just shows you the source code for the STL (or Boost or whatever) and
>> points at the line on which the problem was actually detected. There
>> seems to be no way that I can discover what line of which file resulting
>> in this template being invoked in the first place - and THAT is surely
>> where the problem is, not in STL itself.
>
> All compilers I know if will give you the full chain of calls that
> ended up in the erroneous line. (And usually looking at the first error
> message that refers to your code will immediately reveal the problem.)
>
> I would be quite surprised if VC didn't do this.

The version of VS C++ I use at work does not give a reference chain for 
any error.  In a number of cases I am unable to discern what caused the 
cited file to be invoked.

Regards,
John

Post a reply to this message