[Pharo-users] In Praise of the Very Best Programming Language

[horrido]

My farewell article? 
https://medium.com/@richardeng/in-praise-of-the-very-best-programming-language-eae36ae434af

  



--
View this message in context: 
http://forum.world.st/In-Praise-of-the-Very-Best-Programming-Language-tp4955487.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Little challenge: Best way to read stream and count line returns

[Julián Maestri]

count := 0.
stream do: [ :character | (character = Character cr and: [stream peek =
Character lf]) ifTrue: [  count := count + 1 ]].
count.

Snippet with example:

| count crlftext stream |
stream := (String
streamContents: [ :s |
s
nextPutAll: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit.';
crlf;
nextPutAll: 'Phasellus sollicitudin lorem ac nunc varius aliquam.';
crlf;
nextPutAll: 'Quisque posuere augue in quam suscipit eleifend.';
crlf;
nextPutAll: 'Donec non tempor ex.';
crlf;
nextPutAll: 'Phasellus placerat leo augue, eu placerat augue luctus quis. ';
crlf;
lf;
cr;
cr ]) readStream.
count := 0.
stream
do: [ :char |
(char = Character cr and: [ stream peek = Character lf ])
ifTrue: [ count := count + 1 ] ].
count

On 13 July 2017 at 09:31, Cyril Ferlicot  wrote:

> Hello everyone,
>
> I often needs to read some streams these days and to get some infos
> related to the lines returns for example.
> Because of the CRLF it is a little complicated sometimes.
>
> I have an example of code here:
>
> | lfShouldBeCounted char count remaining |
> lfShouldBeCounted := false.
> remaining := 0.
> count := 0.
> stream position: startPos.
> [ stream position = endPos ]
>   whileFalse: [
> "13 is a CR, 10 a LF"
> (char := stream next asInteger) = 13
>   ifTrue: [ count := count + 1. remaining := 0. lfShouldBeCounted :=
> false ]
>   ifFalse: [
> char = 10
>   ifTrue: [
> lfShouldBeCounted
>   ifTrue: [ count := count + 1. remaining := 0 ]
>   ifFalse: [ lfShouldBeCounted := true ] ]
>   ifFalse: [ remaining := remaining + 1 ] ] ]
>
> With this example I know how many lines where passed between the
> startPos and the endPos in a stream. I also know how many char there
> is between the last line return and the endPos.
>
>  I wanted to know if you had a better way to do that? The way need to
> be as performant than this snippet. I know some people here can
> produce a snippet more readable and easier to maintain :)
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France
>
>

Re: [Pharo-users] Pharo 6.0 don't start

[Trussardi Dario Romano]

Ciao,


> Nothing there jumps out at me, so just a general question... what other 
> versions of Pharo have you successfully run on your system?

I have run:

Pharo4.0  Launcher Latest update: #40621

Pharo 4.0   Latest update: #40625

Pharo 5.0 Latest update: #50763
> 
> 
> Also, OSX 10.7.5 (September 19, 2012) is considered old (no longer support by 
> Apple)... 
>
> http://www.computerworld.com/article/2950580/operating-systems/the-end-is-near-for-os-x-mountain-lion-support.html
> so perhaps that could be related.  

It could be ?? !


Thanks,

