Implemented 'finally' keywords for php

RFC: https://wiki.php.net/rfc/finally
FR: https://bugs.php.net/bug.php?id=32100
and I have got some improvment ideas(performance), will impleme

Implemented 'finally' keywords for php

RFC: https://wiki.php.net/rfc/finally
FR: https://bugs.php.net/bug.php?id=32100
and I have got some improvment ideas(performance), will implemented
later. thanks

show more ...

News for bug#40459

Merge branch 'pull-request/132'

* pull-request/132:
OK, bye bye JavaScript, let's just include credits before license
Nicer (JSLint-compliant!) credits reveal JavaScript
Re

Merge branch 'pull-request/132'

* pull-request/132:
OK, bye bye JavaScript, let's just include credits before license
Nicer (JSLint-compliant!) credits reveal JavaScript
Removed now-unnecessary expose_php checks for logo
Fixed small misalignment in prev commit
Removed Logo GUIDs and replaced with Data URIs and div hidden with JS

show more ...

add note for mcrypt_ecb

Reflect changes made in merge 99e48d3

typo

add NEWS/UPGRADING

Removed Logo GUIDs and replaced with Data URIs and div hidden with JS

- removed php_logo_guid()
- removed php_egg_logo_guid()
- removed php_real_logo_guid()
- removed zend_logo_g

Removed Logo GUIDs and replaced with Data URIs and div hidden with JS

- removed php_logo_guid()
- removed php_egg_logo_guid()
- removed php_real_logo_guid()
- removed zend_logo_guid()
- removed logo GUID handling
- removed logo GUIDs from source
- added logo data URIs instead for phpinfo()
- added credits to phpinfo() page, but hidden by default

show more ...

Add new function hash_pbkdf2() to UGRAPDING doc

Merge branch 'pull-request/112' into PHP-5.4

* pull-request/112:
Added in NEWS and UPGRADING for feature 55218
Adding in test for feature 55218
Implements feature 55218

Added in NEWS and UPGRADING for feature 55218

Update UPGRADING given 7596445

one more correction for COM upgrading notes

com ext upgrading infos

UPGRADING entry for boolval()

Updated UPGRADING for the changes in eb346ef

Merge branch 'pull-request/54'

* pull-request/54:
Allow arbitrary expressions for empty()

This change is as per RFC https://wiki.php.net/rfc/empty_isset_exprs.

Merge branch 'pull-request/54'

* pull-request/54:
Allow arbitrary expressions for empty()

This change is as per RFC https://wiki.php.net/rfc/empty_isset_exprs.

The change allows passing the result of function calls and other
expressions to the empty() language construct. This is accomplished by
simply rewriting empty(expr) to !expr.

The change does not affect the suppression of errors when using empty()
on variables. empty($undefinedVar) will continue not to throw errors.
When an expression is used inside empty() on the other hand, errors will
not be suppressed. Thus empty($undefinedVar + $somethingElse) *will*
throw a notice.

The change also does not make empty() into a real function, so using
'empty' as a callback is still not possible.

In addition to the empty() changes the commit adds nicer error messages
when isset() is used on function call results or other expressions.

show more ...

Changed ResourceBundle constructor behavior

null is now accepted for two first (mandatory arguments).

Passing null as the package name causes NULL to be passed to ICU and
the d

Changed ResourceBundle constructor behavior

null is now accepted for two first (mandatory arguments).

Passing null as the package name causes NULL to be passed to ICU and
the default ICU data to be loaded.

Passing null as the locale name causes the default locale to be used.

show more ...

add news for new pg_ functions

Note recent changes to ext/intl in UPGRADING

Dummy (whitespace) change so Dan Brown can verify snap generation from git

PHP snapshots were still pulling from SVN and were out of date. This
is a dummy PHP 5.4-only commit so Dan can

Dummy (whitespace) change so Dan Brown can verify snap generation from git

PHP snapshots were still pulling from SVN and were out of date. This
is a dummy PHP 5.4-only commit so Dan can verify what he's updated for
git in the backend.

show more ...

fd fix

update NEWS/UPGRADING

Keep date precision in MessageFormatter.

MessageFormatter::parse and MessageFormat::format (and their static
equivalents) now don't throw away better than second precision in the
arg

Keep date precision in MessageFormatter.

MessageFormatter::parse and MessageFormat::format (and their static
equivalents) now don't throw away better than second precision in the
arguments.

It's already bad enough that in MessageFormatter and IntlDateFormatter we
use seconds since epoch instead of milliseconds since epoch, deviating
from the ICU date representations. But we don't need to throw away extra
precision when parsing dates; we can keep the seconds since epoch
convention and return non integer doubles with only a small BC impact.
Note that we already could return doubles from MessageFormatter::parse if
the date was sufficiently in the past or in the future.

show more ...

Updated UPGRADING with changes to ext/intl.