- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 2247. is it closed?
by Bernardo Ezequiel Contreras Dec. 13, 2010

Dec. 13, 2010

Hi all, i added a new comment to http://code.google.com/p/pharo/issues/detail?id=2247 could you check it? Thank you

1 0

[Pharo-project] Is executing a file platform dependent?
by Max Leske Dec. 13, 2010

Dec. 13, 2010

Hi guys I was wondering if it is true that executing a file from within Pharo is platform dependent. I don't actually need to execute a file; it's more a theoretical question and I have no idea what the mechanisms are that would be used. To give you a clearer picture: Imagine you have C, sh, and perl files. What I'm thinking about is that I would have some data in the image that I would want to process with the code in one of those files. I would then wait for the result and process the result in the image. So my questions are: is there a platform independent way to execute C, sh or perl files from Pharo? Does the VM handle the platform dependencies? Are there any other issues with the idea I described? Don't go out of your way to find answers, please. But I'd be happy to hear your thoughts. Cheers, Max

4 5

Re: [Pharo-project] Ring - model infrastructure for Pharo
by Marcus Denker Dec. 13, 2010

Dec. 13, 2010

> the format is different for RecentMessageList > 'Class >> #selector' > 'Class(removed) >> #selector' > Is this class being used? Or its method #removeAMethod: ? > I just noticed > that it is invoking #methodSymbol: from MethodReference, but that method > does not exist... > Without this, in fact we don't need an iVar, and we should manage an unique > format Hmm... that looks strange. In general, MethodReference should not seen as something defining what a general model needs, as it is in itself very strange and ugly. We need to carefully check. The use of RecentMessageList seems to be more that it needs a general way to associate meta-data with a reference ("I deleted this"). We should check the new stuff regarding RecentMessages that Benjamin did. Lots of the old things should be removed... -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

2 1

Re: [Pharo-project] Issue 2353 in pharo: #findString:startingAt:caseSensitive: broken for WideStrings
by pharo＠googlecode.com Dec. 13, 2010

Dec. 13, 2010

Updates: Status: Accepted Cc: siguctua Comment #6 on issue 2353 by stephane.ducasse: #findString:startingAt:caseSensitive: broken for WideStrings http://code.google.com/p/pharo/issues/detail?id=2353 Igor it would be nice if you could have a look in the coming month.

1 1

[Pharo-project] [update 1.2] #12277
by Marcus Denker Dec. 13, 2010

Dec. 13, 2010

12277 ----- Issue 3398: SystemNavigation and SourcedMethodReference Issue 3402: SmalltalkEditor new raises an Error -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3402 in pharo: SmalltalkEditor new raises an Error
by pharo＠googlecode.com Dec. 13, 2010

Dec. 13, 2010

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.2 New issue 3402 by stephane.ducasse: SmalltalkEditor new raises an Error http://code.google.com/p/pharo/issues/detail?id=3402 SmalltalkEditor new

1 4

[Pharo-project] Issue 3398 in pharo: SystemNavigation and SourcedMethodReference
by pharo＠googlecode.com Dec. 13, 2010

Dec. 13, 2010

Status: Accepted Owner: luc.fabresse Labels: Milestone-1.2 Type-FailingTest New issue 3398 by luc.fabresse: SystemNavigation and SourcedMethodReference http://code.google.com/p/pharo/issues/detail?id=3398 6 tests in SystemNavigationTest and SystemNavigationOnNewlyCreatedEnvironementTest are failing in 1.2-12272 This is because of the introduction of SourcedMethodReference. I already speak about this problem here: http://forum.world.st/About-SourcedMethodReference-td3035187.html SourcedMethodReference>>= must not be based on identity (==) because it prevents to have multiple SourcedMethodReference pointing to the same CompiledMethod. And we need that because each tools will use different SourcedMethodReference. IMHO, SourcedMethodReference are just proxies and we don't care of their identity. I attach a cs that make these 6 tests pass. I replace MethodReference by SourcedMethodReference in SystemNavigationTest and al... And I modified the equality method of SourcedMethodReference: SourcedMethodReference>>= anotherMethodReference ^ (super = anotherMethodReference) and: [ (self timeStamp = self timeStamp) and: [ self sourceCode = self sourceCode ]] I have no idea of the impact of this change for the SourcedMethodReference stuff point of view. Attachments: FixFailingSystemNavigationTests.1.cs 3.6 KB

1 8

Re: [Pharo-project] Issue 3208 in pharo: WriteStream>>nextChunkPut: aString
by pharo＠googlecode.com Dec. 13, 2010

Dec. 13, 2010

Updates: Status: Closed Comment #2 on issue 3208 by marcus.denker: WriteStream>>nextChunkPut: aString http://code.google.com/p/pharo/issues/detail?id=3208 Not enough information to reproduce

1 0

[Pharo-project] Issue 3407 in pharo: HashedCollection missed abstract method noCheckAdd:
by pharo＠googlecode.com Dec. 13, 2010

Dec. 13, 2010

Status: Accepted Owner: step...@stack.nl New issue 3407 by step...@stack.nl: HashedCollection missed abstract method noCheckAdd: http://code.google.com/p/pharo/issues/detail?id=3407 HashedCollection grow calls noCheckAdd: All direct subclasses implement noCheckAdd: Pharo image: core Pharo core version: 12272 Add the following method to HashedCollection: noCheckAdd: anObject self subclassResponsibility

1 1

[Pharo-project] I am a genius
by Norberto Manzanos Dec. 13, 2010

Dec. 13, 2010

Yes, I am. I can teach people how to write. Look, this is the unique class with only one method of my AI system: LinTirany >> analize: aString | errors | errors:= OrderedCollection new. #('would' 'very' ) do:[:each | (aString substrings includes: each) ifTrue:[ errors add: 'Avoid ',each]]. aString substrings size > 40 ifTrue:[errors add: 'Avoid long sentences']. ^errors Try it at http://textlint.lukas-renggli.ch and becomes an expert article writer. -- Norberto Manzanos Instituto de Investigaciones en Humanidades y Ciencias Sociales (IdIHCS) FaHCE/UNLP - CONICET Calle 48 e/ 6 y 7 s/NÂº - 8Âº piso - oficina 803 Tel: +54-221-4230125 interno 262

1 0