Dario
> 
> cheers -ben
> 
> On Tue, Jul 11, 2017 at 11:08 PM, Trussardi Dario Romano 
>  wrote:
> Ciao,
> 
>   I'm interested to understund how git support work in Pharo.
> 
>   i download and unzip Pharo 6.0 from  
> http://files.pharo.org/platform/Pharo6.0-mac.zip
> 
>   Now when i open the application on the desktop the system open a dialog 
> with : Pharo 6.0 it closed unexpectedly.
> 
> 
>   The relative information are:
> 
>> Process: launchd [75184]
>> Path:/Users/USER/Desktop/Pharo6.0.app/Contents/MacOS/Pharo
>> 
>> Identifier:  org.pharo.Pharo
>> 
>> Version: ??? (???)
>> 
>> Code Type:   X86 (Native)
>> 
>> Parent Process:  launchd [178]
>> 
>>  
>> 
>> Date/Time:   2017-07-11 16:40:23.605 +0200
>> 
>> OS Version:  Mac OS X 10.7.5 (11G63b)
>> 
>> Report Version:  9
>> 
>>  
>> 
>> Interval Since Last Report:  33830084 sec
>> 
>> Crashes Since Last Report:   465
>> 
>> Per-App Crashes Since Last Report:   30
>> 
>> Anonymous UUID:  E84D2E1F-939E-4486-AF79-68ABE2A5AAB9
>> 
>>  
>> 
>> Crashed Thread:  Unknown
>> 
>> Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
>> 
>> Exception Codes: KERN_INVALID_ADDRESS at 0x8fe01030
>> 
>> Backtrace not available
>> 
>> Unknown thread crashed with X86 Thread State (32-bit):
>> 
>> eax: 0x  ebx: 0x  ecx: 0x  edx: 0x 
>> 
>> edi: 0x  esi: 0x  ebp: 0x  esp: 0x
>> 
>> ss: 0x0023  efl: 0x00010202  eip: 0x8fe01030   cs: 0x001b
>>   
>> ds: 0x0023   es: 0x0023   fs: 0x   gs: 0x
>>  
>> cr2: 0x8fe01030
>> Logical CPU: 0
>> 
>> Binary images description not available
>> 
>> External Modification Summary: 
>> 
>> Calls made by other processes targeting this process:
>>
>> task_for_pid: 1
>>
>> thread_create: 0
>>
>> thread_set_state: 0
>>  
>> Calls made by this process:
>>
>> task_for_pid: 0
>>
>> thread_create: 0
>>
>> thread_set_state: 0
>>  
>> Calls made by all processes on this machine:
>>
>> task_for_pid: 140939
>>
>> thread_create: 0
>> 
>> thread_set_state: 0 
>> Model: MacBookPro5,2, BootROM MBP52.008E.B05, 2 processors, Intel Core 2 
>> Duo, 2.8 GHz, 8 GB, SMC 1.42f4
>> 
>> Graphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 512 MB
>> 
>> Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
>> 
>> Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x830B, 
>> 0x4D3253344736344342384847354E2D424520
>> 
>> Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x830B, 
>> 0x4D3253344736344342384847354E2D424520
>> 
>> AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), 
>> Broadcom BCM43xx 1.0 (5.106.198.19.22)
>> 
>> Bluetooth: Version 4.0.8f17, 2 service, 11 devices, 3 incoming serial ports
>> 
>> Network Service: Ethernet, Ethernet, en0
>> 
>> Network Service: AirPort, AirPort, en1
>> 
>> Serial ATA Device: Hitachi HTS545050B9SA02, 500,11 GB
>> 
>> Serial ATA Device: HL-DT-ST DVDRW  GS21N
>> 
>> USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x2440 / 2
>> 
>> USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0237, 
>> 0x0460 / 3
>> 
>> USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x0450 / 2
>> 
>>  USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 
>> 0x4500, 0x0610 / 2
>> 
>>  USB Device: Bluetooth USB Host Controller, 
>> apple_vendor_id, 0x8217, 0x0611 / 5
>> 
>  Thanks for considerations,
> 
> 
>   Dario
> 

Re: [Pharo-users] How to run a window in full-screen mode?

[Luke Gorrie]

On 17 July 2017 at 16:02, Nicolai Hess  wrote:

> There is a FullscreenMorph
>

Thanks, Nicolai! That's exactly what I need.

I wonder how I missed it in the Spotter :).

Re: [Pharo-users] How to run a window in full-screen mode?

[Nicolai Hess]

2017-07-17 15:50 GMT+02:00 Luke Gorrie :

> Hoi!
>
> I am looking for a way to run a window in full-screen mode in Pharo. That
> is it should maximize, beyond the bounds that the expand button usually
> takes, and it should automatically resize when the world does.
>
> I'm thinking of the GTInspector but a custom class would be fine too.
>
> Is there a simple solution?
>
> On Discord I got a partial solution:
>
> window := GTInspector openOn: self.
> window
>   removeBoxes;
>   beSticky;
>   bounds: window world clearArea.
>
> but the main problem here is that it doesn't resize when the world does.
>
> I wonder if it would make more sense to avoid the SystemWindow and embed
> the inspector directly in the World somehow...?
>
> Cheers!
> -Luke
>
>
There is a FullscreenMorph

see for example
StandardWindow>>#openFullscreen

[Pharo-users] How to run a window in full-screen mode?

[Luke Gorrie]

Hoi!

I am looking for a way to run a window in full-screen mode in Pharo. That
is it should maximize, beyond the bounds that the expand button usually
takes, and it should automatically resize when the world does.

I'm thinking of the GTInspector but a custom class would be fine too.

