Re: [Pharo-users] #ast vs. #parseTree

2018-05-04 Thread aglynn42
Just as TLA is a three letter acronym ... 

-Original Message-
From: Pharo-users  On Behalf Of Esteban A. 
Maringolo
Sent: Friday, May 4, 2018 2:21 PM
To: Any question about pharo is welcome ; Richard 
Sargent 
Subject: Re: [Pharo-users] #ast vs. #parseTree


On 04/05/2018 13:54, Richard Sargent wrote:

>> On Fri, May 4, 2018 at 9:45 AM, Sean P. DeNigris 
>> > wrote:
>> 
>> Ramon Leon-5 wrote
>> > And my point made; I don't even know what that means.
>> 
>> Ha ha, I googled it and even after seeing the definition still didn't
>> understand - we must be getting old ;-)

> Also, if one Googles an acronym, such as the recently cited TMA, one 
> gets results like https://en.wikipedia.org/wiki/TMA (a disambiguation 
> page with a lengthy list). [I still don't know which TMA was meant, by 
> the way, so I can't use it for the following example.] If one Googles 
> Abstract Syntax Tree, one will find exactly what it means. But 
> additionally, one could make a reasonable guess at an approximation of 
> its meaning even without searching.


I think that the "we have a TMA situation" is a nice joke if the right guess is 
that TMA means "Too Many Acronyms" :)

Regards!



--
Esteban A. Maringolo





[Pharo-users] Pharo developers wanted in Toronto

2018-05-04 Thread aglynn42
Telna is looking for developers with Smalltalk experience, preferably Pharo,  
in Toronto Canada.

The role is listed on indeed.ca if anyone is interested.

Andrew Glynn




Re: [Pharo-users] Where do we go now ?

2018-04-13 Thread aglynn42
Btw, in my fascination with messing around, the 32 bit version of Pharo 7 for 
Windows runs better on OS/2 v.5 (yes, it still exists, it was released last 
June).  Probably because its Win32 subsystem is more compatible with Win32 apps 
than Windows 10.

 

Andrew

 

From: Benoit St-Jean  
Sent: Friday, April 13, 2018 5:26 AM
To: Esteban Lorenzano 
Cc: Any question about pharo is welcome 
Subject: Re: [Pharo-users] Where do we go now ?

 

BTW, why put an .exe installer for Windows available when it crashes right from 
the start? It just doesn't work at all.  Period.  For everyone.

 

And I thought looking for senders of a method was something we mastered a long 
time ago, like starting with Smalltalk-76.  Am I supposed to assume that 
everything, even basic functionalities, are all broken because it's labeled 
"alpha" ?

 

 

- 
Benoît St-Jean 
Yahoo! Messenger: bstjean 
Twitter: @BenLeChialeux 
Pinterest: benoitstjean 
Instagram: Chef_Benito
IRC: lamneth 
Blogue: endormitoire.wordpress.com 
"A standpoint is an intellectual horizon of radius zero".  (A. Einstein)

 

 

On Friday, April 13, 2018, 5:20:28 a.m. EDT, Esteban Lorenzano 
 > wrote: 

 

 

 





On 13 Apr 2018, at 11:07, Benoit St-Jean  > wrote:

 

I'm on Windows 10, using Pharo 7.0 alpha 32 bit.

 

 

and btw… which part of ALPHA you do not get?

 

Esteban



Re: [Pharo-users] Where do we go now ?

2018-04-13 Thread aglynn42
Maybe I’m missing something, or maybe I’m not ‘everyone’, but I’ve only had a 
few problems with 32 bit Pharo 7 and Windows.  Btw Windows 10 “64 bit” is about 
as 64 bit as Windows 95 was 32 bit.  i.e. not very.  Most of the issues center 
around Moose, not the core Pharo.  But I’m only playing with Pharo 7, mainly on 
Linux where the latest image seems pretty stable.  My actual development is 
still on 61 (and in one case, 5.0 since it requires the old FFI).

 

