- Pharo-dev - lists.pharo.org

Re: [Pharo-project] DocTest

by Tudor Girba

+1 Doru On Jan 23, 2013, at 1:07 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > for that we already have a fully working Phexample: > > http://www.squeaksource.com/phexample.html > > which I will push in 3.0, cause I never really liked #assert: and friends being > sent to self. Furthermore we could finally build up decent messages! > > On 2013-01-22, at 18:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> it would be nice to introduce the same syntax than Sunit >> >> exp assert: exp2 >> >> [ exp ] shouldraise: >> >> Stef >> >> >> On Jan 21, 2013, at 4:41 AM, Benjamin wrote: >> >>> Hi guys, >>> >>> I am attending a python lecture and discovered DocTest[1], and I was wondering if such a tool exists for Pharo ? :) >>> >>> >>> Ben >>> >>> [1]http://docs.python.org/2/library/doctest.html >>> >>> >> >> > > -- www.tudorgirba.com "Every thing should have the right to be different."

Jan. 23, 2013

Re: [Pharo-project] iCal port to Magritte3

by Yanni Chiu

Hmmm. It seems the ConfigurationOf is expecting GemStone and Squeak, not Pharo. Yikes, the differences in Date, Time, DateAndTime, timezones, etc. across dialects and versions is a *challenge*. I probably don't need Magritte3. I just want to create ical files. [Aside. I wish there were a mailing list for cross-platform packages] On 22/01/13 3:05 PM, Yanni Chiu wrote: > I just started to look at ical on squeaksource, and am happy to find > it's actively being worked on. > > Is anyone working on porting iCalMagritte to Magritte3? > Should I do it, and call it iCalMagritte3? Then we'd have two dev > streams to maintain. > > There are some minor problems with the code. > > - ICalChronos-PaulDeBruicker.5 is not in the repository (maybe lost to a > squeaksource restart) > - the test class StafferDateAndTime is not defined anywhere (maybe it's > in the missing package)

Jan. 23, 2013

Re: [Pharo-project] User Interrupt Broken?!

by David T. Lewis

Keep in mind that responding to the user interrupt key can be timing dependent, so differences between the behavior of Cog and interpreter VMs may be nothing more than the effect of a faster versus slower VM running the same image. It does not mean that Cog is more (or less) error prone, it might be just that Cog is arriving at the error condition faster. Basically, the VM will try to figure out what process was *probably* running at the time of the user interrupt (but this is really only a guess as to which process the user intended to interrupt), and the image needs to figure out what process to interrupt in a debugger based on whatever it can learn out from the VM. This is not an entirely reliable operation ;) Dave On Wed, Jan 23, 2013 at 01:17:18AM +0100, Camillo Bruni wrote: > have you tried an older StackVM, I remember getting this behavior with more > certainty under the CogVM... > > On 2013-01-22, at 18:51, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > > > Has anyone else noticed this? Open a fresh 2.0482 latest and hit Cmd-. a > > bunch of times. If the debugger opens on the first, close it and keep > > pressing the shortcut. Most presses seem to do nothing. > > > > > > > > -- > > View this message in context: http://forum.world.st/User-Interrupt-Broken-tp4664619.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > >

Jan. 23, 2013

Re: [Pharo-project] User Interrupt Broken?!

by Sean P. DeNigris

Camillo Bruni-3 wrote > have you tried an older StackVM I can't even start a fresh 2.0482 image with a stack vm. I tried an old one from early 2012, and the oldest and newest from the static file server. -- View this message in context: http://forum.world.st/User-Interrupt-Broken-tp4664619p4664744.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 23, 2013

Re: [Pharo-project] User Interrupt Broken?!

by Camillo Bruni

have you tried an older StackVM, I remember getting this behavior with more certainty under the CogVM... On 2013-01-22, at 18:51, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > Has anyone else noticed this? Open a fresh 2.0482 latest and hit Cmd-. a > bunch of times. If the debugger opens on the first, close it and keep > pressing the shortcut. Most presses seem to do nothing. > > > > -- > View this message in context: http://forum.world.st/User-Interrupt-Broken-tp4664619.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 23, 2013

Re: [Pharo-project] NativeBoost and unions

by Camillo Bruni

yes please! On 2013-01-22, at 19:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > as all the core packages for pharo (and NB is one of them), it should be in smalltalkhub :) > > On Jan 22, 2013, at 5:29 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On Jan 22, 2013, at 5:26 PM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> wrote: >> >>> Hi Igor, >>> >>> as usual after squeaksource restart, i lost my commit rights on the NativeBoost repository... >>> >> >> Could NativeBoost move away from SqueakSource? SqueakSource is not stable. >> >>> This time I have a small refactoring in the NBExternalStruct/NBExternalStructFields to enable union support. >>> >>> Besides that, c unions, I have implemented a first prototype, and now my question for you is: Should I add it in nativeboost (its rightful place in my opinion), >>> or should I keep it only as support code for my TalkFFI project(in TalkFFI-runtime)? What do you think? >>> >>> Cheers, >>> Ciprian >>> -- >>> Dr. Ciprian TEODOROV >>> IngÃ©nieur DÃ©veloppement CAO >>> >>> tÃ©l : 06 08 54 73 48 >>> mail : ciprian.teodorov(a)gmail.com >>> www.teodorov.ro >> >

