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


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

Re: Tricky!

From Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups comp.lang.c++
Subject Re: Tricky!
Date 2019-07-30 08:03 -0700
Organization A noiseless patient Spider
Message-ID <86imrj8szn.fsf@mailhub.linuxsc.com> (permalink)
References <qhmmgr$dih$1@news.albasani.net> <7995a414-14ec-47ae-8afc-9ebcc520e30d@googlegroups.com> <qhn54k$dk6$1@dont-email.me>

Show all headers | View raw


"Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> writes:

> On 29.07.2019 15:30,  <<D6 F6 [05b6]>>  Tiib wrote:
>
>> On Monday, 29 July 2019 14:49:58 UTC+3, Bonita Montero  wrote:
>>
>>> I need a class-function / method that returns a function-pointer
>>> to the same type of class-function.  How do I implement this?  I
>>> need this to have a kind of state-machine where each state-func-
>>> tion returns a pointer to the next state function.  I.e I would
>>> write:  "while( (fn = state->*fn()) != nullptr );".  I see no way
>>> to define the type of fn since it is recursive.
>>
>> Perhaps there are no way to make a function that return function
>> pointer of its own type.  However I do not understand the need
>> of it.
>
> I think she is inspired by (possibly someone else who is inspired
> by) an article by the Go language creator.
>
> As I recall his examples work nicely in Go, or assembly language, or
> a more dynamic language like Python, but have to be rewritten with
> some indirection for a language with strong static type checking
> like C++.

The problem here is not strong static type checking but the lack
of recursive types in C++.  A language can have recursive types
and also have strong static type checking.

> The reason for doing it that way, in languages where it's simple, is
> the textual simplicity of the source code.  Since it doesn't give
> that textual simplicity in C++, it's not a good way in C++.  It's
> doable, just not in any practical way.

That depends on what is meant by "practical".  It can be done
like this:

    #include <iostream>

    class State {
	using Nexter = ...;

      public:
	State(){}
	Nexter r0(){  return  &State::r1;  }
	Nexter r1(){  return  &State::r2;  }
	Nexter r2(){  return  &State::rn;  }
	Nexter rn(){  return  0;  }
    };

    void
    run_state_machine(){
	State *s = new State;

	for(  auto f = &State::r0;  f;  f = (s->*f)()  ){
	    ::std::cout << "Got one\n";
	}
    }

with a fairly short (five-ish lines) elaboration for the "...".
Personally I think this approach offers a fairly nice textual
simplicity, and is eminently practical.

If someone thinks five lines of overhead is too much, the "..."
can be made into a template, giving

        using Nexter = WrapMemberFunctionPointer< State >;

which provides an even nicer source text.

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


Thread

Tricky! Bonita Montero <Bonita.Montero@gmail.com> - 2019-07-29 13:49 +0200
  Re: Tricky! Öö Tiib <ootiib@hot.ee> - 2019-07-29 06:30 -0700
    Re: Tricky! "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2019-07-29 17:59 +0200
      Re: Tricky! Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-07-30 08:03 -0700
        Re: Tricky! "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-07-30 11:20 -0400
        Re: Tricky! "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2019-07-30 18:00 +0200
          Re: Tricky! Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-08-10 14:19 -0700
    Re: Tricky! Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-07-30 07:31 -0700
      Re: Tricky! Öö Tiib <ootiib@hot.ee> - 2019-07-30 09:22 -0700
        Re: Tricky! Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-08-10 14:45 -0700
          Re: Tricky! Öö Tiib <ootiib@hot.ee> - 2019-08-11 03:23 -0700
            Re: Tricky! Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-08-17 22:02 -0700
              Re: Tricky! Öö Tiib <ootiib@hot.ee> - 2019-08-17 23:53 -0700
                Re: Tricky! Tim Rentsch <tr.17687@z991.linuxsc.com> - 2019-08-18 05:22 -0700
  Re: Tricky! Sam <sam@email-scan.com> - 2019-07-29 20:51 -0400
  Re: Tricky! Sam <sam@email-scan.com> - 2019-07-29 20:52 -0400
  Re: Tricky! Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2019-07-30 13:58 +0100
    Re: Tricky! Bonita Montero <Bonita.Montero@gmail.com> - 2019-08-11 09:06 +0200

csiph-web