Smalltalk › Pharo › Pharo Smalltalk Developers

garbage on transcript

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

11 messages Options

stepharo

garbage on transcript

Hi

when I define methods and the Transcript is open I get such kind of
trace and I do not get where it comes from.
I think that this is the syntactical coloring.
Would be good to avoid because this is annoying.

StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared)

UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared)

Stef

Thierry Goubier

Re: garbage on transcript

Hi Stef,

yes, this is annoying.

Thierry

Le 08/09/2015 08:09, stepharo a écrit :

> Hi
>
> when I define methods and the Transcript is open I get such kind of
> trace and I do not get where it comes from.
> I think that this is the syntactical coloring.
> Would be good to avoid because this is annoying.
>
> StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared)
>
> UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared)
>
> Stef
>
>

Marcus Denker-4

Re: garbage on transcript

In reply to this post by stepharo

Yes, we do name analysis on the AST before coloring it…

Even worse than the transcript output are

-> it adds everything into Undeclared
-> Playground colors variables wrong that the playground knows as the name analysis does
not setup the requestorscope correctly.

I will add issue tracker entries…

Marcus

> On 08 Sep 2015, at 08:09, stepharo <[hidden email]> wrote:
>
> Hi
>
> when I define methods and the Transcript is open I get such kind of trace and I do not get where it comes from.
> I think that this is the syntactical coloring.
> Would be good to avoid because this is annoying.
>
> StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared)
>
> UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared)
>
> Stef
>

Eliot Miranda-2

Re: garbage on transcript

On Tue, Sep 8, 2015 at 5:13 AM, Marcus Denker <[hidden email]> wrote:

Yes, we do name analysis on the AST before coloring it…

Even worse than the transcript output are

-> it adds everything into Undeclared
-> Playground colors variables wrong that the playground knows as the name analysis does
not setup the requestorscope correctly.

I will add issue tracker entries…

Alternatively one could simply use Shout, a specialized parser for syntax highlighting that is simple, efficient, mature and customizable.

Marcus

> On 08 Sep 2015, at 08:09, stepharo <[hidden email]> wrote:
>
> Hi
>
> when I define methods and the Transcript is open I get such kind of trace and I do not get where it comes from.
> I think that this is the syntactical coloring.
> Would be good to avoid because this is annoying.
>
> StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared)
>
> UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared)
>
> Stef
>

_,,,^..^,,,_

best, Eliot

Marcus Denker-4

Re: garbage on transcript

On 08 Sep 2015, at 15:19, Eliot Miranda <[hidden email]> wrote:

On Tue, Sep 8, 2015 at 5:13 AM, Marcus Denker <[hidden email]> wrote:
Yes, we do name analysis on the AST before coloring it…

Even worse than the transcript output are

-> it adds everything into Undeclared
-> Playground colors variables wrong that the playground knows as the name analysis does
not setup the requestorscope correctly.

I will add issue tracker entries…

Alternatively one could simply use Shout, a specialized parser for syntax highlighting that is simple, efficient, mature and customizable.

The idea was to reduce the amount of Parsers (and models of methods) in the system…

Marcus

Eliot Miranda-2

Re: garbage on transcript

Hi Marcus,

On Tue, Sep 8, 2015 at 6:28 AM, Marcus Denker <[hidden email]> wrote:

On 08 Sep 2015, at 15:19, Eliot Miranda <[hidden email]> wrote:

On Tue, Sep 8, 2015 at 5:13 AM, Marcus Denker <[hidden email]> wrote:
Yes, we do name analysis on the AST before coloring it…

Even worse than the transcript output are

-> it adds everything into Undeclared
-> Playground colors variables wrong that the playground knows as the name analysis does
not setup the requestorscope correctly.

I will add issue tracker entries…

Alternatively one could simply use Shout, a specialized parser for syntax highlighting that is simple, efficient, mature and customizable.

The idea was to reduce the amount of Parsers (and models of methods) in the system…

I understand that. But parsing for code generation is very different from the quick and simple parsing for syntax highlighting that Shout provides, and if one ends up complicating the former to make it encompass the latter then maybe that's not such a good idea. I'd rather have a number of smaller simpler parsers than one great big complex difficult to understand and full of special cases parser (think... Morphic). Just a thought.

Marcus

_,,,^..^,,,_

best, Eliot

Marcus Denker-4

Re: garbage on transcript

On 08 Sep 2015, at 15:53, Eliot Miranda <[hidden email]> wrote:

Hi Marcus,

On Tue, Sep 8, 2015 at 6:28 AM, Marcus Denker <[hidden email]> wrote:

On 08 Sep 2015, at 15:19, Eliot Miranda <[hidden email]> wrote:

On Tue, Sep 8, 2015 at 5:13 AM, Marcus Denker <[hidden email]> wrote:
Yes, we do name analysis on the AST before coloring it…

Even worse than the transcript output are

-> it adds everything into Undeclared
-> Playground colors variables wrong that the playground knows as the name analysis does
not setup the requestorscope correctly.