Jan. 23, 2013

Re: [Pharo-project] DocTest

by Camillo Bruni

for that we already have a fully working Phexample: http://www.squeaksource.com/phexample.html which I will push in 3.0, cause I never really liked #assert: and friends being sent to self. Furthermore we could finally build up decent messages! On 2013-01-22, at 18:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > it would be nice to introduce the same syntax than Sunit > > exp assert: exp2 > > [ exp ] shouldraise: > > Stef > > > On Jan 21, 2013, at 4:41 AM, Benjamin wrote: > >> Hi guys, >> >> I am attending a python lecture and discovered DocTest[1], and I was wondering if such a tool exists for Pharo ? :) >> >> >> Ben >> >> [1]http://docs.python.org/2/library/doctest.html >> >> > >

Jan. 23, 2013

[Pharo-project] Athens replacement for ImageReadWriter?

by Esteban Lorenzano

Hi, So, ImageReadWriter currently reads image files and retrieve Form objects, who can be displayed in world... anybody knows (cough, cough, Igor) what would be the Athens replacement for that? thanks, Esteban

Jan. 23, 2013

Re: [Pharo-project] SmallLint applied on Pharo: Continued

by StÃ©phane Ducasse

> Well. I've written the tag support, so let's make it simple, MIT. > I may export a changeset with that code for you, if you like. Else I will just go over them and it will help me to understand. I think that this is not difficult. > For rules written by CG I'm not sure. You should check with him. > But I think it won't be a problem given that you preserve all > the signatures and #documentation and #version_XXX methods > (we use them to track changes in the source). > > However, what I planned (and run out of time :-) is to make > tag a first class object with name (symbol) description etc > and have class methods to create them. Then one may define and > describe meaning of the tag in an extension method. > Also, the selection/rejection logic could dispatch back on > the tag instance so you may then create fancy dynamic tags > (like #portability that automatically includes everything tagged > as #pharo #squeak #stx #va, for instance or whatever. > > I might hack it later this week, if you would include it into > your version (otherwise I've more important things to do :-) I imagine well. Let us keep it simple. Simple tags with a little class comments are good enough :) > > Cheers > > On 22/01/13 19:32, StÃ©phane Ducasse wrote: >> Jan >> what is the license of your tags and other code? >> >> Stef >> >> On Jan 22, 2013, at 3:45 PM, Jan Vrany wrote: >> >>> On 22/01/13 18:22, StÃ©phane Ducasse wrote: >>>> Hi >>>> >>>> I'm running the rule RBSubclassResponsibilityNotDefinedRule that >>>> >>>> Checks that all subclassResponsibility methods are defined in all leaf classes. >>>> >>>> Now the results display the sender of ^ subclassResponsibility but I have to manually find the >>>> problems. I would be better to report the violations. Of course this is not that simple: returning a class and missing method. >>>> >>>> But this would be much better. Jan did you do that in your version? >>> >>> Good point. Yes, since now we do that :-) >>> >>> Jan >>> >>>> >>>> Stef >>>> >>> >>> >> >> >> > >

Jan. 22, 2013

Re: [Pharo-project] Must OSPlatform class>>osVersion be deprecated?

by David T. Lewis

On Tue, Jan 22, 2013 at 01:51:56PM -0800, Chris Cunningham wrote: > On Tue, Jan 22, 2013 at 12:13 PM, David T. Lewis <lewis(a)mail.msen.com>wrote: > > > On Tue, Jan 22, 2013 at 08:05:02PM +0100, Marcus Denker wrote: > > > > > > On Jan 22, 2013, at 5:27 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > > > > > > > Dave > > > >> > > > This works in Pharo 2.0? > > > > Yes, "Smalltalk os version" is right for Pharo 2.0. > > > > I'm looking for a way to modify the following method so that it adds > > support > > for Pharo 2.0, so that it continues to work in the other images, and so > > that > > it does not raise deprecation warnings or DNUs in any of the images. > > > > Could you capture for deprecation of OSPlatform osVersion, and resend the > other method (Smalltalk osVersion current osVersion)? Or, trap for > Deprecation and resume it (ignore deprecation - once it is removed, you'll > automatically fail-over to the new code). No, Pharo 2.0 is writing console output whenever an exception occurs, so catching the exception is not good. But not raising the exception in the first place works just fine ;) Dave

Jan. 22, 2013