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

Re: [Pharo-project] test crashing the cog vm

by StÃ©phane Ducasse

>> <stephane.ducasse(a)inria.fr> wrote: >>> >>> But why we could not have a byecode validator at the image level that >>> first make sure that byte code are in sync with the format of the objects. >> >> Because it can be compromised. An in-image verifier is subject to attack, >> and could be disabled by an attack that got past the in-image verifier >> before it got a chance to run. An in-VM verifier is not possible to >> side-step because it is the only way to execute code. So an in-VM verifier >> can be secure but an in-image one can't and so is pointless. >> > For real hacker there's nothing impossible :) > > Right now its not possible to split image to layered onion (like > operating system does, where you have kernel level, > and user level), but i think (at least in theory) such composition > could be implemented, except that sure thing > we don't have resources to invest in this direction. > > It is actually nice field for research (hello guys from academy :) we have three phds on the topics and we will see. > > -- > Best regards, > Igor Stasenko AKA sig. >

March 24, 2011

Re: [Pharo-project] test crashing the cog vm

by StÃ©phane Ducasse

Of course if we talk about attack. I was just talking about verifying to avoid simple crashes. Stef On Mar 24, 2011, at 7:34 PM, Eliot Miranda wrote: > > > On Tue, Mar 22, 2011 at 5:34 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > But why we could not have a byecode validator at the image level that first make sure that byte code are in sync with the format of the objects. > > Because it can be compromised. An in-image verifier is subject to attack, and could be disabled by an attack that got past the in-image verifier before it got a chance to run. An in-VM verifier is not possible to side-step because it is the only way to execute code. So an in-VM verifier can be secure but an in-image one can't and so is pointless. > > > Why this has to be done in the vm. > > Stef >

March 24, 2011

Re: [Pharo-project] Pharo 1.2 red again

by StÃ©phane Ducasse

this is a good news Stef On Mar 24, 2011, at 4:59 PM, Dale Henrichs wrote: > Stef, > > Yep ... all the pieces are there ... it's just a matter of putting them together in the right order..this is what we do for GemStone GLASS builds... > > Dale > > On Mar 24, 2011, at 1:21 AM, StÃ©phane Ducasse wrote: > >> henrichs >> >> do you know if you have now the pieces in place to be able to freeze a configuration and all its recursive sets in a dedicated repository? >> >> Stef > >

March 24, 2011

Re: [Pharo-project] double click highlighting problem with quotation marks

by DougEdmunds

Is there an ambiguity that can't be resolved? If it looked backward first before looking forward, it might find an unmatched 'opening' quotation mark. This applies to both single and double quotes. -- View this message in context: http://forum.world.st/double-click-highlighting-problem-with-quotation-mark… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 24, 2011

[Pharo-project] Issue 3875 in pharo: Merge minor NumberParser refactorings from Squeak

by pharo＠googlecode.com

Status: Accepted Owner: nicolas....(a)gmail.com Labels: Type-Squeak New issue 3875 by nicolas....(a)gmail.com: Merge minor NumberParser refactorings from Squeak http://code.google.com/p/pharo/issues/detail?id=3875 There are three changed methods: 1) using peekSignIsMinus gives a chance to subclasses to parse a leading + 2) using ifNil: is faster than isNil ifTrue: (with current Compiler) 3) skip: -1 in an error case so as to insert the error message at the right place

March 24, 2011

[Pharo-project] [COTDC] 35#2 - MCDefinitionIndex

by laurent laffont

Today: MCDefinitionIndex Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

March 24, 2011

Re: [Pharo-project] [COTDC] 35 - MCPackageCache

by laurent laffont

Aborted. Laurent On Thu, Mar 24, 2011 at 7:18 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Anyone or abort ? > > Laurent. > > On Wed, Mar 23, 2011 at 6:40 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> Today: MCPackageCache >> >> >> Comment Of The Day Contest - One Day One Comment >> Rules: >> #1: Each day a not commented class is elected. Each day the best comment >> will be integrated with name of the author(s). >> #2: If you cannot comment it, deprecate it. >> Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >> >> Laurent >> > >

