Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c++ > #67052

Re: how/why it is written ... int &numberRef; vs int& numberRef;

Show all headers | View raw

Öö Tiib <ootiib@hot.ee> writes:

> On Tuesday, 16 July 2019 01:03:53 UTC+3, Ben Bacarisse  wrote:
>> Juha Nieminen <nospam@thanks.invalid> writes:
>> 
>> 
>> > And yes, this is valid C (and C++):
>> >
>> >   int *function1(), *function2(), function3();
>> >
>> > even though it's quite rarely used. (I bet most C/C++ programmers
>> > weren't aware of that.)
>> 
>> Don't people learn the syntax of the languages they use anymore?  (I'm
>> joking, of course they don't, but C and C++ were designed in era when
>> they did.)
>
> It takes years to learn nuances of all C++ syntax.

Yup.  I was talking about the broad-brush syntax.  I don't know the
details even after decades, but it's a fundamental part of both C and
C++'s syntax that "decoration" around the name alters the name's
relation to the base type:

  int i, function(), array[], *pointer;

> That syntax goes
> back to times when count of punch cards used was concern on one
> hand but it also receives substantial extensions after every few
> years on the other hand.

It goes back to those days, but I would be surprised if that was ever a
concern.  C was created for Unix, and Unix installations rarely used
punched cards.

<cut>
-- 
Ben.

Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

how/why it is written ... int &numberRef; vs  int& numberRef; G G <gdotone@gmail.com> - 2019-07-12 15:12 -0700
  Re: how/why it is written ... int &numberRef; vs int& numberRef; Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2019-07-12 23:16 +0100
    Re: how/why it is written ... int &numberRef; vs int& numberRef; G G <gdotone@gmail.com> - 2019-07-12 15:21 -0700
  Re: how/why it is written ... int &numberRef; vs int& numberRef; James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-07-12 18:55 -0400
  Re: how/why it is written ... int &numberRef; vs  int& numberRef; Öö Tiib <ootiib@hot.ee> - 2019-07-12 18:55 -0700
  Re: how/why it is written ... int &numberRef; vs int& numberRef; Szyk Cech <szykcech@spoko.pl> - 2019-07-13 05:33 +0200
  Re: how/why it is written ... int &numberRef; vs  int& numberRef; Juha Nieminen <nospam@thanks.invalid> - 2019-07-15 20:33 +0000
    Re: how/why it is written ... int &numberRef; vs  int& numberRef; Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-07-15 23:03 +0100
      Re: how/why it is written ... int &numberRef; vs  int& numberRef; Öö Tiib <ootiib@hot.ee> - 2019-07-15 18:31 -0700
        Re: how/why it is written ... int &numberRef; vs  int& numberRef; Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-07-16 03:04 +0100
          Re: how/why it is written ... int &numberRef; vs  int& numberRef; Öö Tiib <ootiib@hot.ee> - 2019-07-16 05:59 -0700
        Re: how/why it is written ... int &numberRef; vs int& numberRef; "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2019-07-16 05:48 +0200
          Re: how/why it is written ... int &numberRef; vs int& numberRef; David Brown <david.brown@hesbynett.no> - 2019-07-16 08:47 +0200
            Re: how/why it is written ... int &numberRef; vs int& numberRef; "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2019-07-16 11:52 +0200
              Re: how/why it is written ... int &numberRef; vs int& numberRef; David Brown <david.brown@hesbynett.no> - 2019-07-16 12:45 +0200
                Re: how/why it is written ... int &numberRef; vs int& numberRef; "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2019-07-17 07:06 +0200
                Re: how/why it is written ... int &numberRef; vs int& numberRef; David Brown <david.brown@hesbynett.no> - 2019-07-17 08:17 +0200
                Re: how/why it is written ... int &numberRef; vs int& numberRef; scott@slp53.sl.home (Scott Lurndal) - 2019-07-17 14:03 +0000
          Re: how/why it is written ... int &numberRef; vs int& numberRef; Öö Tiib <ootiib@hot.ee> - 2019-07-16 07:36 -0700
          Re: how/why it is written ... int &numberRef; vs int& numberRef; Juha Nieminen <nospam@thanks.invalid> - 2019-07-17 07:25 +0000
      Re: how/why it is written ... int &numberRef; vs  int& numberRef; Juha Nieminen <nospam@thanks.invalid> - 2019-07-17 07:24 +0000
        Re: how/why it is written ... int &numberRef; vs  int& numberRef; Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-07-17 12:53 +0100

csiph-web