Is there a simple solution?

On Discord I got a partial solution:

window := GTInspector openOn: self.
window
  removeBoxes;
  beSticky;
  bounds: window world clearArea.

but the main problem here is that it doesn't resize when the world does.

I wonder if it would make more sense to avoid the SystemWindow and embed
the inspector directly in the World somehow...?

Cheers!
-Luke

Re: [Pharo-users] Using the Debugger to write code

[Marcus Denker]

>>> 
>>> 2017-07-12 9:09 GMT+02:00 Marcus Denker >> >:
>>> in the workspace it creates a variable (with value nil)… so it treats 
>>> upper-case
>>> unknown vars the same as lower case.
>>> 
>>> I think it might make sense to have for upper case instead the menu that 
>>> asks
>>> what to do (it could there have a “add binding to workspace” entry for the 
>>> current
>>> way, too)
>>> 
>>> I would prefer same behaviour like in method editor. I really hate when I 
>>> made mistake in class name and after evaluation I got uppercase binding 
>>> with nil value. 
>> 
>> yes, we should fix it. binding should just be created for lower case vars.
>> 
> 
> How to fix it:
> 
> OCRequestorScope is the scope of variables in tools. #lookupVar: is the 
> method that is doing the lookup.
> 
> replace the code
> 
> global := self lookupGlobalVar: name.
> global ifNotNil: [ ^ global ].  
> 
> with:
> 
> name first isUppercase ifTrue: [ ^ outerScope lookupVar: name].
> 
> But: right now we abuse the requesterscope to implement the feature that you 
> can hand
> in an additional dictionary with bindings. See 
> testEvaluateWithBindingsWithUppercaseName
> This change breaks this feature… but it just means we need to implement this 
> better, which 
> I will do .
> 
For Pharo6:

https://pharo.fogbugz.com/f/cases/20254/Playground-should-ask-to-create-class-for-non-Existing-Globals
 


This adds a scope for additional bindings and uses this for the bindings, which 
then allows us to change
the requestorscope as needed.

Marcus

Re: [Pharo-users] Creating the smallest server runtime footprint

[Tim Mackinnon]

