Reply to thread

Message

A general remark that causes issues and leads to somewhat (and long) trial-and-error debugging sessions:
Distinguishing between compiler and linking errors; knowing what they are, what causes them and how to resolve them.
Seeing a compiler as a series of steps to translate Hello.cpp to Hello.exe
Really reading error messages and go to step 1.
When debugging, reduce the scope (e.g. 1st test w/o ExcelDriver). Solving 2 problems simultaneously is not a good idea.
Take an analytical approach.
In one of my early modules I explain the compilation process.
[MEDIA=youtube]IhC7sdYe-Jg[/MEDIA]

[QUOTE="Daniel Duffy, post: 239749, member: 607"] A general remark that causes issues and leads to somewhat (and long) trial-and-error debugging sessions: [LIST=1] [*]Distinguishing between compiler and linking errors; knowing what they are, what causes them and how to resolve them. [*]Seeing a compiler as a series of steps to translate Hello.cpp to Hello.exe [*]Really reading error messages and go to step 1. [*]When debugging, reduce the scope (e.g. 1st test w/o ExcelDriver). Solving 2 problems simultaneously is not a good idea. [*]Take an analytical approach. [/LIST] In one of my early modules I explain the [I]compilation process.[/I] [MEDIA=youtube]IhC7sdYe-Jg[/MEDIA] [/QUOTE]

Verification