PHP plus: P++ proposal would create a stricter dialect

A new dialect of PHP, code-named P++, could be developed as a stricter variant of

its dynamic predecessor, with more advanced features and less baggage. The
proposal, being floated in the PHP community by PHP cofounder Zeev Suraski, would
have P++, or whatever it is eventually called, living alongside PHP but not bound
by PHP’s historical philosophy. P++ would not be a fork, but it would be inherently
more strict and could be more daring with backward compatibility. Elements now
considered “baggage,” such as short tags, could be removed while complex features,
especially ones for strictly typed languages such as strict operators or typed
variables, could be added without introducing the same complexity to the PHP
dialect. Like PHP itself, P++ would predominantly be for server-side web
development. The planned PHP 8 release already is expected to extend PHP beyond web
development, with a just-in-time engine and interoperability with C/C++ libraries.
The vast majority of code in PHP and P++ would be identical. Most code would be
shared between PHP and P++ nodes both in source and at runtime. But they would have
different implementations. Binaries will be identical. What is not clear yet is how
a file would be marked as a P++ file. It would probably have a special header at
the top. Builders also could find ways to mark entire namespaces as P++, so the
frameworks do not have to mark each file as P++. Data structures, web server
interfaces, key subsystems, and most everything else will be the exact same code
regardless of whether a file is executed as PHP or P++. Still, two versions of
certain pieces of code would have to be maintained. And P++ is likely to have
additional checks compared to PHP. Developers could mix and match PHP and P++ in
the same app. Both dialects could be run on a single server. If P++ happens, it
would mean a different evolution for PHP. Strictness and type-related features are
likely to go in P++. Bias for backward compatibility will stay in PHP. Unrelated
features, such as performance improvements in the engine or developments in
extensions, would be available in both P++ and PHP. Zuraski points out potential
options for the P++ language: Staying with a dynamic PHP, which would not be
accepted by proponents of a stricter language. Evolving toward a stricter PHP, not
acceptable to proponents of a more dynamic language. Forking the codebase, a net
loss for everyone involved. Devising a solution to cater to both audiences, which
is what the P++ proposal attempts. Concerns about the P++ proposal include:
Converting PHP code to P++ would not be trivial. How true that is will depend on
what ultimately ends up in P++. PHP tools will not support P++. But it could be
simpler for vendors to support P++ rather than support granular declare()s or an
unlimited amount of editions. Breaking of PHP compatibility. But doing so via a new
dialect rather than breaking PHP itself could be more palatable. P++ would differ
from Facebook’s Hack language, which was built on PHP, in that: Hack was developed
by a single company. Hack and the accompanying HHVM virtual machine do not have
PHP’s large distribution vehicle.

WordPress Proposes Plan for 61% of WP Sites Using Outdated PHP

WordPress development volunteers published a proposal to urge users of potentially

vulnerable versions of PHP to upgrade. An alarming number of WordPress users still
use PHP versions that no longer receive security updates. WordPress Addresses 61.6%
of Vulnerable Publishers PHP is the underlying scripting language that WordPress
runs on. The most current version is PHP 7.3.7. PHP is continually updated to make
it more efficient and to patch security issues. Except versions that have reached
“End of Life” status (EOL). PHP versions 5.6 and 7.0 reached EOL in December 2018.
PHP version 7.1 will reach EOL in December 2019. According to official WordPress
statistics, 45.3% of WordPress publishers are running their sites on PHP versions
5.6 and 7.0. An additional 16.3% of WordPress publishers are using versions that
are even older than 5.6. That’s a total of 61.6% of WordPress publishers who are
using versions of PHP that no longer receive security updates.NOTE: Those numbers
are 0.1% over 100%. 38.5% sites using valid PHP + 61.6% using retired versions of
PHP = 100.1%. Those numbers are from WordPress. 61.6% of WordPress Publishers are
Vulnerable This means that 61.6% of WordPress users may be vulnerable to hacking
events. The WordPress proposal is to get all out of date PHP users up to date by
using a nag screen. This means reaching all users of WordPress 5.6 and under plus
those who are still using version 7.0. This is the proposed timeline: “Our
suggested roadmap to increase the minimum PHP version is: Display the PHP update
widget for PHP 5.6. This will trigger the widget for anyone using PHP 5.6 or below
and WordPress 5.1+ in their dashboards warning them of the fact we recommend
upgrading the version of PHP. Display the PHP update widget for users of PHP 7.0
and below. Based around support and stats of points 1 and 2, have a discussion
about whether the next step should be displaying the PHP update widget for PHP 7.1
or a direct increase of the required minimum version to PHP 7.2.” WordPress
Proposal for Nag Screen Widget The official WordPress proposal calls for a nag
screen to display. The nag screen urges users to upgrade their PHP. Here’s what the
official announcement states: “I would like to propose we trigger displaying the
PHP update widget for users of PHP 5.6 in WordPress. At the time of writing, the
WordPress stats show that: PHP 5.6 has a usage share of 29.1%PHP 7.0 has a usage
share of 16.2%PHP 7.1 has a usage share of 13.2%” The first nag screen may begin
showing as soon as August 5, 2019. Subsequent nag screens will be determined at a
later date. Here’s the proposed timeline: “We suggest to start showing the update
recommendation for users of PHP 5.6 or lower starting August 5th, the timeline for
showing the warning to PHP 7.0 users will be announced in a followup post, and
relies on factors like support load, and adoption rate from the previous increase.”
Read the official WordPress discussion: Proposal for increasing recommended PHP
version in WordPress

Results of Single Center Study on Delcath’s PHP Therapy Published in Cancer Imaging

Retrospective Study by University Hospital of Tubingen Shows Median Overall

