And now the question for the monday morning development effort is: what more semantic warnings of the compiler can we reveal like this? :-)On Nov 28, 2015, at 19:06, Cyril Ferlicot <cyril.ferlicot@gmail.com> wrote:This is really cool ! :)One more step to get a nice IDE!Thank you for your efforts :)
On Saturday, November 28, 2015, Marcus Denker <marcus.denker@inria.fr> wrote:Hi,One result of Friday���s Pharo Sprint in Chile: Use the nice icons of the new text editorto display some of the semantic errors nicely (instead of breaking flow with a intrusive dialog):This was done by Johan based on the prototype Miguel did in September:1) unused temps:<unused.png>(the ���drag the crosshair���r is an artefact of the snapshot tool)2) temps used that are not initialised:<uninit.png>In a next step, we need to integrate that with the QA tool��� no need to have this reportedtwice.What is nice is that this simplified the Compiler: instead of having an Exception and raisingit, we now just annotate the AST:unusedVariable: variableNodevariableNode propertyAt: #semanticWarning put: 'unused variable���(this is very simple for now, with a node just being able to have one kind of semanticWarning).SemanticWarningIconStyler is what adds the icon. It has 4 methods with one line each.Marcus
--CheersCyril Ferlicot
---> Save our in-boxes!��http://emailcharter.org <---
Johan Fabry �� - ����http://pleiad.cl/~jfabry
PLEIAD and RyCh labs ��- ��Computer Science��Department (DCC) ��- ��University of Chile