Ah, so thats the reason! Theres an easy fix for that i think, such that the implicit import at least shows the errors.
JurgenVinju (Nov 16 '11)edit
So, after I've changed a .rsc file in eclipse and I want to test my changes in the console, do I have to import the module again?
No, modules are imported automatically after every change.
In the current release this seems to be working fine, but in older versions this did not always work as expected (in particular when changing a module that was only indirectly imported in the console session).
Hence: no you don't have to reload manually after a change. Only in case of doubt you may want to reload manually.
While Paul's answer is almost correct, this does not hold if you've introduced a parsing error into your module. Than the old version of the module is used.
While some parse errors are visible by the red squiggly line in the editor, some problems such as those with function declarations with patterns as parameters are only shown after an explicit import statement.
So in case that the results of a re-run of the method does not change as you intended, try to import your module again and see if that reports any errors.
Ah, so thats the reason! Theres an easy fix for that i think, such that the implicit import at least shows the errors.
JurgenVinju (Nov 16 '11)editOver my recent Rascal development time, it happened several times that I changed a piece of my code, and even reimported it manually, but Rascal simply didn't notice the change! I had to restart my Eclipse to get Rascal finally reflect the change. There was nothing for me to log AFAIK except that I could have perhaps filmed the event. Whilst I couldn't think of this by that time, my supervisor also witnessed it.
Asked: Nov 15 '11
Seen: 34 times
Last updated: Jan 24
Copyright CWI, 2010-2012. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
