Convert resource to object in Sysvshm extension

[kocsismate]

No description provided.

[cmb69]

I just noticed that this overlaps with PR #3235.

[kocsismate]

@cmb69 Thanks for the heads up! Unfortunately, I didn't notice this before. However, I think Michał's PR is quite much outdated.

Though, should we get inspiration from his work, and use SysvSharedMemoryBlock (or SysvSharedMemorySegment) instead of SysvSharedMemory?

[brzuchal]

@cmb69 my PR is way outdated. AFAIR it took me a while to figure out proper naming of classes and functions so feel free to reuse them.

[brzuchal]

I didn't take a deserved look to the patch to agree with closing my outdated PR enough. What you propose here is just a replacement for a resource and delivers an object with no behaviour - IMO that doesn't make sense to bring a class with no behaviour if we can! most of read-write functions could be added to the OOP API on introduced class.

[kocsismate]

didn't take a deserved look to the patch to agree with closing my outdated PR enough.

Then sorry for the premature close, and feel free to reopen it if you desire to.

I hope my previous reply (#3235 (comment)) clears your doubts. I think it makes sense to separate these changes. Especially, because the migration by using an "opaque" object didn't need any RFC (or at least comments of a wider audience), while a new API does.

[brzuchal]

@kocsismate no worries. I'll take advantage of proposing similar API on a fresh PR soon.