"breger" wrote:
I've increased -XmX in the eclipse.ini file up to 1024. Any higher and I get a "Can't start the java virtual machine" error message and eclipse closes.
That message means you don't have 1GB of memory free to allocate to Eclipse.
Sounds like you either have very little memory installed on your machine, or you have a lot of other things running at the same time that are consuming lots of memory.
*However*
It's not yet clear that low memory was your original problem (based on the error messages, it's likely it's not).
"breger" wrote:
Once eclipse opens several files show errors. All of them are errors such as "Expecting End" and eclipse would be highlighting the letters 'rin' out of 'print' as the error.
I'd need to see a complete source code file example to know what's causing the "Expecting End" errors.
The error offset highlighting issue is separate and is a known eclipse bug (a race condition in updating the offsets for error markers). Doing a clean rebuild usually clears those up.
"breger" wrote:
I get an error message...
Save Failed
Middle member reference ('addparam') into an AA ('http.addparam') does not exist but should.
I've tried removing those lines from the file, but I get the same result.
If you truly removed all those lines (are you certain you got all instances in all source files?), then it should remove the errors following the invocation of a clean full build.
Note, in eclipse, a build is often necessary to remove previous error markers - editing alone is not sufficient.
Changing a file doesn't automatically result in a rebuild unless you have "Build Automatically" checked in the project menu.
And... Eclipse sometimes gets into a confused state and leaves previous error markers behind anyway - so sometimes you must manually invoke a clean build ( Clean... from the project menu ) even if "Build automatically" is checked.
In any case, that error message is due to a known bug in the BrightScript plugin involving ifAssociativeArray and ifEnum function/sub calls from context (m.*) variables.
The bug's been fixed, but the new plugin version containing the fix has not been published yet.
I'm lobbying the people in charge of plugin releases to publish a hotfix release ASAP, and they're looking at it.
If you can't wait, there is also a code workaround that's possible:
Use a text editor on the offending source files (you can temporarily switch to a text editor on .brs files in eclipse, just remember to switch back when done),
and replace any instance of an ifAssociativeArray and ifEnum function/sub call that starts with an "m.*" with 2 lines:
The first line is a new variable assignment of the m.* prefix up to just before the func/sub call itself, and...
The second line is the function/sub call using that new variable.
e.g.:
instead of something like this:
m.x.foo.addReplace(y,"bar")
replace it with this:
mxf = m.x.foo
mxf.addReplace(y,"bar")
"breger" wrote:
Everything worked before the upgrade.
Please tell me how to downgrade back to the previous eclipse plugin.
If you can't wait for the plugin hotfix, and the workaround mentioned above is too much to deal with... and you can live without the current plugin's bugfixes, enhancements, and new features, then...
Eclipse has a built-in revert mechanism:
http://help.eclipse.org/juno/index.jsp? ... ks-123.htmCheers
