C++ needs undefined behavior, but maybe less
-
think-cell[^]:
The behavior of a C++ program is defined by the C++ standard. However, it does not describe the behavior to the full extent and leaves some of it up in the air: the implementation-defined, unspecified, and undefined behavior.
I thought that was C++'s middle name?
-
think-cell[^]:
The behavior of a C++ program is defined by the C++ standard. However, it does not describe the behavior to the full extent and leaves some of it up in the air: the implementation-defined, unspecified, and undefined behavior.
I thought that was C++'s middle name?
Kent Sharkey wrote:
and leaves some of it up in the air: the implementation-defined, unspecified, and undefined behavior.
Not to mention the undefined errors :rolleyes: :laugh:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Kent Sharkey wrote:
and leaves some of it up in the air: the implementation-defined, unspecified, and undefined behavior.
Not to mention the undefined errors :rolleyes: :laugh:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
In fairness, if the C++ Standard specified the form of every possible error in a program, it would be at least twice as long as it already is.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
In fairness, if the C++ Standard specified the form of every possible error in a program, it would be at least twice as long as it already is.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
In the time I was programming industrial lines with PLC and Robots I always said: - Automatic sequences are the easy part. The difficult one is the home run / reset run, as the "initial" position for it will be after manual mode (a.k.a. wherever the user stops with or without thinking about it) or an error.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.