Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119333
Message-ID: <A00D1DBC-01CE-469A-B722-C3BFF781B99C@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_7B9D108A-85B3-48CE-87A0-31C469EACBB6"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\))
Date: Wed, 18 Jan 2023 21:09:06 +0100
In-Reply-To: <CABigaAXz+7g2moCjxRzpx_SZ=PdzzOvywmEw=0TKJmjXuSQEDg@mail.gmail.com>
Cc: Kamil Tekiela <tekiela246@gmail.com>,
 PHP Developers Mailing List <internals@lists.php.net>
To: autaut03@gmail.com
References: <CAFPFaMLtOAkRzTsqfdhvkZZ17JpUBg_WSQBpgVU6+xg-mLt2zA@mail.gmail.com>
 <alpine.DEB.2.23.453.2301181523100.23089@singlemalt.home.derickrethans.nl>
 <04288995-54CE-41A4-BFFD-A7CF72F16D3F@gmail.com>
 <CAGBsUreK46-tg6XZmykPJx2ap-fnKbLs0=NsjwTntxbbFK2E-Q@mail.gmail.com>
 <F0C029A9-76AF-459F-87AC-433770CE745C@gmail.com>
 <CABigaAXz+7g2moCjxRzpx_SZ=PdzzOvywmEw=0TKJmjXuSQEDg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Path to Saner Increment/Decrement operators
From: claude.pache@gmail.com (Claude Pache)

--Apple-Mail=_7B9D108A-85B3-48CE-87A0-31C469EACBB6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> Le 18 janv. 2023 =C3=A0 19:33, Alex Wells <autaut03@gmail.com> a =
=C3=A9crit :
>=20
> Classes and methods is the expected way of implementing standard =
library in an OO language. New APIs (such as the new Random api) use OO =
instead of functions and it makes more sense to use OO in this case too: =
there's likely a place for other methods too, like toBase(int =
$otherBase) etc. It would also be possible to use overloaded operators =
if needed.

Fortunately, PHP is not (yet) a language where every problem requires =
the use and manipulation of objects implementing a generalised and =
unified solution. I guess that the OO way of writing:

```php
function next_alpha_id(): string {
    static $x =3D 'zz';
    return ++$x;
}

function next_num_id(): int {
    static $x =3D 0;
    return ++$x;
}

$my_id =3D next_alpha_id();
$my_other_id =3D next_num_id();
```

would resemble to the following, except that `mixed` should be replaced =
by the use of generics. For brevity, I left the mandatory interfaces as =
exercise to the reader.

```php
class IdGenerator {
   =20
    protected mixed $current;

    public function __construct(
        protected readonly IdGeneratorType $type
      , protected readonly IdGeneratorDirection $direction
      , mixed $start
    ) {
        $this->current =3D $start;
    }
   =20
    public function next(): mixed {
        // implementation...
    }
   =20
}

enum IdGeneratorType {
    case alphabetic;
    case numeric;
}

enum IdGeneratorDirection {
    case positive;
    case negative;
}



final class StandardGlobalAlphabeticIdGenerator {
   =20
    private static IdGenerator $id_generator;

    public static function get(): IdGenerator {
        return self::$id_generator ?? new IdGenerator(
            type: IdGeneratorType::alphabetic
          , direction: IdGeneratorDirection::positive
          , start: 'aaa'
        );
    }

}

final class StandardGlobalNumericIdGenerator {
   =20
    private static IdGenerator $id_generator;

    public static function get(): IdGenerator {
        return self::$id_generator ?? new IdGenerator(
            type: IdGeneratorType::numeric
          , direction: IdGeneratorDirection::positive
          , start: 1
        );
    }

}


$my_id =3D StandardGlobalAlphabeticIdGenerator::get()->next();
$my_other_id =3D StandardGlobalNumericIdGenerator::get()->next();
```

=E2=80=94Claude


--Apple-Mail=_7B9D108A-85B3-48CE-87A0-31C469EACBB6--