Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #140999
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: list of chars to introduce in future c |
| Date | 2019-02-14 13:49 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <878syiiip4.fsf@bsb.me.uk> (permalink) |
| References | <8b6a2c57-8c85-40ef-9c8a-0f77ab380586@googlegroups.com> <q41ads$s9n$1@dont-email.me> <q41opl$n17$1@news.albasani.net> <q439ri$cfs$1@dont-email.me> <q43ek5$bap$1@news.albasani.net> |
BGB <cr88192@hotmail.com> writes: <cut> > Clarification: One doesn't generally need new operators/... > Because it is usually possible to express most concepts sufficiently > via function calls, and if they invoke special logic in the compiler > (like an operator would), then using an operator is merely an > aesthetic convenience. There's are a couple of exceptions. Numerical operators in C are privileged in that they are usually defined for all arithmetic (and sometimes scalar) types. A max operator would be more convenient than that family of max functions. Also, with a binary operator X you would expect an assignment operator X= which is harder to arrange with a function. Keeping a running maximum could then be written mval[i] @= val; Some languages have syntax to let you turn functions into operators and operators into functions. Makes sense when they are only syntactically different, but in C that is not the case though one could imagine some hairy type matching rules that could make it work. <cut> -- Ben.
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-13 03:16 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-13 04:56 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-13 05:16 -0800
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-13 15:43 +0100
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-13 09:55 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-13 11:05 -0800
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-13 20:29 +0100
Re: list of chars to introduce in future c "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-02-13 20:33 +0100
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-13 12:08 -0800
Re: list of chars to introduce in future c John Bode <jfbode1029@gmail.com> - 2019-02-13 12:02 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-13 12:16 -0800
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 09:34 +0100
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-14 02:04 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-14 02:08 -0800
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 11:28 +0100
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-14 02:38 -0800
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 14:54 +0100
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-14 06:39 -0800
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 16:26 +0100
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-14 02:49 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-14 02:59 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-14 03:10 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-14 03:34 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 05:25 -0800
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-15 13:54 +0000
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 06:07 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 06:10 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 06:14 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 06:18 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 06:22 -0800
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-15 14:24 +0000
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 06:32 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 06:39 -0800
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-15 14:47 +0000
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 07:32 -0800
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-15 15:56 +0000
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 08:18 -0800
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-15 17:10 +0100
Re: list of chars to introduce in future c Keith Thompson <kst-u@mib.org> - 2019-02-14 12:20 -0800
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 21:32 +0100
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-14 13:52 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-14 02:31 -0800
Re: list of chars to introduce in future c BGB <cr88192@hotmail.com> - 2019-02-13 12:48 -0600
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 09:45 +0100
Re: list of chars to introduce in future c BGB <cr88192@hotmail.com> - 2019-02-14 04:06 -0600
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 11:39 +0100
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-14 14:34 +0000
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 16:31 +0100
Re: list of chars to introduce in future c Robert Wessel <robertwessel2@yahoo.com> - 2019-02-14 14:39 -0600
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-14 23:48 +0000
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-15 09:20 +0100
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-15 11:09 +0000
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-15 17:25 +0100
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-15 16:46 +0000
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-15 18:05 +0100
Re: list of chars to introduce in future c BGB <cr88192@hotmail.com> - 2019-02-17 14:45 -0600
Re: list of chars to introduce in future c James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-02-15 10:51 -0800
Re: list of chars to introduce in future c BGB <cr88192@hotmail.com> - 2019-02-14 13:59 -0600
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 21:36 +0100
Re: list of chars to introduce in future c BGB <cr88192@hotmail.com> - 2019-02-15 00:47 -0600
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-15 09:26 +0100
Re: list of chars to introduce in future c BGB <cr88192@hotmail.com> - 2019-02-15 14:15 -0600
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-16 01:36 +0000
Re: list of chars to introduce in future c BGB <cr88192@hotmail.com> - 2019-02-16 01:25 -0600
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-16 12:17 +0000
Re: list of chars to introduce in future c BGB <cr88192@hotmail.com> - 2019-02-16 15:08 -0600
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-16 23:10 +0000
Re: list of chars to introduce in future c BGB <cr88192@hotmail.com> - 2019-02-17 00:56 -0600
Re: list of chars to introduce in future c Bart <bc@freeuk.com> - 2019-02-17 17:30 +0000
Re: list of chars to introduce in future c BGB <cr88192@hotmail.com> - 2019-02-17 16:02 -0600
Re: list of chars to introduce in future c Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-02-14 13:49 +0000
Re: list of chars to introduce in future c Philipp Klaus Krause <pkk@spth.de> - 2019-02-14 09:08 +0100
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 09:56 +0100
Re: list of chars to introduce in future c Philipp Klaus Krause <pkk@spth.de> - 2019-02-14 11:06 +0100
Re: list of chars to introduce in future c David Brown <david.brown@hesbynett.no> - 2019-02-14 15:01 +0100
Re: list of chars to introduce in future c mark.bluemel@gmail.com - 2019-02-15 05:30 -0800
Re: list of chars to introduce in future c fir <profesor.fir@gmail.com> - 2019-02-15 05:42 -0800
Re: list of chars to introduce in future c Lynn McGuire <lynnmcguire5@gmail.com> - 2019-02-15 18:19 -0600
csiph-web