Conference decwet::visual

454.0. "CW fails to parse AFX_DATA_MAP on open file" by PAMSRC::XHOST::SJZ (Rocking the Messaging Desktop !) Fri Jan 31 1997 13:13

    
    We have a set of files that was once a MSVC 2.0 project.
    What we have now is a bastardized makefile (hand edited)
    and the source files.
    
    When we bring it into  MSDEV  it  says  something  "Duh,
    this ain't one of  my  makefiles" (which  we  expected).
    We press the "Yes, please wrap my makefile with one of
    yours - thank you." button and we are in business.
    
    Then we starting inserting the source files into the
    project - Hakuna Matata.   Then we bring up the Class
    Wizard which says "I can't find the .CLW file",  and we
    press the "add all files to build me a new one" button.
    
    Then in the Class Wizard I look at the message maps for
    my various classes (which are generally a bunch of
    CFormView's with data exchange).
    
    The problem is,  if I have one of the .cpp files open for
    one of my CFormView classes,  then the Class Wizard fails
    to reconstruct that class.  Specifically it barfs when it
    tries to parse the DoDataExchange  AFX_DATA_MAP.  For in-
    stance we get
    
    'Parsing error: Expected end-of-line.
    Input Line: "DDX_Text(pDX, IDC_RECEIVER_STATE, m_sReceiverState);
    nected;"'
    
    that last (third line) is actually the end of another
    line in the AFX_DATA_MAP (it varies though (as in random
    corruption type stuff). If we make sure all of the files
    are closed before recreating the .CLW file it works just
    fine.   However,  once I open up one of the  .cpp  files
    the Class Wizard once again complains about the  "Expect-
    ed end of line." followed by what looks like a valid
    line in the data map and then some trailing garbage.
    Closing the file and then reseleting the class in the
    Class Wizard make everything okay.
    
    This happens on Intel using V4.2, and on the Alpha using
    V4.1.  It does not happen on the Alpha using V4.0.  That
    is we start with the exact same files and do the exact
    same steps and it just works.  If you cannot reproduce
    this and you want a copy of our application files just
    say so.
    
    _sjz.

    have you checked to see if this is fixed in the V5.0 kit?
    

    
    will give it a try.
    _sjz.