microsoft.public.vc.mfc - Microsoft Visual C
Here is a chunk of data float m_fStrtTime, m_fTRise, m_fT0 float m_fFO20, m_fFO2M, m_fFO2F float m_fFCO20, m_fFCO2M, m_fFCO2F float m_fFHeF, m_fFHeFF; float m_fR2Hel, m_fR2Acet, m_fR2DME, m_fR2CO float m_fIHel, m_fKHel, m_fIAcet, m_fKAcet, m_fIDME, m_fKDME, m_fICO, m_fKCO float m_fAcetCardOut, m_fAcetVtis float m_fAcetCardOut1, m_fAcetVtis1 float m_fAcetWagnCardOut float m_fDMECardOut, m_fDMEVtis float m_fDMECardOut1, m_fDMEVtis1 float m_fDMEWagnCardOut float m_fDCOr, m_fOCDCO, m_fOCDCOVA float xFGas0[RDI_END_POS+1] float xFGasLung[RDI_END_POS+1] float m_fFresp, m_fMeanVT, m_fTotVE float m_fEELV, m_fVRtot, m_fVDeff, m_fVAeff, m_fVR, m_fVENTeff float m_fOCVA, m_fOCVSD, m_fOCVSDI float m_fAcetCOfac float m_fDMECOfac double m_daSolnHe[RD_SOLNHE_PARAMS+1] unsigned m_uLungDataPos double m_dVO2, m_dVCO2 float m_fDNO, m_fKNO, m_fINO, m_fR2NO short __gxrcFinData And here is a little method to get the size of this set of data size_t sz=(char *)&__gxrcFinData-(char *)&m_fStrtTime; return sz In VC++ v6.0, this returns 408 bytes. In VC++.NET, it returns 412 bytes. In debugging some code that reads/writes a binary file with this data chunk in it, I can tell there is no problem up to the array m_daSolnHe. The array size is reported as 32 by both compileres. The size of the unsigned is 4 in both. I can NOT put my finger on the problem here -- does anyone know of a problem with fundamental data types in the more recent compiler version?
After taking 2 semesters of C++ at school, I've decided to get a compiler for my personal use when not at school, and one that can do Windows programming. I've pretty much come down to either vc++ .net 2003 standard or vc++ 6.0 pro. Basically, my main reservations about .net 2003 is that from what I've read it lacks optimizations, but 6.0 seems to be more dated, "less standardized", and the support will expire soon. Any opinions or help would be appreciated. Thanks in advance. -Aaron
"gene" < XXXX@XXXXX.COM > skrev i meddelandet news: XXXX@XXXXX.COM ... > Just an observation and a gripe - the fstream getline function behaves > differently in VC 6.0 and VC.NET 2003. In VC.NET, if you call getline with a > buffer size less than the length of the line in the file, the fail() bit gets > set and must be cleared before any further reads can be done. In VC 6.0, the > fail() bit does not get set and reading can continue. Any logical reason why > MS should change the way this function behaves between VC 6.0 and VC.NET > other than to cause incompatibility and headaches for developers? To comply with the C++ Standard? :-) Bo Persson