- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Newbie question: Connection to SQLite DB

by Schwab,Wilhelm K

I'm not sure I follow your concern. The Win32 examples will certainly fail on other than Win32. I am not even certain if they are currently expected to work on Windows (not simply a dig at its flakiness - it might have changed enough to break something). It looks like one is expected to click a mouse button to terminate the example. Are you matching 32 and 64 bit OS and image/vm? What error do you get? Posting a debug log of it might help. Especially early in Metacello's life, I had big problems with: (1) discovering how to use a given configuration; (2) some configurations were loading things that one might not necessarily want. An example of the latter was ConfiurationOfCitezen, which at one point loaded Seaside; it now does what one would want, leaving it to the user to load the desired version of Seaside. You just prompted me to look at Migrate's various #load* methods, which reveals a few decisions that are no doubt incorrect or at least overly presumptuous. I would pass along the once common advice of "just search the web" but that turns up a very dangerous mix of current and dated links. Make sure you are using the configuration correctly. Sorry if I am missing your point. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of nullPointer [epicfan(a)gmail.com] Sent: Monday, October 04, 2010 8:27 AM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Newbie question: Connection to SQLite DB Well, I first install Sqlite project; I add ConfigurationOfSQLite3 to image. Later: (ConfigurationOfSQLite3 project version: '1.1') load. That seems load Sqlite3 classes and dependences too, FFI included. But if I try execute one example of FFI I get an error. For example: Win32Window win32Draw Now IÂ´m using Windows7 but fails me too Mac Snow Leopard OS... IÂ´m very lost on that subject... Regards -- View this message in context: http://forum.world.st/Newbie-question-Connection-to-SQLite-DB-tp2954195p295… Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ 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] bad bracket autocompletion in Pharo Core 1.2

by Mariano Martinez Peck

I detected a similar problem: once you type an opening parenthesis, and then something else, it adds a new one at the END of the code check http://code.google.com/p/pharo/issues/detail?id=2939 2010/10/6 Guillermo Polito <guillermopolito(a)gmail.com> > http://code.google.com/p/pharo/issues/detail?id=3069 > > if you type: > > [] -> []] > > () -> ()) > > {} -> {}} > > > > Bye! > > _______________________________________________ > 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] Pointer types

by Schwab,Wilhelm K

Sig, Am I correct in taking this as a description of how to solve it with NB, not Squeak/Pharo FFI? That's ok, just want to know if there is an applicable lesson on FFI to be extracted. You say the NB callout generator knows nothing about types. Is that how it should be? The scenario I have in mind is a bogus type and whether that can/should be flagged at compile time vs. runtime. Maybe all it takes is a scan for a suitable handler before or after the method is compiled. I ask because I hit a related snag with FFI runtime errors being reported as coercion errors when in fact I had used errant types in the callout definitions. IIRC, Andreas patched the compiler to report the bogus types. "Or, if you want make double* type to use it as a DoubleArray, then you can add an alias: MyClass>>externalTypeAlias: aTypeName aTypeName = 'double*' ifTrue: [ ^ #DoubleArray ]. ^ nil Then, any method which contains an FFI callout in MyClass, will use that alias." What is MyClass in the above? Is it the class holding the callout method, or it elsewhere in the chain? I ask because it could be a sore spot for maintenance/pluggability. I'm wondering how you and I would independently add such instructions. If it goes in the external type subclass, then it is probably fine; if it goes in a class that makes the call, we might stomp on each other. Make sense? My hunch is that you have it handled. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua(a)gmail.com] Sent: Monday, October 04, 2010 7:36 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Pointer types On 4 October 2010 06:15, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Sig, > > You mentioned something that might be useful, depending on where it lives. Our ability to use underscores now leaves me thinking I really should rework some things that suffered mightily: there are some external things that are named assuming underscores, and in mixed case, they turn into an unreadable mess. Along with this, I have a large number of FFI calls that take double pointers, and I have for some time been demoralized into (or stupid enough to<g>) expressing them as void pointers to allow me to pass byte arrays into them. > > Is there a way that I can get FFI to recognize DOUBLEArray (which uses a ByteArray to hold its data) as something that should be acceptable for a double* call? If not FFI, how does NB handle it? > In NB, there is a type system, which implements C<->Smalltalk coercions. The responsibility of type coercions taken by a subclasses of NBExternalType, so NB callout code generator actually knows nothing about types and how to coerce them. To create own custom type, you need to subclass from NBExternalType and override methods which responsible for coercions. There you can define any kind of operations , what needs to be done in order to push value on stack, or convert it to some smalltalk object. Then, in your DoubleArray class, simply implement a message on a class side: asNBExternalType: gen ^ MyDoubleArrayExternalType new And then, in FFI callouts you can use a class name directly: DoubleArray foo (DoubleArray arr, DoubleArray * arrPtr) etc. Or, if you want make double* type to use it as a DoubleArray, then you can add an alias: MyClass>>externalTypeAlias: aTypeName aTypeName = 'double*' ifTrue: [ ^ #DoubleArray ]. ^ nil Then, any method which contains an FFI callout in MyClass, will use that alias. So, you can write callout as: double* foo (double *arr, double ** arrPtrPtr) but it will be understood as: DoubleArray foo (DoubleArray arr, DoubleArray * arrPtr) About handling pointers.. well for smalltalk there is no pointers, just objects. So, in NB NBExternalType keeps two things: - a value type - a pointer arity So, for example, when you specifying type, like: char *** a value type will be char and pointer arity will be 3. It is up to NBExternalType subclass how to push values whose pointer arity > 0. By default, if pointerArity > 0, then it is treated as a pointer, which can be either: - nil, ByteArray, or NBExternalAddress > Bill > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ 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

On Oct 6, 2010, at 7:18 PM, Eliot Miranda wrote: > > > On Wed, Oct 6, 2010 at 7:31 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > generate a new image. > > But that's not what it does. Yes I know gnerates = clone in my mail. > t merely clones an image, which is a long way form building an image form source. *That*'s a useful project. John Maloney's lovely MicroSqueak is a good starting point for ideas (basically have a copy of a kernel subset of the system in a namespace and generate a fresh image from that). Do you have a pointer on the code of john. We are looking at bootstrap code right now. > > 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 > > > _______________________________________________ > 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] Tests broken with Citezen

by StÃ©phane Ducasse

have a look at the configuration you can pick noWeb. Stef On Oct 6, 2010, at 7:17 PM, Schwab,Wilhelm K wrote: > Damien, > > FWIW, I use Citezen but not Pier etc. I need a good BibTeX parser (which you provide) to parse incoming entries (typically originating from Google Scholar). I then add fields for my own comments (which get edited as I work) and a URL to full text and save the result to intermediate storage. To limit the scope of damage and because it does no harm otherwise, I store each BibTeX entry in a separate file and, on demand, glue them together into a largely unreadable mess (bibtex does fine with it) that I put adjacent to the offending manuscript as a .bib file. > > The way most journals of interest to me release full text articles, the workflow is awful. To not go afoul of copyright law, I store the articles out of public view (and not merely by obscurity). Worse than that, I have to make a local copy of the article and then upload it to the Seaside app, after which things start to work as I intended. I would much prefer to give the Seaside app a URL to the article, but things don't work that way. It's clunky, but the result is very useful to me. > > In short, Citezen is useful by itself, and you have at least one such user. The biggest problem I have had to date was that ConfigurationOfCitezen originally loaded Seaside,which was prematurely forcing 3.0 on me; the current configuration works great. I suspect I won't even notice the change to FileSystem. > > Thanks for a good tool!! > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Damien Pollet [damien.pollet(a)inria.fr] > Sent: Wednesday, October 06, 2010 9:02 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Tests broken with Citezen > > On Wed, Oct 6, 2010 at 14:53, Alexandre Bergel <alexandre(a)bergel.eu> wrote: >> There is no implementor of #fieldKeysToRemove > > yes, probably a missing constant method. > I should also remove the dependency to Rio and use Filesystem instead, > but my next preoccupation is to get the scripting/validation to work. > You're free to hack on the Pier stuff. > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > _______________________________________________ > 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] Re: Smalltalk at: #Foo - needs clarification

