COLLECTED BY

Organization: Archive Team

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

Collection: Archive Team: The Github Hitrub

This collection is a set of Github repository archives from two major sets: A panic grab upon the acquisition by Microsoft, and a larger, ongoing set of Pretty Much Everything.

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20210128170921/https://github.com/php/php-src/pull/1699

php / php-src

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for a digit separator #1699

Closed

tpunt wants to merge 3 commits into php:master from tpunt:number-format-separator

Contributor

tpunt commented Dec 28, 2015

RFC: https://wiki.php.net/rfc/number_format_separator

nikic reviewed

View changes

Zend/zend_language_scanner.l Outdated

  
        	int len = yyleng - 2;

        	char *end;

        	char *end, *bin = strndup(yytext + 2, len);

nikic Dec 28, 2015
Member

Where is this freed again? Also, should use estrndup. It would also be good point to avoid copying the string if it does not have digit separators.

smalyshev added the RFC label

tpunt force-pushed the tpunt:number-format-separator branch from b03c616 to 53aa68d

tpunt closed this

tpunt force-pushed the tpunt:number-format-separator branch from af5604a to 65e456f

tpunt added 2 commits


          Add support for a digit separator in PHP


          Add tests for digit separator

27d2159

tpunt reopened this

tpunt force-pushed the tpunt:number-format-separator branch 4 times, most recently from 40a6d87 to 61f5aab


          Fix segfaults in implementation

tpunt force-pushed the tpunt:number-format-separator branch from 9f820c6 to 3580086

tpunt closed this

tpunt reopened this

Contributor Author

tpunt commented Jan 25, 2016

This feature has been rejected with a final vote of 20:18 (yes:no).

tpunt closed this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment