Bug 268317

There are more features [1] that need to be supported for PHP 7.1.

Thanks.
[1] http://php.net/manual/en/migration71.php

MISSING FEATURES:

Nullable Types
==============
<?php ... function test(?string $name): ?string {...}

Multi catch exception handling
==============================
<?php ... catch (FirstException | SecondException $e) {}
- goes red in the editor

Support for keys in list()
==========================
<?php ... list("id" => $id1, "name" => $name1) = $data[0];
- goes red in the editor

Class constant visibility
=========================
<?php ... public const PUBLIC_CONST_B = 2;
- should be very easy to integrate

Symmetric array destructuring
=============================
<?php ... [$id1, $name1] = $data[0];
- not relevant ... we can just use list(...)

!!!THINGS THAT WORK OK!!!:

Void functions
========================
- works ok in the editor

iterable pseudo-type
====================
- shows ok in editor, no need to do anything

Support for negative string offsets
===================================
- works

The rest are just libs/function changes.


Thanks,
Alex

+1 for PHP 7.1 support

My top priorities for supported new features are nullable types and void return type.

+1 Thanks for working on this IDE. I hope you will create support of PHP 7.1.

+1
Don't want switch from NetBeans to PHPStorm only for php 7.1 support. Please add php 7.1 support to NetBeans)

Can we have a stage 1 for this issue please !!!

All we need is: 
1. Option to create a PHP 7.1 project
2. Modify the lexer to accept nullable types: "?TYPE"
(all we need here is not to highlight things as errors, 
just ingnore the "?" infront of a type)

I can help with the development if I get a bit of guidence 
especially with the LEXER.

PLEEEASE !!!

Regards,
Alex Stanciu

Sounds great :)



