- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
[netbeans] summarizing current problems
Fri, 2009-11-13, 08:25
Caoyuan,
Returning to not-complete parsing: during these weeks after first reporting
about this problem I ascertained there is somewhere the plugin (or it's deps)
code fragment which guesses there is some kind of correlation between class
names and file names.
I'd summarize all my problems (at current plugin state) this way:
1. basing on ant compiling tasks (as a result, frequent Shift-F11)
2. FU/rename don't find all occurences
3. not-complete parsing (false error reporting)
Probably, there are other, but they don't bother me :-) Say, incorrect vars
highlighting at such case:
val deep = new AnyRef { var deepVar = 1 }
val deepVal = deep.deepVar // deepVar MUST BE RED
isn't comparable with these three listed above.
Of course, it's just my experience, and anybody (with you at first place) has
own - probably different - view.
To not look too unglad, I say you, Caoyuan, thank you! Overall feeling of
using the plugin is very positive :-)
Andrew
Sat, 2009-11-14, 18:27
#2
Re: [netbeans] summarizing current problems
On Fri, Nov 13, 2009 at 3:36 PM, Caoyuan wrote:
> On Fri, Nov 13, 2009 at 3:25 PM, Andrew Gaydenko wrote:
>> Caoyuan,
>>
>> Returning to not-complete parsing: during these weeks after first reporting
>> about this problem I ascertained there is somewhere the plugin (or it's deps)
>> code fragment which guesses there is some kind of correlation between class
>> names and file names.
>>
>>
>> I'd summarize all my problems (at current plugin state) this way:
>>
>> 1. basing on ant compiling tasks (as a result, frequent Shift-F11)
>
> I've notice this issue, it usually happens on several dependent
> projects, when one of them was cleaned-built, the others may complain
> some classes are not found when "build", then have to "clean-build"
> it. I've begun to dig it.
I've submit patches to fix some ant scalac related issues, and tested
on my machine, a dependencies aware setting will be ready soon.
>
>> 2. FU/rename don't find all occurences
>
> Just finished some progress to get it better
>
>> 3. not-complete parsing (false error reporting)
>
> This usually happens when there are classes in a source file that has
> different file name from class name. I tried some tricks, but not
> success yet. It's in low priority among my todo list though.
>
>>
>> Probably, there are other, but they don't bother me :-) Say, incorrect vars
>> highlighting at such case:
>>
>> val deep = new AnyRef { var deepVar = 1 }
>> val deepVal = deep.deepVar // deepVar MUST BE RED
>
> I'll try to fix this.
>
>>
>> isn't comparable with these three listed above.
>>
>> Of course, it's just my experience, and anybody (with you at first place) has
>> own - probably different - view.
>>
>> To not look too unglad, I say you, Caoyuan, thank you! Overall feeling of
>> using the plugin is very positive :-)
>>
>>
>> Andrew
>>
>
On Fri, Nov 13, 2009 at 3:25 PM, Andrew Gaydenko wrote:
> Caoyuan,
>
> Returning to not-complete parsing: during these weeks after first reporting
> about this problem I ascertained there is somewhere the plugin (or it's deps)
> code fragment which guesses there is some kind of correlation between class
> names and file names.
>
>
> I'd summarize all my problems (at current plugin state) this way:
>
> 1. basing on ant compiling tasks (as a result, frequent Shift-F11)
I've notice this issue, it usually happens on several dependent
projects, when one of them was cleaned-built, the others may complain
some classes are not found when "build", then have to "clean-build"
it. I've begun to dig it.
> 2. FU/rename don't find all occurences
Just finished some progress to get it better
> 3. not-complete parsing (false error reporting)
This usually happens when there are classes in a source file that has
different file name from class name. I tried some tricks, but not
success yet. It's in low priority among my todo list though.
>
> Probably, there are other, but they don't bother me :-) Say, incorrect vars
> highlighting at such case:
>
> val deep = new AnyRef { var deepVar = 1 }
> val deepVal = deep.deepVar // deepVar MUST BE RED
I'll try to fix this.
>
> isn't comparable with these three listed above.
>
> Of course, it's just my experience, and anybody (with you at first place) has
> own - probably different - view.
>
> To not look too unglad, I say you, Caoyuan, thank you! Overall feeling of
> using the plugin is very positive :-)
>
>
> Andrew
>