Skip to content

Wrap strings passed to libzip with zip_source_function_create()#21659

Merged
DanielEScherzer merged 1 commit intophp:masterfrom
tstarling:zip_source_function_create
Apr 10, 2026
Merged

Wrap strings passed to libzip with zip_source_function_create()#21659
DanielEScherzer merged 1 commit intophp:masterfrom
tstarling:zip_source_function_create

Conversation

@tstarling
Copy link
Copy Markdown
Contributor

Wrap strings passed to libzip with zip_source_function_create() instead of using zip_source_buffer_create(). This allows us to make the string writable, and simplifies memory management.

Split from #21497 as requested by @DanielEScherzer

Wrap strings passed to libzip with zip_source_function_create()
instead of using zip_source_buffer_create(). This allows us to make
the string writable, and simplifies memory management.
@tstarling tstarling force-pushed the zip_source_function_create branch from 8527d42 to bb06b21 Compare April 7, 2026 02:32
@Ayesh Ayesh removed the Category: CI label Apr 7, 2026
@DanielEScherzer
Copy link
Copy Markdown
Member

Everything looked correct on an implementation level yesterday - I'll come back to this with fresh eyes in a few days and confirm that nothing looks off, and then merge it

Copy link
Copy Markdown
Member

@DanielEScherzer DanielEScherzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me - question for Ben about adding license headers for new files between now and when #20904 merges, but otherwise makes sense

+----------------------------------------------------------------------+
| Copyright (c) The PHP Group |
+----------------------------------------------------------------------+
| This source file is subject to version 3.01 of the PHP license, |
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CC @ramsey - should this be added with the new license header for the new license? Or should it be added with the 3.01 license and be switched in your migration patch?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You may go ahead and use the new license header. Otherwise, if it’s merged as-is before I merge the license update PR, I’ll try to catch it.

@DanielEScherzer
Copy link
Copy Markdown
Member

@tstarling do you have merge rights? I see that you are an org member
If not I can merge this

@tstarling
Copy link
Copy Markdown
Contributor Author

@tstarling do you have merge rights? I see that you are an org member If not I can merge this

No, I only have merge rights in doc-en and doc-base.

@DanielEScherzer DanielEScherzer merged commit e0e2963 into php:master Apr 10, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants