[Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

[Manuel Leuenberger]

Hi,

I am currently playing with MetaLinks in Pharo 7 and stumbled upon some issues. 
For example, I found that instrumenting message sends may break compilation 
(see 
https://pharo.fogbugz.com/f/cases/22681/Metalink-on-message-may-break-compilation
 
).
 Two other issues also arised:

i) How do I reify the value of an RB(Valuel|Literal|LiteralValue)Node? 
RFValueReification does not work, and there is no reification for literal, 
value, or literal value nodes.
ii) How do I reify arguments and results of blocks? I tried reify context for 
the block body #before and value for #after block "last", but I often run into 
the problem of no reification for literals.
iii) How are cascaded message sends reified? Am I supposed to instrument the 
cascade node or the individual message sends?

I am grateful for any pointers towards a solution. BTW, Marcus' lecture slides 
give a great intro to metalinks 
(http://marcusdenker.de/talks/18LectureMetaLinks/MetaLinks.pdf 
).

Cheers,
Manuel

[Pharo-users] Iceberg documentation, tutorial, video

[nacho]

Hi!
I'm trying to learn how to use Iceberg to switch my projects to GutHub.
Are there any docs, tutorials o video showing how to configure, use,
Iceberg?
Thanks in advance!
cheers
nacho




-
Nacho
Smalltalker apprentice.
Buenos Aires, Argentina.
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

[Pharo-users] Pharo 7 Loading stops at Seaside-Pharo-JSON-Jo....5

[Sanjay Minni]

How do I proceed from here ?

(Pharo 7 32 bit on Win 10) 

whle installing a developed package - Loading stops at
Seaside-Pharo-JSON-Jo5

This package depends on the following classes:
  WAPharoEncoder
You must resolve these dependencies before you will be able to load these
definitions: 
  WAPharoJsonEncoder
  WAPharoJsonEncoder>>#delegateOn:
  WAPharoJsonEncoder>>#initialize
  WAPharoJsonEncoder>>#initializeJsonTable





-
---
Regards, Sanjay
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

[Marcus Denker]

Hi,

Thanks! I will check all of them… it might very well be that they are not 
implemented / there are bugs.

I will add them to the bug list.

(the problem is that each of them takes effort… write test, stare at byte-code… 
so it will take some time)

> On 19 Nov 2018, at 09:30, Manuel Leuenberger  wrote:
> 
> Hi,
> 
> I am currently playing with MetaLinks in Pharo 7 and stumbled upon some 
> issues. For example, I found that instrumenting message sends may break 
> compilation (see 
> https://pharo.fogbugz.com/f/cases/22681/Metalink-on-message-may-break-compilation
>  
> ).
>  Two other issues also arised:
> 
> i) How do I reify the value of an RB(Valuel|Literal|LiteralValue)Node? 
> RFValueReification does not work, and there is no reification for literal, 
> value, or literal value nodes.
> ii) How do I reify arguments and results of blocks? I tried reify context for 
> the block body #before and value for #after block "last", but I often run 
> into the problem of no reification for literals.
> iii) How are cascaded message sends reified? Am I supposed to instrument the 
> cascade node or the individual message sends?
> 
> I am grateful for any pointers towards a solution. BTW, Marcus' lecture 
> slides give a great intro to metalinks 
> (http://marcusdenker.de/talks/18LectureMetaLinks/MetaLinks.pdf 
> ).
> 
> Cheers,
> Manuel
> 

Re: [Pharo-users] [Pharo-dev] Pharo 7 speed compared to VW

[Eliot Miranda]

Hi Shaping,

On Mon, Nov 19, 2018 at 5:04 AM Shaping  wrote:

> (Second try in 6 days.  Does anyone have recent performance data for Pharo
> 7 relative to VW 7.10 or later?)
>