Well I’ve been shooting in the dark a bit - but I also left out the sound and 
display so’s (e.g. -x execlude the following and add back the null so's

zip -r --symlinks ../deploy/$LAMBDA_NAME.zip * -x pharo-local/\* \*.sources 
\*.changes \*.st \*.log
*/libgit2.* */libSDL2* */B3DAccelerator* */JPEGRead* */vm-sound* 
*/vm-display* tmp/\* */__MACOSX\*
- zip -uR ../deploy/$LAMBDA_NAME.zip *-null.so

And everything seems to run clean. (Would be useful to get some feedback from 
those in the know - does just leaving out so’s incurred a penalty if you don’t 
recompile the VM? Presumably something would get written to std error or 
pharodebug if it was an issue).

In fact my run times on EC2 are pretty impressive:

PharoLambdaMin]$ time ./pharo Pharo.image exec "Lambda processJSON: '{}'"
{"outputSpeech":{"text":"Good Morning, it's eleven 
twenty-six","type":"PlainText"},"shouldEndSession":true,"card":{"content":"Operation
 Successful","title":"Pharo Lambda","type":"Simple"}}

real0m0.039s
user0m0.028s
sys 0m0.000s
[ec2-user@ip-172-31-44-73 PharoLambdaMin]$ time ./pharo Pharo.image exec 
"Lambda processJSON: '{}'"
{"outputSpeech":{"text":"Good Morning, it's eleven 
twenty-six","type":"PlainText"},"shouldEndSession":true,"card":{"content":"Operation
 Successful","title":"Pharo Lambda","type":"Simple"}}

real0m0.039s
user0m0.020s
sys 0m0.008s


Not bad eh?

Tim

> On 17 Jul 2017, at 07:00, Tim Mackinnon  wrote:
> 
> Thanks again Pavel - I'll try the 6.0 step 4 or possibly step 5 with sunit 
> (as many libraries don't separate out their tests).
> 
> I've also tried leaving out libgit and libsdl2 .so's on my server build  and 
> that seems fine too - making me wonder what others I can safely leave out? 
> Sound is a candidate (but small fry in size but do you need the null 
> variant?).
> 
> Libcrypto is big - but I wonder if https routines would use that (and it 
> sounds server processing'y so maybe best left).
> 
> I was hoping to find a list explaining them somewhere - but it remains rather 
> mysterious.
> 
> However, at this point, I think I may have hit the sweet spot in size where 
> AWS seems to load efficiently below a zip of 10mb?
> 
> Tim
> 
> Sent from my iPhone
> 
> On 15 Jul 2017, at 09:35, Pavel Krivanek  > wrote:
> 
>> If you want to stay with Pharo 6 image, you can try the bootstrapped version 
>> of the minimal image:
>> https://ci.inria.fr/pharo/view/6.0-SysConf/job/Pharo-6.0-Step-04-01-ConfigurationOfMinimalPharo/
>>  
>> 
>> 
>> -- Pavel
>> 
>> 2017-07-15 10:33 GMT+02:00 Pavel Krivanek > >:
>> Try the Pharo 7 metacello image (=Pharo 7 minimal image that the CI is 
>> already converting to 64bit). There should be no problem with STON because 
>> whole Pharo is loaded into it using metacello and filetree. Pharo 6 minimal 
>> image is done differently (by shrinking) and not so well tested.
>> 
>> For the conversion of 32-bit image to 64-bit image you need a VMMaker image:
>> https://ci.inria.fr/pharo/job/Spur-Git-Tracker/lastSuccessfulBuild/artifact/vmmaker-image.zip
>>  
>> 
>> and then evaluate:
>> ./pharo generator.image eval "[Spur32to64BitBootstrap new bootstrapImage: 
>> 'conversion.image'] on: AssertionFailure do: [ :fail | fail resumeUnchecked: 
>> nil ]"
>> 
>> -- Pavel
>> 
>> 
>> 
>> 2017-07-15 10:19 GMT+02:00 Tim Mackinnon > >:
>> Hi Pavel - thanks for getting me to the point where I could even have a 
>> minimal image. As I’m on the edge of my Pharo knowledge here, I’ll try and 
>> run with this as best I can.
>> 
>> I’d been using the 6.0 image you suggested to me - but maybe I could use a 
>> 70 image with Pharo 6 for a while (until the VM diverges) right? 
>> 
>> The bit I haven’t quite understood however, is how the 64bit image is 
>> created - as your reference is to a 32bit version? Is the 64bit one 
>> converted from 32 in a later stage? (For AWS Lambda I need 64bit) - am I 
>> right in thinking the pipeline stage after this one is the one you sent me - 
>> and the travis.yml file shows me what it does? But I can’t see a trivis.yml 
>> in the conversion stage so I’m not sure how it does that. (Question - how do 
>> I see what the pipelines do to answer my own questions?)
>> 
>> I was hoping that there was a basic image that got me up to metacello 
>> baseline level to load git file tree packages/baselines  in my own repo as 
>> well baselines on the internet. The one you sent me is fairly close to that 
>> (its just missing STON in the image and seems to have an issue with 
>> resolving undeclared classes that get loaded in - should do a fogbugz on 
>> that?)
>> 
>> The follow-on from a metacello image is how we can get people to create 
>> better baselines that give you mo

Re: [Pharo-users] Playground and Dr. Geo

[Hilaire]

The owner of the menu (DockingBarToogleMenuItemMorph) does not have the
right bounds. Therefore its #adjacentTo message returns the wrong
information.


Le 17/07/2017 à 10:50, Hilaire a écrit :
>> if b) The real morph position is probably not the same as where
>> clicked causing it to open at another place.
>>
> I guess so too.
>

-- 
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] Playground and Dr. Geo

[Hilaire]

Hi,


Le 16/07/2017 à 22:02, Henrik Nergaard a écrit :
>
> a)Do you wrap the morph inside the morph tab view? ,
>

I don't understand.

> b) Do you use the same code for rendering as in  Morph>>
> #gtInspectorMorphIn: .
>

No, as I want a Morph view and not a From:

gtInspectorCanvasIn: composite

| morphPresentation |
morphPresentation := composite morph.
morphPresentation
title: 'Morph';
display: [self view]

>
> if a) it is most likely caused by the morph being wrapped within one
> or more transform morphs, and the offset of these are not taken into
> account when opening the menu.
>
>
> if b) The real morph position is probably not the same as where
> clicked causing it to open at another place.
>
I guess so too.