Survival of 27.4 Months in Patients with Ocular Melanoma Liver Metastases NEW YORK,
July 22, 2019 (GLOBE NEWSWIRE) -- Delcath Systems, Inc. (DCTH), an interventional
oncology company focused on the treatment of primary and metastatic cancers of the
liver, announces that results from a single-institution retrospective study
conducted by University Hospital of Tubingen (UHT) in Germany on the use of the
Delcath Hepatic CHEMOSAT® Delivery System to treat patients with metastatic ocular
melanoma with liver metastases were published in the journal Cancer Imaging. The
study, Chemosaturation with percutaneous hepatic perfusion of melphalan for liver
dominant metastatic uveal melanoma: a single center experience, by Dr. Christoph
Artzner, et al, evaluated the safety and efficacy of PHP® Therapy in 16 patients
with unresectable liver metastases from ocular melanoma treated with CHEMOSAT
between June 2015 and December 2018. Tumor response was evaluated following each
PHP treatment using Response Evaluation Criteria in Solid Tumors (RECIST), and
serious adverse events (SAEs) were evaluated using Common Criteria for Adverse
Events (CTCAE). The 16 patients underwent a total of 28 PHP treatments. Results of
the study in the 15 evaluable patients showed that after the first PHP treatment,
nine patients (60%) had a partial response (PR), five patients (33%) stable
disease, and one patient (7%) had progressive disease for an initial disease
control rate of 93%. Median progression free survival (PFS) after the first
treatment was 11.1 months. Six patients received a second PHP treatment, three
patients received three treatments, and a single patient received six treatments.
Median overall survival (OS) was 27.4 months. Safety analysis showed that grade
three SAEs were observed in 14% of treatments, and these were anemia, leukopenia
and thrombocytopenia. The sole grade four SAE observed was in one patient who
suffered a cardiac arrest during the first PHP treatment and was removed from the
study. Subsequent evaluation discovered this patient had coronary artery occlusion
which was successfully treated. Retrospective evaluation of this patient’s pre-
procedure imaging reveal signs of coronary artery disease, and investigators
subsequently modified their screening procedures for cardiovascular risk factors.
Investigators stated that most SAEs were grade one or two and that 5% of the
reported grade three and four SAEs required additional intervention. Investigators
concluded that for patients with liver-dominant metastatic uveal melanoma,
treatment with PHP Therapy had “observed rates for OS and PFS that exceeded the
reported outcomes for traditional systemic treatment.” Investigators stated that
SAEs were frequent, but most did not require additional intervention, and that care
should be taken in patients with suspected coronary heart disease. About
Delcath Systems Delcath Systems, Inc. is an interventional oncology Company focused
on the treatment of primary and metastatic liver cancers. Our investigational
product – Melphalan Hydrochloride for Injection for use with the Delcath Hepatic
Delivery System (Melphalan/HDS) – is designed to administer high-dose chemotherapy
to the liver while controlling systemic exposure and associated side effects. We
have been enrolling a global Registration clinical trial for Patients with Hepatic
Dominant Ocular Melanoma (OM) called The FOCUS Trial and have initiated a global
Phase 3 clinical trial for intrahepatic cholangiocarcinoma (ICC) called The ALIGN
Trial. Melphalan/HDS has not been approved by the U.S. Food & Drug
Administration (FDA) for sale in the U.S. In Europe, our system is marketed under
the trade name Delcath Hepatic CHEMOSAT® Delivery System for Melphalan (CHEMOSAT)
and has been used at major medical centers to treat a wide range of cancers of the
liver. Since January 2019 CHEMOSAT is marketed under an exclusive licensing
agreement with medac, a privately held multi-national pharmaceutical company
headquartered in Germany which specializes in the diagnosis and treatment of
oncological, urological and autoimmune diseases. Forward Looking Statements Story
continues Private Securities Litigation Reform Act of 1995 provides a safe harbor
for forward-looking statements made by the Company or on its behalf. This news
release contains forward-looking statements, which are subject to certain risks and
uncertainties that can cause actual results to differ materially from those
described. Factors that may cause such differences include, but are not limited to,
uncertainties relating to: the timing and results of the Company’s clinical
trials including without limitation the OM and ICC clinical trial programs,
timely enrollment and treatment of patients in the global Phase 3 OM and ICC
Registration trials, IRB or ethics committee clearance of the Phase 3 OM and ICC
Registration trial protocols from participating sites and the timing of site
activation and subject enrollment in each trial, the impact of the presentations at
major medical conferences and future clinical results consistent with the data
presented, the Company’s ability to successfully commercialize the Melphalan
HDS/CHEMOSAT system and the potential of the Melphalan HDS/CHEMOSAT system as a
treatment for patients with primary and metastatic disease in the liver, our
ability to obtain reimbursement for the CHEMOSAT system in various markets,
approval of the current or future Melphalan HDS/CHEMOSAT system for delivery and
filtration of melphalan or other chemotherapeutic agents for various indications in
the U.S. and/or in foreign markets, actions by the FDA or other foreign regulatory
agencies, the impact of the Company’s exclusive licensing agreement with medac on
commercial adoption in Europe and resulting revenue, if any, the Company’s ability
to successfully enter into other strategic partnerships and distribution
arrangements in foreign markets and the timing and revenue, if any, of the same,
uncertainties relating to the timing and results of research and development
projects, and uncertainties regarding the Company’s ability to obtain financial and
other resources for any research, development, clinical trials and
commercialization activities. These factors, and others, are discussed from time to
time in our filings with the Securities and Exchange Commission. You should not
place undue reliance on these forward-looking statements, which speak only as of
the date they are made. We undertake no obligation to publicly update or revise
these forward-looking statements to reflect events or circumstances after the date
they are made. Contact:Delcath Investor RelationsEmail:
investorrelations@delcath.com