I will add issue tracker entries…

Alternatively one could simply use Shout, a specialized parser for syntax highlighting that is simple, efficient, mature and customizable.

The idea was to reduce the amount of Parsers (and models of methods) in the system…

I understand that. But parsing for code generation is very different from the quick and simple parsing for syntax highlighting that Shout provides, and if one ends up complicating the former to make it encompass the latter then maybe that's not such a good idea. I'd rather have a number of smaller simpler parsers than one great big complex difficult to understand and full of special cases parser (think... Morphic). Just a thought.

Yes… but the Shout parser is actually not that simple.

SHParserST80 package linesOfCode “2581”

And if you then see how much work the completion system has to do to get structural information out of the token stream it that is already in a normal AST by default…

Until now the only real change to the RB Parser is the feature to generate an error node for syntactically wrong input. (#parseFaultyExpression/#parseFaultyMethod).

Everything else was ok as is. The AST is unchanged (and we therefore use the same AST for the RB Engine, the Compiler and the syntax highlighter).

Marcus

stepharo

Re: garbage on transcript

In reply to this post by Eliot Miranda-2

The idea was to reduce the amount of Parsers (and models of methods) in the system…

I understand that. But parsing for code generation is very different from the quick and simple parsing for syntax highlighting that Shout provides, and if one ends up complicating the former to make it encompass the latter then maybe that's not such a good idea. I'd rather have a number of smaller simpler parsers than one great big complex difficult to understand and full of special cases parser (think... Morphic). Just a thought.

Elliot when I start to think about Morphic.... :)

Marcus

_,,,^..^,,,_

best, Eliot

Marcus Denker-4

Re: garbage on transcript

In reply to this post by Marcus Denker-4

This has been fixed in 5.0 418 (yesterday).

> On 08 Sep 2015, at 09:13, Marcus Denker <[hidden email]> wrote:
>
> Yes, we do name analysis on the AST before coloring it…
>
> Even worse than the transcript output are
>
> -> it adds everything into Undeclared
> -> Playground colors variables wrong that the playground knows as the name analysis does
> not setup the requestorscope correctly.
>
> I will add issue tracker entries…
>
> Marcus
>> On 08 Sep 2015, at 08:09, stepharo <[hidden email]> wrote:
>>
>> Hi
>>
>> when I define methods and the Transcript is open I get such kind of trace and I do not get where it comes from.
>> I think that this is the syntactical coloring.
>> Would be good to avoid because this is annoying.
>>
>> StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared)
>>
>> UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared)
>>
>> Stef
>>
>

stepharo

Re: garbage on transcript

Thanks!

Le 6/11/15 14:47, Marcus Denker a écrit :

> This has been fixed in 5.0 418 (yesterday).
>
>> On 08 Sep 2015, at 09:13, Marcus Denker <[hidden email]> wrote:
>>
>> Yes, we do name analysis on the AST before coloring it…
>>
>> Even worse than the transcript output are
>>
>> -> it adds everything into Undeclared
>> -> Playground colors variables wrong that the playground knows as the name analysis does
>> not setup the requestorscope correctly.
>>
>> I will add issue tracker entries…
>>
>> Marcus
>>> On 08 Sep 2015, at 08:09, stepharo <[hidden email]> wrote:
>>>
>>> Hi
>>>
>>> when I define methods and the Transcript is open I get such kind of trace and I do not get where it comes from.
>>> I think that this is the syntactical coloring.
>>> Would be good to avoid because this is annoying.
>>>
>>> StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared)
>>>
>>> UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared)
>>>
>>> Stef
>>>
>
>

Tudor Girba-2

Re: garbage on transcript

+1

Doru

> On Nov 6, 2015, at 10:04 PM, stepharo <[hidden email]> wrote:
>
> Thanks!
>
>
> Le 6/11/15 14:47, Marcus Denker a écrit :
>> This has been fixed in 5.0 418 (yesterday).
>>
>>> On 08 Sep 2015, at 09:13, Marcus Denker <[hidden email]> wrote:
>>>
>>> Yes, we do name analysis on the AST before coloring it…
>>>
>>> Even worse than the transcript output are
>>>
>>> -> it adds everything into Undeclared
>>> -> Playground colors variables wrong that the playground knows as the name analysis does
>>> not setup the requestorscope correctly.
>>>
>>> I will add issue tracker entries…
>>>
>>> Marcus
>>>> On 08 Sep 2015, at 08:09, stepharo <[hidden email]> wrote:
>>>>
>>>> Hi
>>>>
>>>> when I define methods and the Transcript is open I get such kind of trace and I do not get where it comes from.
>>>> I think that this is the syntactical coloring.
>>>> Would be good to avoid because this is annoying.
>>>>
>>>> StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared)
>>>>
>>>> UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared)
>>>>
>>>> Stef
>>>>
>>
>>
>
>

--
www.tudorgirba.com

"The coherence of a trip is given by the clearness of the goal."