- Pharo-users - lists.pharo.org

Re: [Pharo-users] SmalltalkHub permission denied

by Ben Coman

On Tue, Jun 2, 2015 at 4:28 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > I have permission denied from Monticello when saving a package to > SmalltalkHub repo. > Do I miss something? Can you copy your repo definition (of course minus the password :) cheers -ben

June 2, 2015

Re: [Pharo-users] Pharo 4 Image Freeze

by Nicolai Hess

2015-06-01 23:44 GMT+02:00 Craig Johnson <craig(a)hivemind.net>: > Sure thing. > > To see the bug, file the code below into a clean image and run the > example. The when the debugger pops, step over each line in the method. > I'm doing this on a Windows OS. > > Object subclass: #Cooler > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'ImageFreeze'! > > !Cooler methodsFor: 'as yet unclassified' stamp: 'CraigJohnson 6/1/2015 > 23:31'! > runMe > | a | > self halt. > self except. > a := 1.! ! > > "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! > > Cooler class > instanceVariableNames: ''! > > !Cooler class methodsFor: 'as yet unclassified' stamp: 'CraigJohnson > 6/1/2015 23:16'! > example > self new runMe ! ! > > This worked until pharo 40245 -> it looks like phase4 in issue 11996 <https://pharo.fogbugz.com/default.asp?11996> Wrong exception handler problem introduced this behavior. > > > > On 2015/06/01 11:00 PM, Esteban Lorenzano wrote: > >> wellâ¦ pharo4 is not a beta :) >> weird that no one else reports same bugâ¦ can you give us a way to >> reproduce the problem? Instead telling you which image does not have a >> problem I was not aware, I would like more to give you a bugfix :) >> >> Esteban >> >> On 01 Jun 2015, at 22:31, Craig Johnson <craig(a)hivemind.net> wrote: >>> >>> >>> Hi All, >>> >>> I'm getting tired of Pharo 4 beta freezing. It happens whenever a >>> exception occurs while in the debugger. >>> >>> Funny that I don't remember any of the Pharo 4 development images >>> freezing. >>> >>> Which image can I use that won't do this? >>> >>> Craig >>> >>> >> > >

June 2, 2015

Re: [Pharo-users] Pharo 4 Image Freeze

by Craig Johnson

Sure thing. To see the bug, file the code below into a clean image and run the example. The when the debugger pops, step over each line in the method. I'm doing this on a Windows OS. Object subclass: #Cooler instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'ImageFreeze'! !Cooler methodsFor: 'as yet unclassified' stamp: 'CraigJohnson 6/1/2015 23:31'! runMe | a | self halt. self except. a := 1.! ! "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! Cooler class instanceVariableNames: ''! !Cooler class methodsFor: 'as yet unclassified' stamp: 'CraigJohnson 6/1/2015 23:16'! example self new runMe ! ! On 2015/06/01 11:00 PM, Esteban Lorenzano wrote: > wellâ¦ pharo4 is not a beta :) > weird that no one else reports same bugâ¦ can you give us a way to reproduce the problem? Instead telling you which image does not have a problem I was not aware, I would like more to give you a bugfix :) > > Esteban > >> On 01 Jun 2015, at 22:31, Craig Johnson <craig(a)hivemind.net> wrote: >> >> >> Hi All, >> >> I'm getting tired of Pharo 4 beta freezing. It happens whenever a exception occurs while in the debugger. >> >> Funny that I don't remember any of the Pharo 4 development images freezing. >> >> Which image can I use that won't do this? >> >> Craig >> >

June 1, 2015

Re: [Pharo-users] Pharo 4 Image Freeze

by Esteban Lorenzano

wellâ¦ pharo4 is not a beta :) weird that no one else reports same bugâ¦ can you give us a way to reproduce the problem? Instead telling you which image does not have a problem I was not aware, I would like more to give you a bugfix :) Esteban > On 01 Jun 2015, at 22:31, Craig Johnson <craig(a)hivemind.net> wrote: > > > Hi All, > > I'm getting tired of Pharo 4 beta freezing. It happens whenever a exception occurs while in the debugger. > > Funny that I don't remember any of the Pharo 4 development images freezing. > > Which image can I use that won't do this? > > Craig >