> What method are you using for opening the menu: (#popUpEvent:in: ,
> #popUpAt:forHand:in: , other)?
>
The menu are opened with #popUpAdjacentTo:forHand:from:


Menu are instantiate as:

menuBar := self window newToolDockingBar.
menuBar
add: 'File' translated
font: self theme menuBarFont
icon: nil
help: 'Load, save or export Dr. Geo figure.' translated
subMenu: self fileMenu.



> also
> see: 
> https://pharo.fogbugz.com/f/cases/15927/Menu-is-broken-when-contained-in-a-scrollable-pane
>
>
Looks to be the same. But issue was closed so it should be ok, may be an
unrelated problem.


Hilaire

-- 
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] Mysterious problem in loading Pharo

[Peter Uhnak]

With fast boot I had experiences where the restart wasn't enough and I had to 
restart several times, but since I disabled fast boot restarting once was 
always enough... so usually the first thing I do when windows boots is to check 
if Pharo runs ok.

In some rare unclear circmustances (now I wonder whether it happened after 
sleep) it broke after some time... but that happened only two or three times in 
past ~6 months.

Also dual-booting increases the probability it seems... there were some 
correlated issues regarding time and network card, but nothing conclusive.

Peter


On Mon, Jul 17, 2017 at 12:01:55AM +0100, PBKResearch wrote:
> Peter
> 
> I think the implication of your second para is that your last resort, 
> re-booting the system, is always effective in fixing the problem. If so, 
> while it is obviously a nuisance I think I can live with that. I think I have 
> had this only once before - at least, I have seen the debug console in some 
> context. But yesterday it happened simultaneously on two separate machines. 
> So it all depends on how frequently it happens.
> 
> Peter Kenny
> 
> -Original Message-
> From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of 
> Peter Uhnak
> Sent: 16 July 2017 15:40
> To: Any question about pharo is welcome 
> Subject: Re: [Pharo-users] Mysterious problem in loading Pharo
> 
> I had this problem for several months (and still do), and so far I didn't 
> manage to figure out what is the actual cause.
> 
> Sometimes it fixes itself (close Pharo and open again), sometimes opening it 
> with different VM (and then reopen with the original) helps, and sometimes I 
> have to restart system.
> 
> After I disabled Windows Fast Boot it is somewhat more infrequent (or rather 
> it fixes itself without the need to restart).
> 
> But otherwise I might as well wave a magical wand. It is annoying but still 
> better than then spending countless hours digging randomly and aimlessly in 
> the VM ¯\_(ツ)_/¯.
> 
> Peter
> 
> 
> On Sat, Jul 15, 2017 at 10:38:51PM +0800, Ben Coman wrote:
> > Maybe revew recent Windows 10 updates...
> > http://www.sysprobs.com/how-to-view-installed-updates-on-windows-10-8-
> > 1-server-2012
> > 
> > cheers -ben
> > 
> > On Sat, Jul 15, 2017 at 6:26 PM, PBKResearch 
> > wrote:
> > 
> > > Hello
> > >
> > >
> > >
> > > I have a problem in loading Pharo images which, until yesterday, 
> > > loaded without difficulty. All the images showing the problem are 
> > > Pharo 6 with the Cog VM; older images do not seem to be affected.
> > >
> > >
> > >
> > > The first sign of a problem is that, as soon as I start the image, 
> > > the debug console appears, with several repeats of the message:
> > >
> > > LoadLibrary(FT2Plugin.dll) (998: Invalid access to memory location.)
> > >
> > > The other strange thing is that the appearance of some opened 
> > > windows has changed. Most obviously, the three icons at the top left 
> > > (close, minimise,
> > > expand) are very close together. Also, I think the print size has 
> > > got a bit smaller, though this is not obvious.
> > >
> > >
> > >
> > > I have recently reinstalled some components of Pharo and Moose, 
> > > trying to solve my problems with PunQLite, so I wondered if I had 
> > > fouled something up. To check, I made a completely new install of 
> > > Pharo 6 (#60508) from the Pharo download page in a separate folder. 
> > > When I start the image, both the strange things above are present, 
> > > plus a debug window with the message;
> > > ‘FT2 Error: Freetype2 primitive failed’.
> > >
> > >
> > >
> > > So it looks as though something has happened to my system which 
> > > means that any Pharo 6 image will show these oddities. The images I 
> > > have tried seem able to run some of my functions correctly, so it’s 
> > > all to do with appearance.
> > >
> > >
> > >
> > > I am running on Windows 10 with all recent updates. There was a 
> > > major update of Windows late yesterday, so it may be that the 
> > > problems appeared then. Does anyone have any suggestions?
> > >
> > >
> > >
> > > Many thanks
> > >
> > >
> > >
> > > Peter Kenny
> > >
> 
> 

Re: [Pharo-users] VoyageMongo with Metacello project spec in Pharo 6 on MacOS Sierra

[Esteban Lorenzano]

> On 16 Jul 2017, at 15:27, Guillaume Giraud  
> wrote:
> 
> Thanks a lot !
> 
> I used your config and now it works.
> 
> The result of evaluating 'Smalltalk os’ is 'a MacOSPlatform’, and the VM is 
> 201705310241.
> 
> By the way, I find it difficult to fully grasp the Metacello config process.
> I have read Deep into Pharo, but I can’t really understand why the 
> modification you suggested works.
> Are there other resources available on the subject ?

yeah, not really much… metacello is hard mostly because dependency management 
is hard. 
there are some few cases like this, however, that are mostly “accidental 
complexity” and is because of evolution of the tool.
this is the problem you were seeing: 

configurations (those who starts with “ConfigurationOf”) were made to match 
older monticello repositories. Then they define versions that points to 
specific package versions. 
baselines (those who starts with “BaselineOf”) are made to match git and “git 
like” repositories: there you do not need to define versions because the commit 
contains all the information you need. That’s defined in the url  
"github://pharo-nosql/voyage:1.5/mc ", 
where the “1.5” part points to the “1.5” release (which is just a git tag).

what happened in your project case is that you where downloading “master” 
version to load ConfigurationOfVoyageMongo which then was downloading another 
version of voyage (not master) which was then loading from another, incorrect 
release (1.4). So it was doing double work. Using directly “baseline:with:” 
prevents this because downloads just the version you want :)

