Re: [Pharo-dev] Iceberg workflow

Hi Ben, On 29 November 2017 at 06:51, Ben Coman wrote: > On 29 November 2017 at 02:40, Torsten Bergmann wrote: >> Hi Ben, >> >> I think you forgot to give Iceberg the "src" subdirectory where all the code >> packages reside. > > Not such much forgot and

Re: [Pharo-dev] Iceberg workflow

On 29 November 2017 at 07:50, Sean P. DeNigris wrote: > Stephan Eggermont-3 wrote >>>2c) Code subdirectory: enter "src" here !!! >> Do we really need that? Why would I care about that? > > BTW in latest Iceberg this is automatically selected if it is one of the >

Re: [Pharo-dev] Iceberg workflow

On 29 November 2017 at 02:40, Torsten Bergmann wrote: > Hi Ben, > > I think you forgot to give Iceberg the "src" subdirectory where all the code > packages reside. Not such much forgot and not being aware of the impact of that field :P ;) > When you forget to give the "Code

[Pharo-dev] (no subject)

A minor thing, but a fix is probably easy... I have... FFIExternalStructure subclass: #CXSourceLocation instanceVariableNames: '' classVariableNames: 'VoidPointer2' package: 'Libclang' initialize "self initialize" VoidPointer2 := FFITypeArray ofType: 'void*' size: 2. fieldsDesc

Re: [Pharo-dev] I love the launcher!!!!

demarey wrote >> pre Pharo-5 image > It probably means that the command used to determine the image version > failed! Oh, are Pharo 4 and prior supposed to work? I figured they were just not intended to be supported - Cheers, Sean -- Sent from:

Re: [Pharo-dev] Iceberg workflow

Stephan Eggermont-3 wrote >>2c) Code subdirectory: enter "src" here !!! > Do we really need that? Why would I care about that? BTW in latest Iceberg this is automatically selected if it is one of the standard names (e.g. src, repository) - Cheers, Sean -- Sent from:

[Pharo-dev] [Pharo 7.0-dev] Build #346: 20777-Fix-instVarAt-instVarAt-put-comment

There is a new Pharo build available! The status of the build #346 was: FAILURE. The Pull Request #559 was integrated: "20777-Fix-instVarAt-instVarAt-put-comment" Pull request url: https://github.com/pharo-project/pharo/pull/559 Issue Url: https://pharo.fogbugz.com/f/cases/20777 Build

Re: [Pharo-dev] Iceberg workflow

You do not have to use "src" or "repository" - you can store your packages directly in the root if you like. You are free to choose. But over time it can "bloat" the topmost level of your project with the Smalltalk packages folders and it might get confusing the more packages you have or the

Re: [Pharo-dev] I love the launcher!!!!

On 28.11.2017 17:33, Christophe Demarey wrote: > Hi, > > >> Le 25 nov. 2017 à 21:45, Volkert a écrit : >> >> The PharoLauncher is really nice ... >> >> Is it possible to use a 64Bit VM run an Image (6.1 >)? Per default a >> 32bit VM is downloaded. > Yes, Pharo

Re: [Pharo-dev] FFIIntegerTypes inheritance hierarchy

> On 28 Nov 2017, at 16:25, Ben Coman wrote: > > I just bumped into... >FFUInt64>>basicHandle: aHandle at: index >^ aHandle signedLongLongAt: index that’s probably a bug :) Esteban > > and I'm curious why #unsignedLongLongAt: is not used. > Seems I had the

Re: [Pharo-dev] Iceberg workflow

On 28-11-17 19:40, Torsten Bergmann wrote: 2c) Code subdirectory: enter "src" here !!! Do we really need that? Why would I care about that? Stephan

Re: [Pharo-dev] I love the launcher!!!!

