[WIP] Resourceless ext/sysvshm

[brzuchal]

This patch removes System V Shared Memory resource list type and provides new class SharedMemoryBlock which replaces resource type.

function shm_attach(int $key, int $size, int $mode) : SharedMemoryBlock
function shm_detach(SharedMemoryBlock $object) : bool
function shm_remove(SharedMemoryBlock $object) : void
function shm_put_var(SharedMemoryBlock $object, int $variable_key, $variable) : bool
function shm_has_var(SharedMemoryBlock $object, int $variable_key) : bool
function shm_get_var(SharedMemoryBlock $object, int $variable_key) 
function shm_remove_var(SharedMemoryBlock $object, int $variable_key) 

class SharedMemoryBlock {
    public function __construct(int $key, int $size, int $perm) 
    public function has(int $variable_key) : bool
    public function get(int $variable_key) 
    public function set(int $variable_key, $variable) : void
    public function remove(int $variable_key) : void
    public function free() : void
}

There will be RFC created for this patch later. This patch targets PHP 8.

[cmb69]

This might be closed in favor of PR #5499.

[kocsismate]

I'm closing this since the migration has just been done by the linked PR.

[brzuchal]

@kocsismate wait the linked PR only replaces reqource with a object without any OOP API, why is that? There's nothing special in object without behaviour?!

[kocsismate]

@brzuchal For now, my goal was only to get rid of a resource type with the least number of controversial changes. Migrations that were previously done (ext/enchant, ext/gd etc.) also did the same.

This doesn't mean that you can't propose an OO interface for sysvshm (or any other extensions), even for 8.0 :) But as you wrote in the description, that will need an RFC.