in general, when in your projects, is recommended to use the “baseline form” 
when pointing to git based projects and to use configurations just for those 
that still resides on smalltalkhub or other of the monticello-based 
repositories.

hope this clarifies :P

cheers!
Esteban


> 
> Bye.
> 
>> Hi,
>> 
>>> On 15 Jul 2017, at 13:46, Guillaume Giraud 
>>> >> > wrote:
>>> 
>>> Hello,
>>> 
>>> I placed this code in a baseline of my package:
>>> 
>>> spec
>>> project: 'VoyageMongo'
>>> with: [ spec
>>> className: #ConfigurationOfVoyageMongo;
>>> version: #stable;
>>> repository: 'github://pharo-nosql/voyage/mc 
>>> ';
>>> loads: #('mongo tests') ].
>>> 
>>> Unfortunately, when I load my Package from Pharo6 on MacOS Sierra I get the 
>>> following error:
>>> 
>>> Error: Unsupported OS platform
>>> 
>>> The first lines of the stack are:
>>> 
>>> BaselineOfPunQLite(Object)  error:
>>> BaselineOfPunQLite  platformLibraryName
>>> BaselineOfPunQLite  preLoad
>>> MetacelloMCVersionpec(MetacelloSpec)doItBlock:
>>> 
>>> In detail:
>>> 
>>> platformLibraryName
>>> " Answer a name for the compiled version of the library "
>>> 
>>> Smalltalk os isUnix ifTrue: [ ^ 'unqlite.so' ].
>>> Smalltalk os isWin32ifTrue: [ ^ 'unqlite.dll' ].
>>> Smalltalk os isMacOSX   ifTrue: [ ^ 'unqlite.dylib' ].
>>> 
>>> self error: 'Unsupported OS platform?
>>> 
>>> With Pharo6 on MacOsSierra, ?  Smalltalk os isMacOSX ? return ? false ?. 
>>> But ?  Smalltalk os isMacOS ? return ? true ?.
>>> 
>>> What can I do? I just need to load Voyage with the configuration of my 
>>> package ?
>> 
>> you can just change the Smalltalk os isMacOSX line for Smalltalk os isMacOS 
>> for the moment. 
>> now, that?s very weird :)
>> What?s the result of evaluating "Smalltalk os? ?
>> and after executing "OSPlatform startUp: true.? ?
>> which VM are you using (Smalltalk vm version) ?
>> 
>> 
>> and btw, is a lot better to make your config as this: 
>> 
>> spec
>>  baseline: 'Voyage'
>>  with: [ 
>>  spec
>>  repository: 'github://pharo-nosql/voyage:1.5/mc 
>> ';
>>  loads: #('mongo tests') ].
>> 
>> (referring directly the baseline)
>> 
>> 
>> cheers!
>> Esteban
>> 
>>> Thanks.