Easy to use non-blocking timing for periodic-delayed code-execution

Projects Tutorials
21

That's the point. If the user declared the variable himself he knows it.
If it is a demo-code he hasn't written himself and this user is a very very beginner
showing both versions and explaining it will teach him this as a side-effect.

And again: as an expert it is a peace of cake to understand what

if (itsRaining == true) {
  // getWet();
}

means

22

well

Yes you would understand the intent but "as an expert" it's quite shocking that anyone would recommend that to any wannabe developer.

any one reading English would fully get

if (itIsRaining) { // is it raining ?

because that's how you speak.

23

But it deviates from the previous learned pattern where an explicit compairing must be made

if (rainPulses >=  100) {
  pullInTheAwning();
}
24

not really, it is also natural language, it's common to compare stuff when you speak

if the wind speed is more than 80Km/h then don't go sailing

if you name your variables appropriately then the code is easy to read

if (windSpeedKmh >= 80) {
  // ...
}

Anyone (besides politics) get what a truth value or a comparison is.
I've been working with kids or teens (and older people) and it has never been an issue

25

Not according to the C++ Core Guidelines.

1 Like
26

I consider it a "win" if some user can even be shown that boolean variables and values explicitly exist, have standard names, and can substitute for expressions. Many beginners don't even know that. Let's be honest, C/C++ is not the ideal beginner language because of such features (which are welcomed by experienced programmers).

Once they understand that, choices like the redundant use of == with boolean variables, should be easier to understand and use or not use.

We educators face the problem that many aspects of understanding are co-dependant, demand a parallel learning. So it's difficult to demonstrate specific aspects of a feature, without involving other features which also need to be demonstrated.

Because of this, I think that a demo code that is designed to explicate a certain feature, should have some latitude and flexibility in what other features are employed.

It is not possible to teach everything in one lesson.

27

The == however makes it clear with what type of variable one is dealing with. Personally I'm always using == and !=; but except for some 6 months (4 hours/week) courses in 6809 assembly and Pascal, I have no formal education in programming.

28

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.