September 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Many problems with Iceberg :-(

by Norbert Hartl

I really like this to work. I'm not sure my reports are useful at all. If I should report detailed stuff or should try something just drop me a note. thanks for making iceberg. Until now I've seen just the tip of it ;) Norbert > Am 23.09.2016 um 10:57 schrieb Nicolas Passerini <npasserini(a)gmail.com>: > > Thanks, Norbert. > > On Fri, Sep 23, 2016 at 10:46 AM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > No, > > I unloaded the code and reloaded the development version. My error is slightly different. I use a repository that is having a filetree repository (or gitfiletree) and that I try to open with iceberg > > Norbert > > > <Bildschirmfoto 2016-09-23 um 10.43.46.png> >> Am 23.09.2016 um 00:07 schrieb Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>>: >> >> Hi! >> >> I am facing several bugs using Iceberg. >> Am I the only one? >> >> <Screen Shot 2016-09-22 at 7.06.08 PM.png> >> <Screen Shot 2016-09-22 at 7.06.18 PM.png> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> > >

Sept. 23, 2016

Re: [Pharo-dev] Many problems with Iceberg :-(

by Nicolas Passerini

Thanks, Norbert. On Fri, Sep 23, 2016 at 10:46 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > No, > > I unloaded the code and reloaded the development version. My error is > slightly different. I use a repository that is having a filetree repository > (or gitfiletree) and that I try to open with iceberg > > Norbert > > > > Am 23.09.2016 um 00:07 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: > > Hi! > > I am facing several bugs using Iceberg. > Am I the only one? > > <Screen Shot 2016-09-22 at 7.06.08 PM.png> > <Screen Shot 2016-09-22 at 7.06.18 PM.png> > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Sept. 23, 2016

Re: [Pharo-dev] Many problems with Iceberg :-(

by Norbert Hartl

No, I unloaded the code and reloaded the development version. My error is slightly different. I use a repository that is having a filetree repository (or gitfiletree) and that I try to open with iceberg Norbert > Am 23.09.2016 um 00:07 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: > > Hi! > > I am facing several bugs using Iceberg. > Am I the only one? > > <Screen Shot 2016-09-22 at 7.06.08 PM.png> > <Screen Shot 2016-09-22 at 7.06.18 PM.png> > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Sept. 23, 2016

Re: [Pharo-dev] C Variadic Functions via UFFI?

by Esteban Lorenzano

along with what Andres says, also no, you do not have support for variadic functions. what you do this is to declare your functions as if they were non-variadic: pritnf: format intValue: number self ffiCall: #(int printf(String format, int number)) that will workâ¦ yes is not the best in the word, but it works :) Esteban > On 23 Sep 2016, at 08:11, Andres Valloud <avalloud(a)smalltalk.comcastbiz.net> wrote: > > I wouldn't do that if I were you. The manual says fcntl() can be a macro, and you can't call a macro from an FFI. > > http://pubs.opengroup.org/onlinepubs/009695399/basedefs/fcntl.h.html > > On 9/22/16 15:12 , Mariano Martinez Peck wrote: >> Hi guys, >> >> I am wondering if I can wrap some variadic functions (with optional >> arguments) with UFFI. Is this possible? If true, how so? For my >> particular use case, I am checking if I can call fcntl() >> which has a third optional argument. >> >> Thanks in advance, >> >> -- >> Mariano >> http://marianopeck.wordpress.com >

Sept. 23, 2016

Re: [Pharo-dev] Many problems with Iceberg :-(

by Nicolas Passerini

Hi Alex, I'm sorry I missed your last message on Slack. Yes, current "stable" version (v0.2.1) has a bug, that I decided not to fix because I am about to release v0.3. The new version is quite stable and a lot faster, so maybe you will like to give it a test before the release (that should be in a few days anyway. It seems that you have loaded code from Monticello but at the same time you have the same packages in an Iceberg repository. Am I right? If that is the case, I have to say we do not support exactly that usage pattern. Sorry, for that, I will work on supporting it. In the meanwhile, you have a few workarounds: 1) If your code is already in a git repository (I guess it is the case given your error), then loading it in a clean image should not pose any problems. 2) Or if you loaded from github using metacello it should also work (I would say it should work also for code loaded from gitfiletree but Norbert reported a problem with it, which I am not being able to reproduce.) 3) Otherwise, if your code is only in monticello, then saving it to a clean Iceberg repository should work also. In any case, do not hesitate comming to me with any question or problem, I will try to help you. (But take into account the different time zones.) Cheers, Nico On Fri, Sep 23, 2016 at 5:36 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Please use the development version of Iceberg. It should be fixed there. > > Metacello new > baseline: 'Iceberg'; > repository: 'github://npasserini/iceberg'; > load. > > Cheers, > Doru > > > > On Sep 23, 2016, at 12:07 AM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > > Hi! > > > > I am facing several bugs using Iceberg. > > Am I the only one? > > > > <Screen Shot 2016-09-22 at 7.06.08 PM.png> > > <Screen Shot 2016-09-22 at 7.06.18 PM.png> > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > "Every thing has its own flow." > > > > > > >

Sept. 23, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] d3c4dd: 60236

by Tudor Girba

Great addition! Doru > On Sep 23, 2016, at 8:25 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> >> 19124 enhance Deprecation to log sending method >> https://pharo.fogbugz.com/f/cases/19124 > > > The result of this is that now the log on the CI now exactly tells us what to fix: > (I will add issue tracker entries for each): > > *** Warning: Deprecation: The method GTSpotter>>isEmpty called from GTSpotterTest>>#testNewSpotter has been deprecated. > Use hasSteps instead > > *** Warning: Deprecation: The method Object>>name called from KMRepository>>#addCategory: has been deprecated. > Implement your own domain representation of an object, or use #asString or #printString instead. > > *** Warning: Deprecation: The method Object>>name called from ClassHierarchyTest>>#testSubclasses has been deprecated. > Implement your own domain representation of an object, or use #asString or #printString instead. > > *** Warning: Deprecation: The method Object>>name called from BooleanSlot>>#layoutChanged: has been deprecated. > Implement your own domain representation of an object, or use #asString or #printString instead. > > *** Warning: Deprecation: The method Object>>name called from GlobalVariableTest>>#testSmalltalkNotDoubleSymbol has been deprecated. > Implement your own domain representation of an object, or use #asString or #printString instead. > > *** Warning: Deprecation: The method Object>>name called from PropertySlot>>#layoutChanged: has been deprecated. > Implement your own domain representation of an object, or use #asString or #printString instead. > > *** Warning: Deprecation: The method Object>>name called from UnlimitedInstanceVariableSlot>>#layoutChanged: has been deprecated. > Implement your own domain representation of an object, or use #asString or #printString instead. > > *** Warning: Deprecation: The method Object>>name called from ChangeSet>>#changeRecorderFor: has been deprecated. > Implement your own domain representation of an object, or use #asString or #printString instead. > > -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."

Sept. 23, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] d3c4dd: 60236

by Marcus Denker

> > 19124 enhance Deprecation to log sending method > https://pharo.fogbugz.com/f/cases/19124 The result of this is that now the log on the CI now exactly tells us what to fix: (I will add issue tracker entries for each): *** Warning: Deprecation: The method GTSpotter>>isEmpty called from GTSpotterTest>>#testNewSpotter has been deprecated. Use hasSteps instead *** Warning: Deprecation: The method Object>>name called from KMRepository>>#addCategory: has been deprecated. Implement your own domain representation of an object, or use #asString or #printString instead. *** Warning: Deprecation: The method Object>>name called from ClassHierarchyTest>>#testSubclasses has been deprecated. Implement your own domain representation of an object, or use #asString or #printString instead. *** Warning: Deprecation: The method Object>>name called from BooleanSlot>>#layoutChanged: has been deprecated. Implement your own domain representation of an object, or use #asString or #printString instead. *** Warning: Deprecation: The method Object>>name called from GlobalVariableTest>>#testSmalltalkNotDoubleSymbol has been deprecated. Implement your own domain representation of an object, or use #asString or #printString instead. *** Warning: Deprecation: The method Object>>name called from PropertySlot>>#layoutChanged: has been deprecated. Implement your own domain representation of an object, or use #asString or #printString instead. *** Warning: Deprecation: The method Object>>name called from UnlimitedInstanceVariableSlot>>#layoutChanged: has been deprecated. Implement your own domain representation of an object, or use #asString or #printString instead. *** Warning: Deprecation: The method Object>>name called from ChangeSet>>#changeRecorderFor: has been deprecated. Implement your own domain representation of an object, or use #asString or #printString instead.

Sept. 23, 2016

Re: [Pharo-dev] C Variadic Functions via UFFI?

by Andres Valloud

I wouldn't do that if I were you. The manual says fcntl() can be a macro, and you can't call a macro from an FFI. http://pubs.opengroup.org/onlinepubs/009695399/basedefs/fcntl.h.html On 9/22/16 15:12 , Mariano Martinez Peck wrote: > Hi guys, > > I am wondering if I can wrap some variadic functions (with optional > arguments) with UFFI. Is this possible? If true, how so? For my > particular use case, I am checking if I can call fcntl() > which has a third optional argument. > > Thanks in advance, > > -- > Mariano > http://marianopeck.wordpress.com

Sept. 23, 2016

Re: [Pharo-dev] Many problems with Iceberg :-(

by Tudor Girba

Hi, Please use the development version of Iceberg. It should be fixed there. Metacello new baseline: 'Iceberg'; repository: 'github://npasserini/iceberg'; load. Cheers, Doru > On Sep 23, 2016, at 12:07 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi! > > I am facing several bugs using Iceberg. > Am I the only one? > > <Screen Shot 2016-09-22 at 7.06.08 PM.png> > <Screen Shot 2016-09-22 at 7.06.18 PM.png> > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > -- www.tudorgirba.com www.feenk.com "Every thing has its own flow."

Sept. 23, 2016

C Variadic Functions via UFFI?

by Mariano Martinez Peck

Hi guys, I am wondering if I can wrap some variadic functions (with optional arguments) with UFFI. Is this possible? If true, how so? For my particular use case, I am checking if I can call fcntl() which has a third optional argument. Thanks in advance, -- Mariano http://marianopeck.wordpress.com

Sept. 22, 2016