June 1, 2015

Re: [Pharo-users] SmalltalkHub permission denied

by Esteban Lorenzano

are you entering user and password? > On 01 Jun 2015, at 22:30, Hilaire <hilaire(a)drgeo.eu> wrote: > > Le 01/06/2015 22:28, Hilaire a Ã©crit : >> Hi, >> >> I have permission denied from Monticello when saving a package to >> SmalltalkHub repo. >> Do I miss something? >> >> Thanks >> >> Hilaire >> > > ...and I can login to the SmalltalkHub website > > -- > Dr. Geo > http://drgeo.eu > http://google.com/+DrgeoEu > > >

June 1, 2015

Pharo 4 Image Freeze

by Craig Johnson

Hi All, I'm getting tired of Pharo 4 beta freezing. It happens whenever a exception occurs while in the debugger. Funny that I don't remember any of the Pharo 4 development images freezing. Which image can I use that won't do this? Craig

June 1, 2015

Re: [Pharo-users] SmalltalkHub permission denied

by Hilaire

Le 01/06/2015 22:28, Hilaire a Ã©crit : > Hi, > > I have permission denied from Monticello when saving a package to > SmalltalkHub repo. > Do I miss something? > > Thanks > > Hilaire > ...and I can login to the SmalltalkHub website -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

June 1, 2015

SmalltalkHub permission denied

by Hilaire

Hi, I have permission denied from Monticello when saving a package to SmalltalkHub repo. Do I miss something? Thanks Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

June 1, 2015

Re: [Pharo-users] Issue with UDP Sockets

by Henrik Johansen

> On 29 May 2015, at 7:24 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 29 May 2015, at 18:23, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >> >>> >>> On 19 May 2015, at 11:01 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> >>>> On 19 May 2015, at 10:53, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: >>>> >>>>> Did you look in all your package caches ? >>>> I did. Must have been a victim of cleaning ... but maybe TimeMachine has something ... thanks for the reminder. >>>> >>>>> If it is just a small example, like one class, maybe it could be >>>>> added to the image, in which case it should indeed be a slice. >>>> The package was pretty simple. Basically only adding a few convenience methods around Socket>>#setOption:value: . Still I think a usage example in form of a class comment and test case might be appropriate. So unless Multicast should be part of the base image I'll start with a separate package first. >>> >>> Since Socket is a fundamental part, and multicast is a key feature, I think it would logical to move it to the image itself, with a test case. >> >> It's not just multicast... >> As a Socket newbie I recently spent longer than I care to admit learning you need to set SO_BROADCAST to true to not get a primitive failure when sending to a broadcast address. >> At least the comments in sqUnixSocket were entertaining! >> >> Though I realize which options are actually supported depends on the VM, moving the list of potentially available cross-platform options (and a description of what they're used for) to a comment in the image (setOption: value: being the obvious location) might be a nice first step. > > Please help in the documentation effort. I later found the option names are already documented in getOption:, but since that wasn't of much help (at least to me), I suggest introducing a more specific error than primitiveFailure. Implementing that, the new test revealed a bug; empty UDP payloads will not be sent. A suggested fix for both these issues can be found in SLICE-Issue-15657-Empty-UDP-packets-are-not-sent-HenrikSperreJohansen.1 Cheers, Henry

June 1, 2015

Re: [Pharo-users] Slot questions

by tsl4

As usual, though, a lot of interesting ideas emerge from this. If we were to do documentation in a "Smalltalky" way, then what would it look like? Perhaps something like Doug Engelbart's NLS system, in outlines, but each element of the outline would have an associative history to it. That would mean breaking the process of description down to familiar component parts. Selecting a version of the software would flow through the outline, calling up the appropriate historical elements. That would enable comparative documentation. Or is it possible to find some kind of self documentation that would be better than the useful but a little crude class comments? It seems like such a basic thing to get right, but really very little work has been done on it. -- View this message in context: http://forum.world.st/Slot-questions-tp4679631p4829738.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 1, 2015