I have wondered if we aren't shooting ourselves in the foot by asking for more and more functionality in the product, especially when the functions exist elsewhere in the system. As RDi gets bigger and bigger and more and more complex, doesn't that increase the chances that new releases will have issues?
------------------------------
message: 6
date: Fri, 2 Oct 2015 17:53:08 +0000
from: Ken Killian <kkillian@xxxxxxxxxxxx>
subject: Re: [WDSCI-L] Memory Leaks?
My C.I.O. asked me if RDI has finally become Stable. I had to be honest and say "NO"...
That was an Omen... <Sad Face>
I tried to open a member with only 741 lines of code, and I get this error:
An internal error occurred during: "Live parsing MCDTHBRL.SQLRPGLE".
java.lang.StackOverflowError
I have restarted 6-times, and same error every time.
I hate OUTLINE View, when I used the OLD WDSC without outline view, WDSC was awesome! I had a lot fewer errors....
I should be able to VIEW CODE. That should be 100% STABLE/PERFECT.
Do NOT get me wrong, I love outline view & code-Assist, but if it makes the product UNSTABLE, what good is it?
My memory is 99M of 175M....
I guess I need to turn off OUTLINE View, and quit using that Unstable feature, it is NOT worth it....
windows>preferences>Remote System>Remote System LPEX Editor>ILE RPG
O uncheck "Automatic syntax checking of SQL Statements (performed on the Server)
O Uncheck "Update the Outline view when text is changed in the editor"
THAT WORKED! <Joy Joy> Back to No Frills Code Editor...
But, there Verify shows errors on SQL statements in the Methods (a.k.a. Procedures)....
Death by 1,000 papercuts continues...
-Ken Killian-
PS. Going to the vending machine to get a snickers bar. I am not myself, when RDI doesn't work... :(
midrange.com