M$ is supposed to fix the remains of 32 bit Windows next year, but we all know 
what ‘next year’ means to Microsoft, it’s forever ‘next year’.

 

As far as I understood, most of the development of Pharo 7 is focused on the 64 
bit version in any case.  What’s missing from 61 that you absolutely have to 
have ATM?  

 

Andrew

 

 

 

From: Benoit St-Jean  
Sent: Friday, April 13, 2018 5:26 AM
To: Esteban Lorenzano 
Cc: Any question about pharo is welcome 
Subject: Re: [Pharo-users] Where do we go now ?

 

BTW, why put an .exe installer for Windows available when it crashes right from 
the start? It just doesn't work at all.  Period.  For everyone.

 

And I thought looking for senders of a method was something we mastered a long 
time ago, like starting with Smalltalk-76.  Am I supposed to assume that 
everything, even basic functionalities, are all broken because it's labeled 
"alpha" ?

 

 

- 
Benoît St-Jean 
Yahoo! Messenger: bstjean 
Twitter: @BenLeChialeux 
Pinterest: benoitstjean 
Instagram: Chef_Benito
IRC: lamneth 
Blogue: endormitoire.wordpress.com 
"A standpoint is an intellectual horizon of radius zero".  (A. Einstein)

 

 

On Friday, April 13, 2018, 5:20:28 a.m. EDT, Esteban Lorenzano 
 > wrote: 

 

 

 





On 13 Apr 2018, at 11:07, Benoit St-Jean  > wrote:

 

I'm on Windows 10, using Pharo 7.0 alpha 32 bit.

 

 

and btw… which part of ALPHA you do not get?

 

Esteban



Re: [Pharo-users] Keeping packages up to date

2018-04-01 Thread aglynn42
You can open the repository in the Monticello browser if it’s a 
Metacello/Monticello repo, or use Iceberg with git if it’s a git repo in the 
same manner you would with any other git project.  You can also open the 
project in Versionner to get the latest version.

 

As far as scripting it, that’s reasonably obvious if you look at the Monticello 
or Versionner code itself.

 

From: Pharo-users  On Behalf Of Andrei 
Stebakov
Sent: Saturday, March 31, 2018 7:14 PM
To: Any question about pharo is welcome 
Subject: [Pharo-users] Keeping packages up to date

 

I wonder if there is a generic solution to keeping certain Pharo project in 
sync with development tree.

For example when I want to get latest Roassal I execute

Gofer it

smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';

package: 'Roassal2';

package: 'Roassal2GT';

package: 'Trachel';

load.

 

Also I wouldn't know this unless the maintainers (thanks Alexandre!) of the 
project told me what script to execute to get the latest version.

If I went to Project Catalog I can only get the stable version and if I go and 
find Roassal2 it won't give me information how to get its latest version.

 

How would I get info about how to update, say Roassal given the script above 
from some Roassal project public page?

Talking about Roassal, if I go to 
http://smalltalkhub.com/#!/~ObjectProfile/Roassal2/ page, it offers the 
following script:

Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; 
configurationOf: 'Roassal2'; loadDevelopment 

 

Which is probably not exactly equal to the script above (or is it?).

 

So, is there a generic way to get a latest version of some XYZ package? 

What do I need to learn to be able to get that information about any Pharo 
project (other than asking the community)? Something similar to "git pull" when 
you know the repository.



[Pharo-users] Porting to Solaris 11

2016-06-02 Thread aglynn42
I'm currently porting the Pharo VM to Solaris 11 for a specific project
(Sparc and x86).  I was wondering how many users prefer the stack VM, as for
my own purposes the JIT is better (better concurrency when not using OS
functions on a 128 thread machine, which is the deployment target).  However
since it wouldn't be that much extra work to port the stack VM, if there is
interest I will do that as well.thanksAndrew Glynn



--
View this message in context: 
http://forum.world.st/Porting-to-Solaris-11-tp4898818.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.