Smalltalk › Frameworks & Tools › Moose

GTExample with dependencies no longer considered example

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Peter Uhnak

Oct 07, 2017; 12:41pm

GTExample with dependencies no longer considered example

Hi,

apparently CompiledMethod>>#isGTExampleMethod

has been changed from

isGTExampleMethod

^ self pragmas anySatisfy: [ :each | each isGTExamplePragma ]

isGTExampleMethod

^ (self pragmas anySatisfy: [ :each | each isGTExamplePragma ])

and: [ self numArgs = 0 ]

( https://github.com/feenkcom/gtoolkit-examples/blob/master/src/GToolkit-Examples.package/CompiledMethod.extension/instance/isGTExampleMethod.st , also strange that I don't see the history of the method on github).

In either case this means that if an example has dependencies it is no longer an example, because it has arguments.

Thanks,

Peter

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.list.inf.unibe.ch/listinfo/moose-dev

Tudor Girba-2

Oct 07, 2017; 2:12pm

Re: GTExample with dependencies no longer considered example

Hi Peter,

Nice catch :). Let me explain.

Indeed, we are working right now on the new examples engine, and last night we switched the Moose configurations to use the new engine.

The new engine no longer uses pragmas to describe dependencies, but plain unary message sends. So, now the engine recognizes these dependencies:

exampleA
<gtExample>
^ 41

exampleB
<gtExample>
| a |
a := self exampleA.
^ a + 1

Cheers,
Doru

> On Oct 7, 2017, at 2:41 PM, Peter Uhnák <[hidden email]> wrote:
>
> Hi,
>
> apparently CompiledMethod>>#isGTExampleMethod
>
> has been changed from
>
> isGTExampleMethod
> ^ self pragmas anySatisfy: [ :each | each isGTExamplePragma ]
>
> to
>
> isGTExampleMethod
> ^ (self pragmas anySatisfy: [ :each | each isGTExamplePragma ])
> and: [ self numArgs = 0 ]
>
> ( https://github.com/feenkcom/gtoolkit-examples/blob/master/src/GToolkit-Examples.package/CompiledMethod.extension/instance/isGTExampleMethod.st , also strange that I don't see the history of the method on github).
>
> In either case this means that if an example has dependencies it is no longer an example, because it has arguments.
>
> Thanks,
> Peter
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.list.inf.unibe.ch/listinfo/moose-dev

... [show rest of quote]

--
www.tudorgirba.com
www.feenk.com

"Presenting is storytelling."

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.list.inf.unibe.ch/listinfo/moose-dev

Peter Uhnak

Oct 07, 2017; 6:16pm

Re: GTExample with dependencies no longer considered example

On Sat, Oct 7, 2017 at 4:12 PM, Tudor Girba <[hidden email]> wrote:

Hi Peter,

Nice catch :). Let me explain.

Indeed, we are working right now on the new examples engine, and last night we switched the Moose configurations to use the new engine.

The new engine no longer uses pragmas to describe dependencies, but plain unary message sends. So, now the engine recognizes these dependencies:

exampleA
<gtExample>
^ 41

exampleB
<gtExample>
| a |
a := self exampleA.
^ a + 1

... [show rest of quote]

Ah, I see. This is indeed more practical when I want to call the method directly.

Thanks!

Peter

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.list.inf.unibe.ch/listinfo/moose-dev