March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3320 in pharo: [Kernel Dependencies] Object>>#indexIfCompact

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3320 by Benjamin...(a)gmail.com: [Kernel Dependencies] Object>>#indexIfCompact http://code.google.com/p/pharo/issues/detail?id=3320 (No comment was entered for this change.)

March 12, 2011

Re: [Pharo-project] Issue 3810 in pharo: Methods of Traits are in the changesorter, but not the fileout

by pharo＠googlecode.com

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #1 on issue 3810 by marcus.d...(a)gmail.com: Methods of Traits are in the changesorter, but not the fileout http://code.google.com/p/pharo/issues/detail?id=3810 fix attached. Attachments: FixFileOut.2.cs 991 bytes

March 12, 2011

Re: [Pharo-project] Issue 3323 in pharo: [Kernel Dependencies] Model>>#initialExtent

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3323 by stephane...(a)gmail.com: [Kernel Dependencies] Model>>#initialExtent http://code.google.com/p/pharo/issues/detail?id=3323 (No comment was entered for this change.)

March 12, 2011

Re: [Pharo-project] Issue 3375 in pharo: PositionableStream remove dependence to Compiler

by pharo＠googlecode.com

Updates: Status: Closed Comment #11 on issue 3375 by stephane...(a)gmail.com: PositionableStream remove dependence to Compiler http://code.google.com/p/pharo/issues/detail?id=3375 in 13083

March 12, 2011

[Pharo-project] Issue 3810 in pharo: Methods of Traits are in the changesorter, but not the fileout

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3810 by marcus.d...(a)gmail.com: Methods of Traits are in the changesorter, but not the fileout http://code.google.com/p/pharo/issues/detail?id=3810 Try to fileout a changeset with changes on a trait --> .cs does not contain the method.

March 12, 2011

Re: [Pharo-project] Issue 1507 in pharo: is LocatedMethod needed?

by pharo＠googlecode.com

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #3 on issue 1507 by marcus.d...(a)gmail.com: is LocatedMethod needed? http://code.google.com/p/pharo/issues/detail?id=1507 As a first step, we can just replace it by MethodReference Fix attached. besides the changeset, this method needs to be changed in TTransformationCompatibility collectMethodsFor: aSelector into: methodDescription (self includesSelector: aSelector) ifTrue: [ methodDescription addLocatedMethod: ( MethodReference class: self selector: aSelector)] Attachments: LocatedMethodFix.4.cs 2.2 KB

March 12, 2011

[Pharo-project] [update 1.3] #13082

by StÃ©phane Ducasse

13082 ----- - Issue 3074: Suggestion for Remodularisation -> SmalltalkImage. Thanks Nicolas Paez. - Created System-SourceAndChangeFile - Symbol part 3. - Finder fix. Stef

March 12, 2011

[Pharo-project] Issue 3809 in pharo: Fixed Width / Serif Font

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3809 by camillob...(a)gmail.com: Fixed Width / Serif Font http://code.google.com/p/pharo/issues/detail?id=3809 We should add all three DejaVu fonts directly to the image. - fixed width (major priority for programming!) - serif (for long text text, since they are much more readable)

March 12, 2011

Re: [Pharo-project] Fixed Width Font for COG

by Camillo Bruni

Does anyone know what the proceedure is to include a new font directly in the image without plugin support? eg Issue 3809 using DejaVu Mono in the image camillo On 2011-03-11, at 15:21, StÃ©phane Ducasse wrote: > may be the freetype plugin is missing. > > > On Mar 11, 2011, at 2:57 PM, Camillo Bruni wrote: > >> Hey, >> >> I recently ran into the issue that I cannot use a fixed width/monospace font when working under COG. >> >> How can I include a custom font in the image? >> >> m(^_-)m >> camillo >> >> > >

March 12, 2011

[Pharo-project] Issue 3808 in pharo: Process should not depend on the debugger

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com New issue 3808 by stephane...(a)gmail.com: Process should not depend on the debugger http://code.google.com/p/pharo/issues/detail?id=3808 Process>>debugWithTitle: title "Open debugger on self" | context | context := self isActiveProcess ifTrue: [thisContext] ifFalse: [self suspendedContext]. self debug: context title: title full: true. Process>>terminate "Stop the process that the receiver represents forever. Unwind to execute pending ensure:/ifCurtailed: blocks before terminating." | ctxt unwindBlock oldList | self isActiveProcess ifTrue: [ ctxt := thisContext. [ ctxt := ctxt findNextUnwindContextUpTo: nil. ctxt isNil ] whileFalse: [ (ctxt tempAt: 2) ifNil: [ ctxt tempAt: 2 put: nil. unwindBlock := ctxt tempAt: 1. thisContext terminateTo: ctxt. unwindBlock value ]]. thisContext terminateTo: nil. self suspend ] ifFalse: [ "Always suspend the process first so it doesn't accidentally get woken up" oldList := self suspend. suspendedContext ifNotNil:[ "Figure out if we are terminating the process while waiting in Semaphore>>critical: In this case, pop the suspendedContext so that we leave the ensure: block inside Semaphore>>critical: without signaling the semaphore." (oldList class == Semaphore and:[ suspendedContext method == (Semaphore compiledMethodAt: #critical:)]) ifTrue:[ suspendedContext := suspendedContext home.]. "If we are terminating a process halfways through an unwind, try to complete that unwind block first." (suspendedContext findNextUnwindContextUpTo: nil) ifNotNil: [ :outer | (suspendedContext findContextSuchThat: [ :c | c closure == (outer tempAt: 1)]) ifNotNil: [ :inner | "This is an unwind block currently under evaluation" suspendedContext runUntilErrorOrReturnFrom: inner ]]. ctxt := self popTo: suspendedContext bottomContext. ctxt == suspendedContext bottomContext ifFalse: [ self debug: ctxt title: 'Unwind error during termination']] ]. We should probably raise an exception and catch it somewhere.

March 12, 2011