August 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] UFFI const, unsigned, opaque-ish types

by Esteban Lorenzano

Hi, (Short because I'm by phone) Const should be ignored so you can keep it (if not is a bug) Unsigned does not exist :) You can always put an alias, but the type you are looking for is "uint" Cheers, Esteban > On 31 Aug 2016, at 18:59, Ben Coman <btc(a)openinworld.com> wrote: > > For this definition pulled from a library header file... > typedef struct { > const void *data; > unsigned private_flags; > } CXString; > > which is used with a helper function to get a usable string like... > void show_clang_version(void) > { CXString version = clang_getClangVersion(); > printf("%s\n", clang_getCString(version)); > clang_disposeString(version); > } > > ==> 'Debian clang version 3.5.0-10 (tags/RELEASE_350/final) (based on > LLVM 3.5.0)' > > > So I defined... > FFIExternalStructure subclass: #CXString > instanceVariableNames: '' > classVariableNames: '' > package: 'LibCLang' > > and ignoring the const as advised in the manual [1], I try... > CXString class >> fieldsDesc > ^ #( > void *data; > unsigned private_flags; > ) > > but... > CXString rebuildFieldAccessors. > ==>Error: Unable to resolve external type: unsigned > > I also tried "unsigned int private_flags;" > but get the same error. Any ideas what is wrong? > > > Actually I can kind of ignore creating accessors since this is like an > opaque type where I'm not expected to access its internals, but I do > need CXString as a return value like this... > > LibCLang class >> getClangVersion > ^ self ffiCall: #( CXString clang_getClangVersion () ) module: LibCLang > > which needs to be passed to this function to get a workable string.... > > LibCLang class >> getString: aCXString > ^ self ffiCall: #( String clang_getCString ( CXString aCXString ) > ) module: LibCLang > > However this doesn't work if I use FFIOpaqueObject instead of > FFIExternalStructure. > I guess the difference is opaque objects are normally pointers to a > type, whereas here that pointer is contained in a struct. > > What I've done at the moment to push ahead with experimenting is avoid > needing to generate accessors by adding... > > CXString >> printOn: asStream > self getString printOn: aStream > > CXString >> getString > ^ self ffiCall: #( String clang_getCString ( CXString self ) ) > module: LibCLang > > such that... > LibCLang getClangVersion "<Print It>" > ==> 'Debian clang version 3.5.0-10 (tags/RELEASE_350/final) (based > on LLVM 3.5.0)' > > > Is there a better way to approach this? > > cheers -ben > > btw, this is in Pharo 5 (Moose 6). > > [1] https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… >

Aug. 31, 2016

BitArray and BooleanArray ?

by Bernardo Ezequiel Contreras

Hi, why there isn't a BitArray or BooleanArray in the collection library? is there a sustitute for that? thanks -- Bernardo E.C. Sent from a cheap desktop computer in South America.

Aug. 31, 2016

UFFI const, unsigned, opaque-ish types

by Ben Coman

For this definition pulled from a library header file... typedef struct { const void *data; unsigned private_flags; } CXString; which is used with a helper function to get a usable string like... void show_clang_version(void) { CXString version = clang_getClangVersion(); printf("%s\n", clang_getCString(version)); clang_disposeString(version); } ==> 'Debian clang version 3.5.0-10 (tags/RELEASE_350/final) (based on LLVM 3.5.0)' So I defined... FFIExternalStructure subclass: #CXString instanceVariableNames: '' classVariableNames: '' package: 'LibCLang' and ignoring the const as advised in the manual [1], I try... CXString class >> fieldsDesc ^ #( void *data; unsigned private_flags; ) but... CXString rebuildFieldAccessors. ==>Error: Unable to resolve external type: unsigned I also tried "unsigned int private_flags;" but get the same error. Any ideas what is wrong? Actually I can kind of ignore creating accessors since this is like an opaque type where I'm not expected to access its internals, but I do need CXString as a return value like this... LibCLang class >> getClangVersion ^ self ffiCall: #( CXString clang_getClangVersion () ) module: LibCLang which needs to be passed to this function to get a workable string.... LibCLang class >> getString: aCXString ^ self ffiCall: #( String clang_getCString ( CXString aCXString ) ) module: LibCLang However this doesn't work if I use FFIOpaqueObject instead of FFIExternalStructure. I guess the difference is opaque objects are normally pointers to a type, whereas here that pointer is contained in a struct. What I've done at the moment to push ahead with experimenting is avoid needing to generate accessors by adding... CXString >> printOn: asStream self getString printOn: aStream CXString >> getString ^ self ffiCall: #( String clang_getCString ( CXString self ) ) module: LibCLang such that... LibCLang getClangVersion "<Print It>" ==> 'Debian clang version 3.5.0-10 (tags/RELEASE_350/final) (based on LLVM 3.5.0)' Is there a better way to approach this? cheers -ben btw, this is in Pharo 5 (Moose 6). [1] https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…

Aug. 31, 2016

Re: [Pharo-users] [Garage] How to espace sql special chars in a query?

by Blondeau Vincent

Hello, I used some method of RAEscapingSqlPrinter to escape the quotes. And it is working nicely now. I added the escaping method in Garage: String >> asPostgresEscapedSql You have to call it on the "unsafe strings" before executing the query (prepared statement or not). Thanks Pierce! Cheers, Vincent > -----Message d'origine----- > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de > Pierce Ng > EnvoyÃ© : vendredi 12 aoÃ»t 2016 17:44 > Ã : Any question about pharo is welcome > Objet : Re: [Pharo-users] [Garage] How to espace sql special chars in a query? > > On Fri, Aug 12, 2016 at 01:36:21PM +0200, Blondeau Vincent wrote: > > > Which database? > > Postgres > > PostgresV2 driver does not support the PostgreSQL extended query protocol > which allows prepared statements, AFAIK. > > https://www.postgresql.org/docs/current/static/protocol-overview.html. > > As for escaping SQL, the ROE package has a class called RAEscapingSqlPrinter > which may help. > > http://smalltalkhub.com/#!/~PharoExtras/ROE > > Pierce !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Aug. 31, 2016

Re: [Pharo-users] The myth of a small deployment image using metacello

by Dale Henrichs

On 8/31/16 4:34 AM, Denis Kudriashov wrote: > Hi Dale. > > 2016-06-24 21:53 GMT+02:00 Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>>: > > Does the following meet your needs? > > project: 'Magritte3' with: [ > spec > className: > #ConfigurationOfMagritte3; > versionString: #'stable'; > repository: > 'http://smalltalkhub.com/mc/Magritte/Magritte3/main/ > <http://smalltalkhub.com/mc/Magritte/Magritte3/main/>' ]; > > project: 'Magritte3Seaside' > copyFrom: 'Magritte' > with: [ spec loads: #('Seaside' ) ]; > project: 'Magritte3Core' > copyFrom: 'Magritte' > with: [ spec loads: ##('Core' ) ]; > > > I assume the "stupid workaround" is the fact that in your example > you had to specify Magritte twice? #project:copyFrom:with: has > been around for a long time in Metacello and was invented to solve > this particular problem ... FWIW, this feature is documented in > Lesson12 of "Metacello Configuration Tutorial Part 2" in the Help > Browser ... > > > Yes, this is pattern which we all must use. But problem that it is > duplication of groups definition in all dependant projects. > Norbert suggest solution for this by referencing group name inside > dependency list (spec requires: #( 'Magritte3*:Core*' )). I really > like this idea. > Denis, thanks for clarifying. I can definitely see that 'Magritte3*:Core*' is more convenient ... Could you add a Metacello issue[1] with these details? I don't have any major Metacello work scheduled in the near term so it will probably be a while before I implement such a feature. At first blush it would seem to require a bit of rework in the project name space implementation. A pull request with an implementation would be even better:) Dale [1] https://github.com/dalehenrich/metacello-work/issues/new

Aug. 31, 2016

Re: [Pharo-users] The myth of a small deployment image using metacello

by Denis Kudriashov

Hi Dale. 2016-06-24 21:53 GMT+02:00 Dale Henrichs <dale.henrichs(a)gemtalksystems.com>: > Does the following meet your needs? > > project: 'Magritte3' with: [ > spec > className: > #ConfigurationOfMagritte3; > versionString: #'stable'; > repository: ' > http://smalltalkhub.com/mc/Magritte/Magritte3/main/' ]; > > project: 'Magritte3Seaside' > copyFrom: 'Magritte' > with: [ spec loads: #('Seaside' ) ]; > project: 'Magritte3Core' > copyFrom: 'Magritte' > with: [ spec loads: ##('Core' ) ]; > > > I assume the "stupid workaround" is the fact that in your example you had > to specify Magritte twice? #project:copyFrom:with: has been around for a > long time in Metacello and was invented to solve this particular problem > ... FWIW, this feature is documented in Lesson12 of "Metacello > Configuration Tutorial Part 2" in the Help Browser ... > Yes, this is pattern which we all must use. But problem that it is duplication of groups definition in all dependant projects. Norbert suggest solution for this by referencing group name inside dependency list (spec requires: #( 'Magritte3*:Core*' )). I really like this idea.

Aug. 31, 2016

Re: [Pharo-users] Network System Settings

by Blondeau Vincent

Hello, If you have an orange corner at the top right of the field, the content is not saved. To do it, you have to Accept the changes: CTRL+S or CMD +S. The store setting allows you to use the same settings for other images. Best, Vincent > -----Message d'origine----- > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de > bharath > EnvoyÃ© : mercredi 31 aoÃ»t 2016 12:02 > Ã : pharo-users(a)lists.pharo.org > Objet : [Pharo-users] Network System Settings > > Using Pharo 5.0 with default image. > > I tried configuring proxy settings(to access monticello repositories). As part of > this (via both Welcome window -> settings browser and Systems -> > Settings) > . selected Use HTTP Proxy > . Changed port no. > . Set the proxy server name > . Added exception patterns > Then > . Clicked on Store settings. > get a pop up informing the the settings have been stored to disk. > At this point the text input fields still have yellow highlight showing it has not > been saved. > Now I try to open a repository. This fails saying the connection to > 0.0.0.0:80 has timed out. Which means both the server name and port are not > being used. > > How can i fix this ? > > Regards, > Bharat > > > > > > -- > View this message in context: http://forum.world.st/Network-System-Settings- > tp4913359.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Aug. 31, 2016

Re: [Pharo-users] Network System Settings

by Nicolai Hess

Accept the change when editing the values. Am 31.08.2016 12:05 nachm. schrieb "bharath" <bshetty(a)gmail.com>: > Using Pharo 5.0 with default image. > > I tried configuring proxy settings(to access monticello repositories). As > part of this (via both Welcome window -> settings browser and Systems -> > Settings) > . selected Use HTTP Proxy > . Changed port no. > . Set the proxy server name > . Added exception patterns > Then > . Clicked on Store settings. > get a pop up informing the the settings have been stored to disk. > At this point the text input fields still have yellow highlight showing it > has not been saved. > Now I try to open a repository. This fails saying the connection to > 0.0.0.0:80 has timed out. Which means both the server name and port are > not > being used. > > How can i fix this ? > > Regards, > Bharat > > > > > > -- > View this message in context: http://forum.world.st/Network- > System-Settings-tp4913359.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 31, 2016

Network System Settings

by bharath

Using Pharo 5.0 with default image. I tried configuring proxy settings(to access monticello repositories). As part of this (via both Welcome window -> settings browser and Systems -> Settings) . selected Use HTTP Proxy . Changed port no. . Set the proxy server name . Added exception patterns Then . Clicked on Store settings. get a pop up informing the the settings have been stored to disk. At this point the text input fields still have yellow highlight showing it has not been saved. Now I try to open a repository. This fails saying the connection to 0.0.0.0:80 has timed out. Which means both the server name and port are not being used. How can i fix this ? Regards, Bharat -- View this message in context: http://forum.world.st/Network-System-Settings-tp4913359.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 31, 2016

Re: [Pharo-users] [Moose-dev] [ann] pillar support in gtinspector

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 31/08/16 08:52, stepharo wrote: > I do not get how you can write a PhD in a system that does not support > > - footnote > > - citation > > - figure reference. > > Pillar supports all that. > Pandoc's markdown support all that. I need zotero bibliography integration by using @keys. I started writing my thesis using them and I have already markdown documents with yaml metablocks and other pandoc features. I need compatibility with my own past and bridges with other practices/tech beyond pharo community (here at hackademia nobody is using Pillar markup, but they're using Pandoc's markdown now and have PhD documents already wrote on that, like me). > >> I wouldn't image that giving syntax highlighting support for markdown >> in Pharo could be that hard, but I can write the thesis without it, >> using just black text anywhere. Anyway having syntax support for >> another languages is something that is being done for software >> analysis, so, maybe at some point I can just try to learn how is >> being done with Petit Parser o Smacc and see if I can help to create >> a more markdown friendly environment in Pharo. > I do not see the point > I do not get why after all the efforts we are doing around Pillar and > the proof that we can use it for making so great > output people want markdown. Sorry but do not expect us to do anything > in that direction. > I'm good with that, as soon as the community doesn't discourage any *individual* attempt to support any other markup language on the world. For me would be like not supporting git because community has invested a lot on effort on monticello and it is what community is doing right now. I don't even like git, and rant against it, but I think that this work is valuable and strategic. The only thing I don't want is getting git into my way, but the work Nico is doing in that direction seems really promising. Python has reST as default, but not as the only markup in the world it support for documentation. There is some other stuff beyond what we're using and support it is a way to get more people interested in Pharo, not less. Cheers, Offray

Aug. 31, 2016