I don't have access to recent vnc versions beyond 7.7.  If you have access
perhaps you could run the computer language shootout benchmarks (
https://benchmarksgame-team.pages.debian.net/benchmarksgame/faster/smalltalk.html)
and report the results.


>
>
> *From:* Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] *On Behalf
> Of *Shaping
> *Sent:* Tuesday, November 13, 2018 00:33
> *To:* 'Pharo Development List' 
> *Subject:* [Pharo-dev] Pharo 7 speed compared to VW (was: The STON
> Specification, Cog speed, and namespaces/modules)
>
>
>
> Does anyone know whether  Pharo 7 is as fast as VW 7.10 or later?
>
>
>
> Do we have recent comparative benchmarks?
>
>
>
> The comparison should ignore potential GPU-based improvement in my algo;
> that will happen later.  The test should involve some math, file streaming,
> and the parsing that entails—an ordinary mix of macrobenchmarks.  The
> comparison should be based on both Pharo 7 and VW each running a single
> Smalltalk Process (one time-slice of one OS thread in one OS process).   I
> need Pharo 7 speed to be comparable or better to justify the port.
>
>
>
> Pharo is definitely looking and working better.  I’ve spend more time with
> it last few weeks than during the previous decade.  Thanks to everyone for
> the effort and improvements.
>
>
>
>
>
> Shaping
>
>
>
> *From:* Shaping [mailto:shap...@uurda.org ]
> *Sent:* Wednesday, November 7, 2018 00:41
> *To:* 'Pharo Development List' 
> *Subject:* RE: [Pharo-dev] [ANN] The STON Specification, Cog speed, and
> namespaces/modules
>
>
>
> Hi Eliot.
>
>
>
> Pharo (& Squeak & Cuis) Float subclass BoxedFloat64 maps exactly to
> VW's Double. In 64-bit SmallFloat64 maps exactly to SmallDouble. But I
> wonder whether there is any issue here.  STON would use the print strings
> for (PSC) Float / (VW) Double, and so deseerialization on Pharo would
> automatically produce the right class.  Going in the other direction might
> need some help.  APF needs support in PSC before one can port, but are
> representable as suitably-sized word arrays.
>
>
>
> There is no support for __float128 anywhere in the VM (e.g. not even in
> the FFI) on PSC as yet.
>
>
>
> I see Pharo’s WordArray.  I’ll work on an APF for Pharo, as time permits.
> I’m using APFs in VW in the 300-bit range, and want to reduce the needed
> precision to 64 bits, to save space and time on large (5 million+) scalar
> time-series, both on the heap and during BOSSing (25 m save-time now).
> The problem is not  so much an issue for the JulianDayNumber
> (JDN)-precision, which is adequate in this app at 14 to 15 digits (even
> though my JDN class subclasses APF, for now).  Other calculations need the
> more extreme precision.  I think I can make 128-bit floats work, and would
> really like to see a small, fast, boxed 128-bit float implementation in
> Pharo or VW.   The APFs are big and slow.  Where in the queue of planned
> improvements to Pharo does such a task lie?  I suspect it’s not a very
> popular item.
>
>
>
> Broadening the issue somewhat, I’m trying to find as many good reasons as
> possible to justify the work needed to port all my VW stuff to Pharo.
>
>
>
> I’ve seen the references to Cog’s speed and coming speed-up.  Are there
> recent (say, in the last year) benchmarks comparing VW and Pharo?   Any
> details here would be very much appreciated.
>
>
>
> Having no namespaces in Pharo is, I think, the biggest impediment.   I
> prefer not to prefix class names, but there may be fewer name-collisions
> than I suppose--maybe none.   Still, I need to know how VW and Pharo
> classes map in order to place overrides and extensions correctly.  Besides
> the mentioned float-class mappings is there a reference on this?
>
>
>
> Object allSubclasses
>
>
>
> in Pharo 7 64-bit, produces 14946 classes.  Pharo is a little bigger than
> it used to be.
>
>
>
> I suppose I don’t need to check all unloaded packages because all classes
> in each of those will have the same unique prefix. Is that correct?  Or, I
> could just load every package I can find, before I check names.  But that
> little experiment has never gone well in the past.
>
>
>
> Is the Pharo-with-namespaces issue dead or merely suspended, awaiting a
> more fitting idea than what VW currently offers?
>
>
>
>
>
> Shaping
>
>
>
>
>
> On Tue, Nov 6, 2018 at 12:56 AM Shaping  wrote:
>
> STON is able to serialise Pharo’s Floats, what do you mean by double ?
>
>
>
> Floating-point numbers in IEEE 64-bit format, 14 or 15 significant digits,
> with a range between =10^307 and 10^307.
>
>
>
> Additionally, I recently asked Sven if t would be possible to store
> ScaledDecimals (I think it implements what you call
> ArbitraryPrecisionFloats) without loss of precision.
>
>
>
> I’m referring to VW’s Double (and SmallDouble in 64-bit engines/image

Re: [Pharo-users] Pharo 7 Loading stops at Seaside-Pharo-JSON-Jo....5

[Sven Van Caekenberghe]

You need to tell us how are loading Seaside, exactly.

Using 

Metacello new
 baseline:'Seaside3';
 repository: 'github://SeasideSt/Seaside:master/repository';
 load.

?

The dev build on P7 passes it seems https://travis-ci.org/SeasideSt/Seaside

> On 19 Nov 2018, at 17:34, Sanjay Minni  wrote:
> 
> How do I proceed from here ?
> 
> (Pharo 7 32 bit on Win 10) 
> 
> whle installing a developed package - Loading stops at
> Seaside-Pharo-JSON-Jo5
> 
> This package depends on the following classes:
>  WAPharoEncoder
> You must resolve these dependencies before you will be able to load these
> definitions: 
>  WAPharoJsonEncoder
>  WAPharoJsonEncoder>>#delegateOn:
>  WAPharoJsonEncoder>>#initialize
>  WAPharoJsonEncoder>>#initializeJsonTable
> 
> 
> 
> 
> 
> -
> ---
> Regards, Sanjay
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> 

Re: [Pharo-users] Pharo on Linux

[Hans-Martin]

One thing that I've learned to appreciate quickly is the pharo launcher. It
takes care of downloading everything you need (of course, it won't set up a
32-bit environment in a 64-bit Linux for you, that must be done manually).
Used it in Linux and Windows environments with good success, it's really the
simplest way of quickly comparing different without much hassle.

Cheers,
Hans-Martin



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

[Manuel Leuenberger]

Thanks for picking this up into the backlog. I am not blocked if I don't have them, I was just curious. I am quite intrigued with the idea of reyfing the runtime semantics, this opens a whole lot of opportunities for tools based on dynamic data.On Nov 19, 2018 17:40, Marcus Denker  wrote:Hi,Thanks! I will check all of them… it might very well be that they are not implemented / there are bugs.I will add them to the bug list.(the problem is that each of them takes effort… write test, stare at byte-code… so it will take some time)On 19 Nov 2018, at 09:30, Manuel Leuenberger  wrote:Hi,I am currently playing with MetaLinks in Pharo 7 and stumbled upon some issues. For example, I found that instrumenting message sends may break compilation (see https://pharo.fogbugz.com/f/cases/22681/Metalink-on-message-may-break-compilation). Two other issues also arised:i) How do I reify the value of an RB(Valuel|Literal|LiteralValue)Node? RFValueReification does not work, and there is no reification for literal, value, or literal value nodes.ii) How do I reify arguments and results of blocks? I tried reify context for the block body #before and value for #after block "last", but I often run into the problem of no reification for literals.iii) How are cascaded message sends reified? Am I supposed to instrument the cascade node or the individual message sends?I am grateful for any pointers towards a solution. BTW, Marcus' lecture slides give a great intro to metalinks (http://marcusdenker.de/talks/18LectureMetaLinks/MetaLinks.pdf).Cheers,Manuel