- Pharo-dev - lists.pharo.org

Re: [Pharo-project] FFI number of arguments

by Miguel CobÃ¡

El miÃ©, 06-10-2010 a las 11:50 -0400, Schwab,Wilhelm K escribiÃ³: > Levente, > > What problem do you have with asking whether someone else has already tried it? Really, have you not seen examples of working hard on advice from one source only to discover yet another limit that was not in fine print? > But Bill, almost all your questions are long and without apparent focus on the real point. Some other times are like this, things that you could easily test by yourself maybe in less time that takes you to write so many words, send the email and wait for a response from someone willing to decipher what the real problem is. Other times you point at problems that you find in your environment without giving better hints than "in a hopefully updated image", "in a, I think, not modified image", "in my machine", that doesn't help in helping you. Then you point some problems that it appears that are very evident to you and whose solution is also very obvious to you but you don't provide a fix for them neither, like the always topic of yours about sockets. Then when someone points and the obvious things you should do (your homework, in verifying yourself what you are asking to the list) or to precise the information needed to better answer you, you respond upset as if anyone should be obliged to answer you or even read your mails. So, please, read http://www.catb.org/esr/faqs/smart-questions.html do your homework and then ask the list. > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Levente Uzonyi [leves(a)elte.hu] > Sent: Tuesday, October 05, 2010 11:09 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] FFI number of arguments > > On Tue, 5 Oct 2010, Schwab,Wilhelm K wrote: > > > yes, that's what the link describes. The open question is whether anyone has successfully done that with 15+ arguments? > > It works up to 128 arguments. But why don't you try it yourself? > > > Levente > > > > > > > > > ________________________________________ > > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Levente Uzonyi [leves(a)elte.hu] > > Sent: Tuesday, October 05, 2010 10:26 PM > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: Re: [Pharo-project] FFI number of arguments > > > > On Tue, 5 Oct 2010, Schwab,Wilhelm K wrote: > > > >> 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? > > > > You can create your own function object and invoke it with an array. > > Here's an fprintf example on windows: > > > > fprintf := ExternalLibraryFunction > > name: 'fprintf' > > module: 'msvcrt.dll' > > callType: ExternalFunction callTypeCDecl > > returnType: ExternalType signedLong > > argumentTypes: { > > (ExternalType structTypeNamed: #FILE) asPointerType. > > ExternalType string. > > ExternalType signedLong }. > > file := Stdio default fopenWith: 'test.txt' with: 'w'. > > fprintf invokeWithArguments: { file. 'Your number is %d.'. 42 }. > > Stdio default fcloseWith: file. > > > > > > Levente > > > > P.S.: Note that you need the FILE and Stdio classes to run this example. > > > >> > >> Bill > >> > >> > >> _______________________________________________ > >> 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 > > > > _______________________________________________ > > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Oct. 6, 2010

Re: [Pharo-project] Smalltalk at: #Foo - needs clarification

by Andreas Raab

On 10/6/2010 6:58 AM, Igor Stasenko 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? The base dictionary access methods (#at:, #at:put:, #at:ifAbsent:) should remain in Smalltalk for compatibility. Then it's a matter of where that request is being delegated. Cheers, - Andreas

Oct. 6, 2010

Re: [Pharo-project] FFI number of arguments

by Schwab,Wilhelm K

Levente, What problem do you have with asking whether someone else has already tried it? Really, have you not seen examples of working hard on advice from one source only to discover yet another limit that was not in fine print? ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Levente Uzonyi [leves(a)elte.hu] Sent: Tuesday, October 05, 2010 11:09 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] FFI number of arguments On Tue, 5 Oct 2010, Schwab,Wilhelm K wrote: > yes, that's what the link describes. The open question is whether anyone has successfully done that with 15+ arguments? It works up to 128 arguments. But why don't you try it yourself? Levente > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Levente Uzonyi [leves(a)elte.hu] > Sent: Tuesday, October 05, 2010 10:26 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] FFI number of arguments > > On Tue, 5 Oct 2010, Schwab,Wilhelm K wrote: > >> 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? > > You can create your own function object and invoke it with an array. > Here's an fprintf example on windows: > > fprintf := ExternalLibraryFunction > name: 'fprintf' > module: 'msvcrt.dll' > callType: ExternalFunction callTypeCDecl > returnType: ExternalType signedLong > argumentTypes: { > (ExternalType structTypeNamed: #FILE) asPointerType. > ExternalType string. > ExternalType signedLong }. > file := Stdio default fopenWith: 'test.txt' with: 'w'. > fprintf invokeWithArguments: { file. 'Your number is %d.'. 42 }. > Stdio default fcloseWith: file. > > > Levente > > P.S.: Note that you need the FILE and Stdio classes to run this example. > >> >> Bill >> >> >> _______________________________________________ >> 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 > > _______________________________________________ > 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

Oct. 6, 2010

Re: [Pharo-project] [squeak-dev] Smalltalk at: #Foo - needs clarification

by Fernando olivero

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

Oct. 6, 2010

Re: [Pharo-project] Tests broken with Citezen

by Alexandre Bergel

Yes, it works also for me. Thanks Cheers, Alexandre On 6 Oct 2010, at 11:03, StÃ©phane Ducasse wrote: > 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 > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 6, 2010

Re: [Pharo-project] Tests broken with Citezen

by StÃ©phane Ducasse

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

Oct. 6, 2010

Re: [Pharo-project] Tests broken with Citezen

by Alexandre Bergel

> 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 6, 2010

[Pharo-project] TextConstants-related issues (3066 & 3067)

by NicolÃ¡s Paez

Issue 3066: Classes using TextConstants as a common Dictionary Issue 3067: TextConstants used in different ways Saludos! Nico. blog: nicopaez.wordpress.com

Oct. 6, 2010

Re: [Pharo-project] Tests broken with Citezen

by StÃ©phane Ducasse

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

Oct. 6, 2010

Re: [Pharo-project] System Tracer

by StÃ©phane Ducasse

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

Oct. 6, 2010