Discussion Overview
The discussion centers on the differences and compatibility between Borland C++ and Microsoft Visual C++ (MSVC++), particularly in the context of programming for different platforms and applications. Participants explore the implications of using each compiler for various types of programming, including OS-independent and Windows applications.
Discussion Character
- Debate/contested
- Technical explanation
Main Points Raised
- One participant questions the compatibility of Borland C++ and MSVC++, asking if Microsoft introduced new syntax that would affect learning and transitioning between the two.
- Another participant suggests that compatibility depends on whether the code is compiler-independent or platform-independent, indicating that common code schemes should be identified.
- A participant mentions that MSVC++ is easier to work with for compatibility with third-party drivers, sharing a personal perspective from their experience in Silicon Valley.
- There is a clarification that MSVC++ and MSVC++.NET are distinct, with .NET being a runtime environment that uses different libraries. The participant notes that while syntactical differences may exist, library methods for Windows applications should be similar.
- It is mentioned that cross-platform development requires different libraries, and a suggestion is made to consider Java for developing cross-platform applications.
Areas of Agreement / Disagreement
Participants express differing views on the compatibility and usability of Borland C++ and MSVC++, with no consensus reached on the best approach for transitioning between the two or the implications for cross-platform development.
Contextual Notes
There are unresolved questions regarding specific syntactical differences and the extent to which library methods align across the two compilers. The discussion also highlights the potential for confusion between different versions of MSVC.