DotNet Visual C: ICE on VC7.1 when destructor is defined but not delcared in class

• jonathanturkanis / 206 / Wed, 27 Jan 2010 07:46:00 GMT / Comments (3)
• Hi,
  This morning I got an internal error on VC7.1 which was apparently
  caused by failing to delete the definition of a destructor after
  removing the declaration from the class body.

  Is this a known issue, or should I (if I have time) attempt to find
  a short example which illustrates the error?

  Jonathan
• Keywords:

  ice, vc7.1, destructor, defined, delcared, class, dotnet, visual, visual c, .net

• http://dotnet.itags.org/visual-c/71194/«« Last Thread - Next Thread »»

• 1. > This morning I got an internal error on VC7.1 which was apparently
     >caused by failing to delete the definition of a destructor after
     >removing the declaration from the class body.
     > Is this a known issue, or should I (if I have time) attempt to find
     >a short example which illustrates the error?

     Jonathan,

     An example will certainly enable someone to say whether it's resolved
     or not, and to submit a bug report if its not.

     Dave

     davidlowndes | Mon, 31 Dec 2007 14:53:00 GMT |

  2. "David Lowndes" <davidl...example.invalid> wrote in message
     news:ms23701a2ogu5cts0sgc9fi5rd66oid4kt...4ax.com...
     > > This morning I got an internal error on VC7.1 which was
     apparently
     > >caused by failing to delete the definition of a destructor after
     > >removing the declaration from the class body.
     > > Is this a known issue, or should I (if I have time) attempt to
     find
     > >a short example which illustrates the error?
     > Jonathan,
     > An example will certainly enable someone to say whether it's
     resolved
     > or not, and to submit a bug report if its not.

     I know that an example would be best, but I was sort of hoping someone
     would recognize the problem from my brief description so I wouldn't
     have to try to produce a short example. ;-)

     If nobody recognizes a known problem along these lines, I'll try to
     produce an example when I get a chance.

     Thanks,
     Jonathan

     jonathanturkanis | Mon, 31 Dec 2007 14:54:00 GMT |

  3. >I know that an example would be best, but I was sort of hoping someone
     >would recognize the problem from my brief description so I wouldn't
     >have to try to produce a short example. ;-)

     I'm afraid I forget the specifics (if I ever knew) of these issues as
     soon as I've reported them, so I can't save you any time.

     Perhaps someone else with a better memory for these things can
     remember - but many of the MVPs are likely to be at the MS summit this
     week.

     Dave
     --
     MVP VC++ FAQ: http://www.mvps.org/vcfaq

     davidlowndes | Mon, 31 Dec 2007 14:56:00 GMT |