An Oracle blog about NetBeans for PHP

Marking returns

The new feature, which I want to mentioned today, is a functionality that should simplify identifying return points from a method or a function.

As you can see on the picture, when you place cursor into the function keyword in a function or method declaration, then the function keyword and all return statements are highlighted.

Join the discussion

Comments ( 8 )
  • Andrew Gaydenko Wednesday, December 10, 2008


    Your blog forces me to begin to try Hudson builds - you are really fast! Thanks and thanks for your efforts!

    (do I understand well, development (nightly or Hudson) builds and upcoming 6.5 patch1 are absolutely different branches?)

  • optik Wednesday, December 10, 2008

    You rocks! Nice feature.

  • FragMaster B Wednesday, December 10, 2008

    These quick little features/tips are great. Keep them going please. I love the concept of learning one new feature a day like this.

  • Petr Wednesday, December 10, 2008

    To Andrew:

    >development (nightly or Hudson) builds and

    >upcoming 6.5 patch1 are absolutely different


    Yes, the trunk (nightly and Hudson) builds are development builds of NetBeans 7.0. NB 6.5 patch1 is different branch and there go only some save fixes from trunk. No new features.



  • pcdinh Thursday, December 11, 2008

    What about marking Exception (highlighting the code line

    throws new DatatabaseException($message)

  • Petr Thursday, December 11, 2008

    Hi pcdinh,

    we were thinking about this as well, but then decide that this is not the real return point. Probably it could be option based.



  • pcdinh Friday, December 12, 2008

    Can Netbeans detect uncatched exceptions. I know that it is not a return point. But it is an exit point.

  • links of london Thursday, October 29, 2009

    It was a very nice idea! Just wanna say thank you for the information you have shared. Just continue writing this kind of post. I will be your loyal reader. Thanks again.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.