March 24, 2011

Re: [Pharo-project] double click highlighting problem with quotation marks

by Nicolas Cellier

Of course, there is an ambiguity whether you want the closing quote or the opening parenthesis... And there is an arbitrary precedence rule. IMO, a modifier key might help to disambiguate... It would also be a nice thing to have a keyboard combination producing the same effect, For example: - Escape left_arrow selects downto the left opening, - Escape right_arrow selects upto the right closing... Unless of course there's already a shortcut I'm not aware of... Nicolas 2011/3/23 DougEdmunds <dougedmunds(a)gmail.com>: > Double clicking just to the left of a closing brace/bracket/parenthesis etc > normally > goes backwards, finds the opening brace/bracket/parenthesis and highlights > the material > between them. Â It does not work correctly if the character immediately > before the > closing mark is a single or double quotation mark. Â Instead it always goes > forward > from the quotation mark to try to find another quotation mark further in the > text. > > File ExampleClass.st > > 'From Pharo1.2 of 14 March 2011 [Latest update: #12341] on 23 March 2011 at > 11:16:26 am'! > Object subclass: #ExampleClass > Â Â Â Â instanceVariableNames: 'content owner' > Â Â Â Â classVariableNames: '' > Â Â Â Â poolDictionaries: '' > Â Â Â Â category: 'Sandbox'! > > !ExampleClass methodsFor: 'as yet unclassified' stamp: 'DougEdmunds > 3/23/2011 11:16'! > testMessage > > > Â Â Â Â | a b c d| > Â Â Â Â a := #( 1 2 (3 4 'test 1') 'test 2'). Â "click just before last closing > parens" > Â Â Â Â b := 'test 3'. > Â Â Â Â c := #( 1 2 (3 4 'test 4') 'test 5' ). "click just before last closing > parens" > Â Â Â Â d := 'test 6'. > ! ! > > -- > View this message in context: http://forum.world.st/double-click-highlighting-problem-with-quotation-mark… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

March 24, 2011

Re: [Pharo-project] Issue 3341 in pharo: use #= for integer comparison instead of #==

by pharo＠googlecode.com

Comment #4 on issue 3341 by nicolas....(a)gmail.com: use #= for integer comparison instead of #== http://code.google.com/p/pharo/issues/detail?id=3341 SLICE-Issue-3341-IntegerComparisonShallUseEqual-Part1-nice.1 Dependencies: Kernel-nice.847 Transform a few == into = and ~~ into ~= in Kernel

March 24, 2011

Re: [Pharo-project] custom code on squeaksource

by Eliot Miranda

On Thu, Mar 24, 2011 at 11:43 AM, Camillo Bruni <camillo.bruni(a)inria.fr>wrote: > We are currently working on first-class slots and layouts in pharo. > This required some changes in how the class definitions are printed: > > ============================================= > Object subclass: #Layout > layout: ObjectLayout > slots: { > #host => Slot. > #compactClassIndex => Slot. > } > classSlots: {} > globals: '' > category: #'Slot-Layout' > I like it! A great use for tuples. Not sure I like sots vs instanceVarables, but then I'm an old man ;) Have you thought about automatically creating accessors for byte data? I'm imagining HeapField subclass: #ObjectHeaderLittleEndian type: #Bits fields: { #classTag => 20. #isPointers => 1 => #Boolean. #isIndexable => 1 => #Boolean. #slotSize => 8 => #Align => 8. #identityHash => 20 => #Align => 32. #isMarked => 1 => #Boolean. #isForwarded => 1 => #Boolean. #isWeak => 1 => #Boolean. #isEphemeron => 1 => #Boolean. } classSlots: {} globals: '' category: #'VMMaker-MemoryManager' > > ============================================= > > I adapted the MCClassDefinition >> definitionString to output our new class > definitions. > > However squeaksource is not too happy with this and rewrites it completely > using the default definition. > > Local mcz files contain the new definition, mcz files loaded form > squeaksources still the old definition. > > Is there a way to still use squeaksources with our custom classes? > > thanks > > v(^_^)v > camillo >

March 24, 2011