This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 189835 - "//"-comment in the last line makes problems
Summary: "//"-comment in the last line makes problems
Status: RESOLVED FIXED
Alias: None
Product: php
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows 7 x64
: P3 normal (vote)
Assignee: Tomas Mysik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-25 11:43 UTC by CyVizzes
Modified: 2011-06-06 16:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description CyVizzes 2010-08-25 11:43:56 UTC
If I have a php-file with a "//"-comment in the last line (*) and try to format it (with ALT + SHIFT + F) Netbeans depends for between 10 and 60 sek. After that the file is not formatted!

If I try to autocomplete a class/function (with STRG + SPACEBAR) depends for ca. 10 sek and then the letters that I typed are missing.
I can autocomplete namespace.

If I delete the "//"-comment all works fine.

(*) for example:
[code]
<?php
$var = 'value';
// <-- last Line!
[/code]

PS: I hope I have done everything right - this is my first report.
Comment 1 Petr Pisl 2010-08-31 15:35:43 UTC
I can confirm this. Thanks for reporting this.
Comment 2 Petr Pisl 2010-09-01 16:26:05 UTC
Fixed in the web-main. Should be in the dev build this night.
Comment 3 Quality Engineering 2010-09-02 03:17:43 UTC
Integrated into 'main-golden', will be available in build *201009020000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/984d8168fdd0
User: Petr Pisl <ppisl@netbeans.org>
Log: #189835 - "//"-comment in the last line makes problems
Comment 4 OndrejBrejla 2011-03-04 14:38:31 UTC
It works for me.
Comment 5 Tomas Mysik 2011-06-03 10:19:49 UTC
Batch reassigning.
Comment 6 Tomas Mysik 2011-06-06 16:07:10 UTC
Marking as fixed again, please provide reason (or use case) for reopening.

Thanks.