(In reply to ealexs from comment #6)
> Can we have a stage 1 for this issue please !!!
> 
> All we need is: 
> 1. Option to create a PHP 7.1 project
> 2. Modify the lexer to accept nullable types: "?TYPE"
> (all we need here is not to highlight things as errors, 
> just ingnore the "?" infront of a type)
> 
> I can help with the development if I get a bit of guidence 
> especially with the LEXER.
> 
> PLEEEASE !!!
> 
> Regards,
> Alex Stanciu

It's been almost six months since the first RC version and still not implemented support for 7.1
This "bug" is here more than four months...
It's ridiculous

Switched to PhpStorm...

(In reply to kucerapetrcz from comment #8)
> It's been almost six months since the first RC version and still not
> implemented support for 7.1
> This "bug" is here more than four months...
> It's ridiculous
> 
> Switched to PhpStorm...

It is. Luckily I have no hosts where is PHP7l so I do not develop under that, but I want to rewrite my framework to PHP7.1.

ealexs collected nicely, what they should do. Six month should be more than enogh.

Guys this is an easy win, all that people want is that the project will not go "all red" because of Nullable Types.
Everyone is moving from PHP 7.0 to 7.1 as 7.1 is already better supported (bugs fixed on 7.1 and not 7.0, ex: https://bugs.php.net/bug.php?id=74072 see "It is not possible to apply this change to PHP 7.0")

All we need is: 
1. Option to create a PHP 7.1 project
2. Modify the lexer to accept nullable types: "?TYPE"
(all we need here is not to highlight things as errors, just ingnore the "?" infront of a type)

Thank you, Alex

I'll do it. When it will be available, I'll write a comment here. So, please wait a while.

Thanks.

Are you doing this already junichi? Many of us are waiting, so when you has already declared to do this nobody else wouldn't.

(In reply to Starycjusz from comment #12)
> Are you doing this already junichi? Many of us are waiting, so when you has
> already declared to do this nobody else wouldn't.

Yes, I'm already working on this. As I wrote above, I will write a comment after I've finished it. Please wait since it takes time.

Thanks for your understanding.

I have improved the basic features(e.g. CC). 
Probably, it will be available tomorrow or later in the development build.
Please try to download and test it because there are bugs. If you find problems, please submit them to the NetBeans bugzilla as new issues.

Thanks!

Thanks. Fully fixed.

Where do I find version which supports PHP 7.1. It is essential for our project and we are aiming to switch IDE if we cannot make this feature available. Any hint? 
PLease help!

Please, do not reopen FIXED issues, simply report a new one.

(In reply to Kartopete from comment #16)
> Where do I find version which supports PHP 7.1. It is essential for our
> project and we are aiming to switch IDE if we cannot make this feature
> available. Any hint? 
> PLease help!

You have to use development version of NetBeans [1] or wait for next stable version of NetBeans (likely NetBeans 9.0).

Thanks.
[1] http://bits.netbeans.org/download/trunk/nightly/latest/

+1, I need PHP 7.1 support.

This is no longer ridiculous, this is a tragedy.
The fix is completed for 4 months but is still not released.
Meanwhile PhpStorm added support for php 7.2 ...

(In reply to kucerapetrcz from comment #19)
> This is no longer ridiculous, this is a tragedy.
> The fix is completed for 4 months but is still not released.
> Meanwhile PhpStorm added support for php 7.2 ...

Unfortunately, NetBeans release cycle is related to new Java version. So probably, NB9 would be released next month.
However, fortunately, as Tomas wrote above, you can use a development version[1].

We already prepared for PHP 7.2[2] (we cannot apply it soon, sorry).

[1] http://bits.netbeans.org/download/trunk/nightly/latest/
[2] https://netbeans.org/bugzilla/show_bug.cgi?id=270929

Thanks for your understanding.

The problem are the looong release cycles, we have to wait for the next big release for such feature which is not acceptable but it is as it is. Of course you can use nightly builds but as others, geertjan and I say, nightlies are not made for production usage. A patch would have been better.

As for me, I use nightly builds for months now in production, but I had to experiment which is stable. Now I use a 20170325 build, it is stable and PHP7.1 works just fine :)

How about releasing such features as plugins before the the stable release is ready ?
I think this type of feature makes a perfect candidate for a plugin rather than core.

Thanks.

I know that for the nbgit plugin. It started as a plugin and went to the core later. Same for twig. It could be a still a module for NetBeans but it should be released separately. Yes. Other IDEs/Editors have faster release cycles. This is a problem for years for NetBeans. Visual Studio Code brings an update each month. IntelliJ, WebStorm, PHPStorm I don't know but they release fast too.

I also am frustrated by the release cycle for PHP support. The work was done a while ago now. But it only is available through dev builds. And unfortunately those dev builds are far from being stable. I get regularly get Java exceptions and everything seems to be slightly slower than a production release.

On the other hand I am using a plugin to add support for TypeScript (https://github.com/Everlaw/nbts). Its release cycle is not tied to NetBeans and it's working great.

So I am kinda wondering why does PHP need to be tied to NetBeans release ? what are the advantage for end-users and/or developers ?

junichi11, do you know whether it would be technically possible to release PHP as a independent plugin more often ?

I don't think we need releases every week. Whenever a new PHP version is released should already be plenty enough and remove a lot of frustration for PHP developers.

It's not about the PHP release, it is about the NB release and what comes with NB. With NetBeans you have HTML/JS/CSS/SCSS/LESS, PHP, Java, C/C++ and something more. So if there are changes in those parts, they need to wait for a next release. Sometimes it happens after a release that you got patches, most of the time with bug fixes but somestimes little enhancements.

So it maybe this can be changed under Apache to have a better release cycle. It is really a pain in the ass and I used the nightlies long time ago every day with success and pain (I know the java exceptions too).

But this is not part of this topic, unfortunately we have to wait and hope for a better release cycles under apache. Maybe we should create a new ticket, but in JIRA, not here anymore.

Reported on JIRA: https://issues.apache.org/jira/browse/NETBEANS-51

Please contribute to the discussion over there, if you feel like the release cycle should change.

For me personally, I am in a situation where I would like to have most recent PHP in a stable release asap. However, this is due to our current situtation. I guess if you start a new software product, you always aiming at a stable IDE version which supports latest PHP. Later usually, you only very seldom update your PHP once a new version is there and therefore you could wait for a stable release with latest PHP. 
But ... as I said, right now, I would like to see this release as well, as I think some major features for PHP 7.1 have been missing on stable version. 
Cheers guys

Stable software is great, stable software takes time.
We need evolution not revolution.

The questions is: Can we have PHP x.x as a plugin ? so we don't have to wait for 1 year to get support for some very simple features, most of them drivven by a lexer configuration.

https://netbeans.org/bugzilla/show_bug.cgi?id=270019

Must read information for those who face NetBeans issues because it is letting us about Apache issue tracking system for new NetBeans issues. 

Ida,
Finance assignment writer,
<a href="http://www.assignmenthelpfolks.com/finance/">http://www.assignmenthelpfolks.com/finance/</a>

Must read information for those who face NetBeans issues because it is letting us about Apache issue tracking system for new NetBeans issues. 

Ida,
Finance Assignment Writer,
http://www.assignmenthelpfolks.com/finance/

very good post.
http://www.winmilliongame.com
http://www.gtagame100.com
http://www.subway-game.com
http://www.zumagame100.com