auroraeosrose

My bugs:

https://bugs.php.net/bug.php?id=54169 - I have a big patch for pdo_odbc in general

streams related issues: - 

https://bugs.php.net/bug.php?id=54156

https://bugs.php.net/bug.php?id=52811 - there are a ton more notification callback related issues - need MAJOR testing for that
https://bugs.php.net/bug.php?id=42387 - yes, this is also on my todo, could use most of the plumbing already in place for the notification callbacks

auroraeosrose

	

    class Entity
    {
      protected $model;
      
      protected function initModel() {
        $this->model = [];
      }
      

auroraeosrose

--- libmemcached-1.0.18/Makefile.am	2014-02-09 20:52:42.000000000 +0900
+++ libmemcached-1.0.18/Makefile.am	2014-02-16 23:42:32.265163300 +0900
@@ -2,6 +2,7 @@
 
 ACLOCAL_AMFLAGS= -I m4 -I libtest/m4
 AM_YFLAGS= -d
+AM_LDFLAGS = -no-undefined
 
 # includes append to these:
 SUFFIXES =

auroraeosrose

An initial dump of ideas for a php generator

1. use composer and symfony console tools for cli manipulation
2. pluggable architecture

components needed - configuration parsing scanning? (helper for generating definitions) templating

auroraeosrose

1. Streams: PHP streams have some major issues - notifications not finished, the horrid http layer (can we PLEASE use a library?), object/class integration, filters and the filter api make people cry, horrific error handling - noise for noise sake and no way to retrieve useful errors and warnings, no curl wrapper anymore, internal api for the implementation is sad
2. Extensions: some pecl <-> php swaps, all internal extensions MUST have ACTIVE maintainers or get punted, some OO apis for older extensions and killing some non useful (looking at you odbc) functionality, better test coverage of extensions
3. Enums: either in spl or in core, an enum object for C style enums (or enums as a zval type, either works for me) - this is highly difficult to implement in userland, in ext/core you can make it act like an int with Moar features
4. Unicode: a unicode string class - yes yes ugly in some ways, but could hold a wchar_t and char * cached of utf8, always act in utf8 when used a string in the majority of PHP cases

auroraeosrose

cairo.c
cairo_context.c
cairo_error.c
cairo_font.c
cairo_font_face.c
cairo_font_options.c
cairo_ft_font.c
cairo_image_surface.c
ext\cairo\cairo.c(618) : warning C4090: 'initializing' : different 'const' qualifiers
ext\cairo\cairo_font_options.c(77) : warning C4101: 'temp' : unreferenced local variable

auroraeosrose

1. Interfaces for streams wrappers (clean up apis) - primarily userland, small to no BC
2. Resources -> objects (engine storage and attachment) - primarily core, some BC issues
3. finish implementations for callbacks - primarily feature addition
4. async IO features (see: jpauli) - feature addition with core implications and some BC issues
5. curl:// stream wrapper - feature addition (functionality of --with-curl-wrappers but with curl:// as prefix)
6. filtering api - buckets hard to use, user_filter class is api possessed - userland and BC
7. factory registration for wrapper creation - feature addition
8. ability to plug into transports from php land instead of requiring C extensions

Streams Interfaces:

auroraeosrose

Index: config.w32
===================================================================
--- config.w32	(revision 0)
+++ config.w32	(revision 0)
@@ -0,0 +1,8 @@
+// $Id: config.w32 264053 2008-08-01 21:20:08Z pajoye $
+// vim:ft=javascript
+
+ARG_ENABLE("pcntl", "process control support", "no");
+

auroraeosrose

PHP7 is coming

And it's breaking all of our extensions
There are currently more changes to the internal apis than there are to things that users will see (and there are enough of those)

In fact not even all the extensions in php source proper are all the way PHP7'd - most of PECL and extensions hosted elsewhere haven't even started!  Heck half don't have maintainers!

Extensions are also notorious for poor api design, poor testing, and non-existent docs
But they're also powerful, useful, and fast and more people should use them
PHP7 is coming - fast - and we have a chance to "break" things and to get the community interested and involved

auroraeosrose

A quick snapshot of what is going on with the project - for the tl;dr see "what can I do?"

What is complete

1. A name- GoPHP7 is a project (not yet really started) to motivate people to migrate to PHP7 when it's released. This echoes the GoPHP5 project of the past
2. An irc channel - registered on freenode - owner auroraeosrose, ops lornajane, ircmaxell and joepferguson
3. A set of goals - see http://goo.gl/BJ3s8D

What is in process

1. Getting "adminy" stuff set up (lornajane is in charge) - This will include website, wikis, twitter, whatever, and other tools