by StÃ©phane Ducasse

This is why the image does not use Smalltalk at: but the at: method is still defined in SmalltalkImage. > Stef, > > You raise a good point about helping to improve code, and I would MUCH rather see us try "aClass environment" for a while before introducing name spaces. Dolphin started leaning toward environments a long time ago, and suddenly "class names" were messages to the environment, and I was completely blown away by the potential power of it. I started in 2002 to remove hardcoded Smalltalk at: and replace them by self class environment for the reason that having the possibility to have different systemDictionary instance can help us for: bootstrapping the compiler, building atomic laoding like VW for example. > > So, I'm very open to the idea. However, I don't see any harm in ( Smalltalk at:#SomethingNotYetInstalled ), which I have had to use extensively in Migrate's image building code. Is there a better way to do the same thing? > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua(a)gmail.com] > Sent: Wednesday, October 06, 2010 12:31 PM > To: The general-purpose Squeak developers list > Cc: Pharo Development > Subject: Re: [Pharo-project] [squeak-dev] Re: Smalltalk at: #Foo - needs clarification > > On 6 October 2010 19:08, Andreas Raab <andreas.raab(a)gmx.de> wrote: >> 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. >> > > Yes, i am also thinking that for compatibility it should stay. > > > Then i think in modern code, a most future-proof way is > > self class environment at: #Foo > > since it completely avoids any kind of early-binding. > > >> Cheers, >> - Andreas >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > 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

[Pharo-project] Strange code replacement when prompting unknown selector

by Guillermo Polito

http://code.google.com/p/pharo/issues/detail?id=3070 Cheers! Guille

Oct. 6, 2010

[Pharo-project] bad bracket autocompletion in Pharo Core 1.2

by Guillermo Polito

http://code.google.com/p/pharo/issues/detail?id=3069 if you type: [] -> []] () -> ()) {} -> {}} Bye!

Oct. 6, 2010

Re: [Pharo-project] Bug in Pharo compiler?

by Henrik Sperre Johansen

Hit the button a bit fast there... On 06.10.2010 23:13, Henrik Sperre Johansen wrote: > On 06.10.2010 22:56, James Ladd wrote: >> 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. > The compiler has been changed to be more strict about shadowing inst > vars, but code which has not been since the change was made may still > exist. > ... which has not been altered since the change... > Submit a bug to the tracker mentioning the affected method, and it > will be fixed. Which would be to rename the method argument name, by the way. Cheers, Henry

Oct. 6, 2010

Re: [Pharo-project] Bug in Pharo compiler?

by Henrik Sperre Johansen

On 06.10.2010 22:56, James Ladd wrote: > 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. The compiler has been changed to be more strict about shadowing inst vars, but code which has not been since the change was made may still exist. Submit a bug to the tracker mentioning the affected method, and it will be fixed. Cheers, Henry

Oct. 6, 2010