- Pharo-dev - lists.pharo.org

[Pharo-project] Bug in Pharo compiler?
by James Ladd Oct. 6, 2010

Oct. 6, 2010

Hi All, Currently im running the Redline Smalltalk compiler (http://redline.st) over the Pharo source to make sure that it is compatible with Pharo. What I noticed while compiling the class BitBlt is that an instance variable is also used as a method argument name! If you try and do this with the environment you get a "name already defined" error, yet it is in the source. Not sure what to do about it? Rgs, James.

2 2

[Pharo-project] FFI number of arguments
by Schwab,Wilhelm K Oct. 6, 2010

Oct. 6, 2010

Hello all, I have been bumping into some functions with large numbers of arguments. One in particular would be best handled in the image if at all possible. The following might be the answer: http://thread.gmane.org/gmane.comp.lang.smalltalk.squeak.general/98538/focu… Have any of you done this with >15 (or whatever the cutoff is) arguments? Bill

6 19

[Pharo-project] KomHttpServer in pharo 1.2
by Guillermo Polito Oct. 6, 2010

Oct. 6, 2010

*HttpServices class>>platform ^SmalltalkImage current platformName* Should be *HttpServices class>>platform ^OSPlatform platformName* How can it be adapted to pharo? Cheers!

5 8

Re: [Pharo-project] System Tracer
by StÃ©phane Ducasse Oct. 6, 2010

Oct. 6, 2010

generate a new image. On Oct 6, 2010, at 2:23 PM, Alexandre Bergel wrote: > Hi! > > What do you want to achieve? > > Cheers, > Alexandre > > > On 6 Oct 2010, at 05:36, Gabriel HernÃ¡n Barbuto wrote: > >> Hi >> >> Does anyone know where I can find the system tracer that is currently >> in use in Pharo? >> >> Bests >> Gabriel >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] Tests broken with Citezen
by Alexandre Bergel Oct. 6, 2010

Oct. 6, 2010

Hi! Citezen seems to not run on a 11414. CZEntry>>clean self class fieldKeysToRemove do: [:each | (self hasFieldWithKey: each) ifTrue: [self removeFieldWithKey: each]] There is no implementor of #fieldKeysToRemove I would like to use Citezen to generate the Research webpage on Pharo. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 2

[Pharo-project] Smalltalk at: #Foo - needs clarification
by Igor Stasenko Oct. 6, 2010

Oct. 6, 2010

Hello, just wanna ask, is this part of API will be deprecated in future? (in Pharo, it put under 'to clean later' category). And if yes, then what will be correct (dialect-agnostic) way to access globals? Smalltalk globals at: #Foo ? I thought that #at: #at:put: (and some others) historically is a part of Smalltalk protocol, and should stay there to support legacy code and cross-dialect code. What you thoughts about it? -- Best regards, Igor Stasenko AKA sig.

3 3

[Pharo-project] Tool for: Image2 - Image1 > FileOut?
by Stefan Marr Oct. 6, 2010

Oct. 6, 2010

Hello: I got here two images without sufficient development history, source code management, or change sets. One of the images is the basis point and the other contains all the relevant code I need to file out somehow so that it represents a diff which can be filed into the base point image easily. I am only interested in classes, methods, and their meta infos, so general state in the image is not a problem at the moment. If it would be only about methods, that would be easy, since I can find out whether it is a changed/new method by locking at the fileIndex. However, for classes that does not work out. How can I find out whether they changed or were added? That seems to be only possible if they were actually commented... Is there any known tool which could produce me a diff/fileOut/changeSet from two given images? Or might there be any other information in the image I could use to create one myself? Thanks and best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

2 1

Re: [Pharo-project] [squeak-dev] Smalltalk at: #Foo - needs clarification
by Fernando olivero Oct. 6, 2010

Oct. 6, 2010

On Oct 6, 2010, at 5:30 PM, Fernando olivero wrote: > > On Oct 6, 2010, at 4:36 PM, stephane ducasse wrote: > >> >> >>> Hello, >>> >>> just wanna ask, is this part of API will be deprecated in future? >>> (in Pharo, it put under 'to clean later' category). >>> >>> And if yes, then what will be correct (dialect-agnostic) way to access globals? >>> >>> Smalltalk globals at: #Foo ? >>> >>> I thought that #at: #at:put: (and some others) >>> historically is a part of Smalltalk protocol, and should stay there to >>> support legacy code and cross-dialect code. >>> >>> >>> What you thoughts about it? >> >> legacy you said! Let us move on. We keep to help people migrating. >> Now we should avoid it as much as possible even Smalltalk globals at:. It should be more >> self class environment at: >> >> In VisualWorks I'm not sure that Smalltalk at: make sense. > > I've been using: > > Smalltalk globals classNamed: aString. > > IMO It's better from a conceptual view because > 1. it breaks the class-symbol binding, > 2. and a Dictionary-like implementation for lookup. > > > Fernando

1 0

Oct. 6, 2010

I just fixed the code. the test pass now. Alex I could generate my web page with this version this summer so it should work. Stef On Oct 6, 2010, at 4:43 PM, Alexandre Bergel wrote: >> I'm loading it right now. >> And the problem is that the default config load everything.... magritte grease seaside.... >> 20 min at least. > > Yes... I was also surprised of this... > > Alexandre > > >> >> >>> Hi! >>> >>> Citezen seems to not run on a 11414. >>> CZEntry>>clean >>> >>> self class fieldKeysToRemove >>> do: [:each | (self hasFieldWithKey: each) >>> ifTrue: [self removeFieldWithKey: each]] >>> >>> There is no implementor of #fieldKeysToRemove >>> >>> I would like to use Citezen to generate the Research webpage on Pharo. >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

Oct. 6, 2010

I'm loading it right now. And the problem is that the default config load everything.... magritte grease seaside.... 20 min at least. Stef > Hi! > > Citezen seems to not run on a 11414. > CZEntry>>clean > > self class fieldKeysToRemove > do: [:each | (self hasFieldWithKey: each) > ifTrue: [self removeFieldWithKey: each]] > > There is no implementor of #fieldKeysToRemove > > I would like to use Citezen to generate the Research webpage on Pharo. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1