Hi, Launcher is a power tool and has helped many of us so far. Thanks to all who helped moving it forward, especially Christophe who is currently caring a lot. Unfortunately one primary issue is not yet solved: The downloadable files for Pharo 7 are not correctly displayed (see Screenshot

Re: [Pharo-dev] Iceberg workflow

Hi Ben, I think you forgot to give Iceberg the "src" subdirectory where all the code packages reside. When you forget to give the "Code subdirectory" in the dialog the repo points to the bencoman/libclang-pharo-bindings root which has no packages. Thats why the packages pane is empty. So I

Re: [Pharo-dev] Would it be possible to also launch templates in PharoLauncher?

On Tue, Nov 28, 2017 at 2:05 PM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Hi Mariano, > > > Le 27 nov. 2017 à 03:08, Mariano Martinez Peck > a écrit : > > > > Hi guys, > > > > Thank you Christophe for continue pushing this useful tool! > > > > One small

Re: [Pharo-dev] Would it be possible to also launch templates in PharoLauncher?

Hi Mariano, > Le 27 nov. 2017 à 03:08, Mariano Martinez Peck a > écrit : > > Hi guys, > > Thank you Christophe for continue pushing this useful tool! > > One small request which might be easy to do... Quite frequently I want to do > something and re-save an image I

Re: [Pharo-dev] I love the launcher!!!!

Hi, > Le 25 nov. 2017 à 21:45, Volkert a écrit : > > The PharoLauncher is really nice ... > > Is it possible to use a 64Bit VM run an Image (6.1 >)? Per default a > 32bit VM is downloaded. Yes, Pharo Launcher manages 32-bits and 64-bits VM.

Re: [Pharo-dev] I love the launcher!!!!

> Le 25 nov. 2017 à 20:08, Sean P. DeNigris a écrit : > > bpi wrote >> UndefinedObject(Object)>>doesNotUnderstand: #, >> PhLVirtualMachineManager>>vmFileName > > I usually get an error that looks like that when I try to launch a pre > Pharo-5 image. IIUC when Launcher is

Re: [Pharo-dev] I love the launcher!!!!

Hi Bernhard, > Le 25 nov. 2017 à 16:24, Bernhard Pieber a écrit : > > Hi Stef, > > I just found download links on this page: > https://github.com/pharo-project/pharo-launcher > They point to Jenkins build artefacts. > > Thank you for implementing the launcher. As a newbie

Re: [Pharo-dev] FFIIntegerTypes inheritance hierarchy

I just bumped into... FFUInt64>>basicHandle: aHandle at: index ^ aHandle signedLongLongAt: index and I'm curious why #unsignedLongLongAt: is not used. Seems I had the same question a year ago... On 1 September 2016 at 22:09, Ben Coman wrote: > I'm looking

[Pharo-dev] Iceberg workflow

I'm still struggling with Iceberg workflow for a personal repo. World menu > Iceberg Clicked Remote URL <-- g...@github.com:bencoman/libclang-pharo-bindings.git Clicked So now I have a new row... Name = libclang-pharo-bindings Current Branch = master Loaded version = No package loaded

[Pharo-dev] [Pharo 7.0-dev] Build #345: 20777-Fix-instVarAt-instVarAt-put-comment

There is a new Pharo build available! The status of the build #345 was: FAILURE. The Pull Request #559 was integrated: "20777-Fix-instVarAt-instVarAt-put-comment" Pull request url: https://github.com/pharo-project/pharo/pull/559 Issue Url: https://pharo.fogbugz.com/f/cases/20777 Build

[Pharo-dev] Iceberg "Create repository" buttons

In Iceberg I am finding the "Create repository" button disconcerting for some of the Iceberg repository dialogs. For example, clicking "Add local repository" shows a dialog "Import local repository into Iceberg" with a "Create repository" button and perception of this which I can't shake is

[Pharo-dev] [Pharo 7.0-dev] Build #344: 20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest, ...

There is a new Pharo build available! The status of the build #344 was: SUCCESS. The Pull Request #557 was integrated: "20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest,..." Pull request url: https://github.com/pharo-project/pharo/pull/557 Issue Url:

Re: [Pharo-dev] QA rule suggestion - assignment symbol slips

On 28 November 2017 at 16:25, Marcus Denker wrote: > as for catching message sends of the kind > > var = 1 + 2. > > (instead of :=), yes, we can add a rule for that. Cool. I added https://pharo.fogbugz.com/f/cases/20780 > >> On 28 Nov 2017, at 09:20, Marcus

Re: [Pharo-dev] clarifying pharo crashing issue(s)

2017-11-27 9:20 GMT+01:00 Tudor Girba : > Hi, > > There are recurrent reports that Pharo is crashing often. > > However, at the moment I believe the reasons are not clarified. So, this > mail is not about fixing the issues, but first about clarifying what they > are. > >

Re: [Pharo-dev] QA rule suggestion - assignment symbol slips

> > or > > messageSelectorAndArgumentNames > | t | > self init: t. > ^t > This one is good to warn… but we have the “unitialized var” rule for that already. Marcus

Re: [Pharo-dev] QA rule suggestion - assignment symbol slips

as for catching message sends of the kind var = 1 + 2. (instead of :=), yes, we can add a rule for that. > On 28 Nov 2017, at 09:20, Marcus Denker wrote: > > Hi, > > The "Temporaries read before written” rule is implemented very in a way that > you get > *a

Re: [Pharo-dev] QA rule suggestion - assignment symbol slips

Hi, The "Temporaries read before written” rule is implemented very in a way that you get *a lot* of false positives. e.g. it treats *any* block as potentially no exectuted, so any code like messageSelectorAndArgumentNames | t | self doSomething: [ t:=1 ]. ^t or