14 May
2020
14 May
'20
3:02 a.m.
On May 13, 2020, at 7:00 PM,Dave Horsfall
<dave(a)horsfall.org> wrote:
I never could figure out why Stroustrup implemented that "feature"; let's
see, this operator usually means this, except when you use it in that
situation in which case it means something else. Now, try debugging that.
C continues the tradition begun by Fortran and Algol 60 of overloading the arithmetic
operators on the various numeric types. C++ allows new types to be defined; when a new
type obeys the generally understood properties of a built-in type, it makes sense to use
the same operator (or function) for the corresponding operation on the new type (e.g.,
addition on complex numbers, arbitrary-precision integers and rationals, polynomials, or
matrices).
14 May
14 May
5:08 p.m.
New subject: v7 K&R C
On 5/13/20, Paul McJones <paul(a)mcjones.org> wrote:
C continues the tradition begun by Fortran and Algol 60 of overloading the
arithmetic operators on the various numeric types. C++ allows new types to
be defined; when a new type obeys the generally understood properties of a
built-in type, it makes sense to use the same operator (or function) for the
corresponding operation on the new type (e.g., addition on complex numbers,
arbitrary-precision integers and rationals, polynomials, or matrices).
I agree; that makes sense. But I don't like things such as << and >>
in I/O-related classes.
-Paul W.
1455
days inactive
1455
days old
2 comments
3 participants
participants (3)
-
Clem Cole -
Paul McJones -
Paul Winalski