- Pharo-dev - lists.pharo.org

[Pharo-project] ConfigurationOfVMMaker updated

by Torsten Bergmann

I've updated the newest development version 1.4 of ConfigurationOfVMMaker so it loads well in latest Squeak 4.1., Squeak trunk, Pharo 1.0 and Pharo 1.1. and uses the latest packages available. Tested on all four platforms. Note that version 1.4 is still blessed with #development in the Metacello spec. What is new =========== - world menu registration works also in Pharo 1.1. - switch to the new SqS/FreetypePlugin for the Squeak part (see Squeak bug 7521) - include latest packages available for VM building For Squeak evaluate: ---------------------------------------------------------------------- Installer squeaksource project: 'MetacelloRepository'; install: 'ConfigurationOfVMMaker'. ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4') load ---------------------------------------------------------------------- For Pharo evaluate: ---------------------------------------------------------------------- Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfVMMaker'; load. ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4') load ---------------------------------------------------------------------- Always remember that Metacello allows you to load newest packages (if they appear) by loading the baseline. Here you can use: ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4-baseline') load What is open ============ VMMaker still has - #fixTemps - deprecated #findLastOccuranceOfString: vs. findLastOccurenceOfString: - ... that could be cleaned up if all VM Builders switch to the latest Squeak and Pharo releases. We should really move forward here! Does anyone still use old Squeak 3.6/3.8 to build the VM? What do you think? Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

May 26, 2010

Re: [Pharo-project] old method #withInheritanceTraitCompositionIncludes: , equivalence?

by StÃ©phane Ducasse

create a bug entry so that we do not forget to have a look at it, may be adrien remove it during his cleaning. Stef > > I donÂ´t know if is important. Perhaps no. I use it for know if a instance > have in some class parent the use of a trait. > > Always I could use the same code from old method. > > Regards. > -- > View this message in context: http://forum.world.st/old-method-withInheritanceTraitCompositionIncludes-eq… > 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

May 26, 2010

Re: [Pharo-project] #and:and:and: deprecated on 1.1, why?

by StÃ©phane Ducasse

reasons - and:and:and: is only used in squeak totally not portable. (we could live with that) - and: is optimized by the compiler - and:and: are not optimized is it ok? Stef On May 26, 2010, at 10:10 AM, nullPointer wrote: > > But I donÂ´t understand why the methods #and:and:and: AND #and:and:and:and: > must be deprecateds... what is the equivalence now for that messages? is > possible create a #&& and #|| messages? > > Regards > -- > View this message in context: http://forum.world.st/and-and-and-deprecated-on-1-1-why-tp2230786p2231198.h… > 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

May 26, 2010

[Pharo-project] plan for 1.1

by StÃ©phane Ducasse

Hi guys we were discussing how we can handle 1.1 and the flux of good changes. Here is the proposal: we take two or three weeks to let people try their code in 1.1 beta we integrate fixes that are important or easy then we wait one week then we launch 1.1 rc and 1.2 unstable does this plan look ok for you? The key point is that we want to avoid to have a pile of changes pending because they can rot easily. Stef

May 26, 2010

Re: [Pharo-project] FFI Documentation

by Igor Stasenko

On 26 May 2010 01:58, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Sig, > > *nix/mac is **essential** - otherwise, we are not cross-platform. Â What is involved in writing the interfaces? Â I fear it is a little out of my league, but you have my attention :) > > You mentioned that anything can be done because one can use native code: true enough and a strength, but I don't want to be forced to resort to it, especially for simple things. Â In fact, therein might lurk a weakness of Alien; IIRC, the author(s) of its documentation declined to boast of its call-out capabilities, leaving me wondering whether one is left to manage the stack rather than having the callout mechanism do it. > > I am working on a wrapper for the Gnu Scientific Library. Â Given the unix code, I could take a shot at transforming my code to use it. Â If you have callbacks, I would have a big reason to dive into it. Â As it is, I am working around the need for callbacks, but it will eventually become unavoidable. Â One thing I am considering for curve fitting is to create a .so with a large number of suitable functions whose addresses can be obtained and given to the library. Â Ultimately, we need callbacks though. > For porting it onto other platform, the basic procedure is following: - subclass NativeBoost class - implement a bootstrap routines: #pointerSize #newAssembler #initializeExternalHeap #generateCallgateCode #basicAllocate: aSize on Win32 i am using a HeapCreate/HeapAlloc kernel functions for working with extenal heap. On unixes same functionality could be provided by mmap + own heap management code, or, link with some library, which provides a basic heap operations (allocate/free) on a heap with execution enabled. The main feature, what a platform-specific code should provide is to enable putting a native code into external heap so, other NB parts could be able to make calls to it. This means that memory, which allocated by calls to NativeBoost>>allocate: should always have an execution enabled. http://linux.die.net/man/2/mmap http://linux.die.net/man/2/mprotect > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko > Sent: Tuesday, May 25, 2010 4:51 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] FFI Documentation > > 2010/5/25 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: >> I too am waiting to find something about NB that we should not like. >> No offense to Sig, there has to be _something_ wrong with it, right? >> :) >> > Right. :) > Wrong, is lack of Unix and mac support. It should be written. > > Examples is missing too. > >> A draft list of stuff we should check: >> >> (1) many examples of calls with int, float/double, pointers, structs, etc. >> (2) mac, Linux, Windows >> (3) callbacks >> >> Bonus: >> (4) calls on separate OS threads so the image can defend itself >> against something that does not return in a "reasonable" time, with >> reasonable being up to either the programmer or the end user (which >> the programmer can hopefully enforce if the image is not locked). >> >> Bill >> >> >> >> ________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >> Denis Kudriashov >> Sent: Tuesday, May 25, 2010 1:08 PM >> To: Pharo-project >> Subject: Re: [Pharo-project] FFI Documentation >> >> Hi. Igor >> >> Can you compare NB callout functionality with FFI and Alien functionality. >> Can NB replace FFI, Alien? >> >> What absent in NB callout? >> >> You implement callbacks with NB. FFI not support it. >> For me NB foreign interface seems more attractive than something else. >> >> >> 2010/5/21 Igor Stasenko <siguctua(a)gmail.com> >>> >>> Very nice topic coverage. I hope, eventually NB will also have >>> something like this :) >>> >>> But it having a little different pros/cons table: >>> >>> NB Pros: >>> Â Â Â Â Â Â Â * as well as for plugin, you can create new >>> functionality that doesn't exist in any library >>> Â Â Â Â Â Â Â * no need to recompile plugin/VM when you making a >>> changes >>> Â Â Â Â Â Â Â * all your code is distributed with the Smalltalk code, >>> but there can be complications with platforms >>> Â Â Â Â Â Â Â * fast - faster than any FFI implementation written in >>> C, and as fast as plugin primitive or even faster >>> >>> Â Â Â Cons: >>> Â Â Â Â Â Â Â * ?unsafe? - you have to provide a safety layers >>> Â Â Â Â Â Â Â (But hey, you have to deal with same sorts of stuff, >>> when writing plugin. No magician workers there) >>> >>> Â Â Â Â Â Â Â * harder to write >>> Yes, its harder than plain smalltalk - true. >>> But i can't say, that writing an assembler is harder than writing a >>> plugin's slang code. >>> If you writing a plugin, you should have an expertise, in VM >>> internals and how to build VM , etc etc and if you writing an native >>> code, you should have an expertise in assembler as well as VM >>> internals. >>> >>> So, they are different, and definitely much harder comparing to plain >>> smalltalk code, but which one is easier is hard to tell. >>> >>> On 20 May 2010 22:25, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> > thanks sean >>> > this is cool to see such kind of documentation emerging. >>> > >>> > Stef >>> > >>> > On May 20, 2010, at 9:16 PM, Sean P. DeNigris wrote: >>> > >>> >> >>> >> I want to get this info into the help system and/or collaborative >>> >> book, as similar questions pop up regularly on the lists. >>> >> >>> >> I compiled every piece of info I could find. Â The focus in on FFI, >>> >> with stubs for other strategies. Â Please read this *very* rough >>> >> outline for missing info and inaccuracies: >>> >> >>> >> FFI >>> >> >>> >> What is FFI and what is it used for? Â Calling functions in >>> >> libraries outside of the image... >>> >> >>> >> FFI, the Squeak Foreign Function Interface, is used to call >>> >> functions located in shared libraries that are not part of the >>> >> Squeak VM nor its plugins. It also provides means to read and >>> >> write memory structures that are associated with the use of those >>> >> shared libraries. A typical use is to directly invoke operating >>> >> system APIs. As such, applications that use FFI can only be used >>> >> on the platform(s) that support the particular API being used. C >>> >> conventions are used throughout, though the external function >>> >> could have been written by any language capable of generating >>> >> object code that follows C conventions. Â FFI is probably the >>> >> easiest way to do the things it does. FFI is pretty fast too. >>> >> Croquet uses FFI calls to OpenGL for all it's drawing routines.[1] >>> >> >>> >> How does FFI work? >>> >> Technically what happens is: >>> >> * you define what the interface is - the parameters, types etc. >>> >> * when you make the call, the FFI logic assembles the data from the >>> >> Squeak >>> >> Objects into the proper structures according to the routine calling >>> >> conventions for your architecture, and of course manages the return >>> >> values. >>> >> So no magic but perhaps just a little assembler in the plugin to >>> >> properly >>> >> deal with all the registers and condition flags. >>> >> >>> >> How do I use it? >>> >> >>> >> 1. make a method (whose structure is similar to a named primitive >>> >> method) >>> >> >>> >> Example: >>> >> system: aString "name (by convention is apiXxx: e.g. apiSystem:)" >>> >> >>> >> Â Â Â <apicall: long 'system' (char*) module: 'libSystem.dylib'> "first >>> >> line >>> >> should be the external function specification" >>> >> Â Â Â ^self externalCallFailed. >>> >> >>> >> Let's take it piece by piece: >>> >> >>> >> Â Â Â system: aString >>> >> Â Â Â Â Â Â Â Method name - by convention named 'apiXxx' >>> >> >>> >> Â Â Â <apicall: long 'system' (char*) module: 'libSystem.dylib'> >>> >> Â Â Â Â Â Â Â Function specification >>> >> Â Â Â Â Â Â Â Â Â Â Â - should be the first line >>> >> Â Â Â Â Â Â Â Â Â Â Â - enclosed in angle brackets: < > containing: >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 1. Calling Convention, either apicall: >>> >> (Pascal convention) or cdecl: (C >>> >> convention) >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - Mac - use either one >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - Unix - use cdecl >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - Windows - use apical >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 2. Return Type (see types) >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 3. External Function Name (literal >>> >> string) >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 4. Argument Types (a literal array) >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 5. Module - "module: " + [filename of the >>> >> external library (literal >>> >> string)] (see below). >>> >> >>> >> Â Â Â self externalCallFailed. >>> >> Â Â Â Â Â Â Â Failure handler >>> >> Â Â Â Â Â Â Â Â Â Â Â - normal smalltalk code >>> >> Â Â Â Â Â Â Â Â Â Â Â - executed if the linking to or calling the >>> >> external function fails >>> >> Â Â Â Â Â Â Â Â Â Â Â - API calls don't know how to communicate failure >>> >> like Squeak primitives >>> >> do, so: >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - it does not tell you whether the >>> >> external function succeeded >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - the most common code is simply '^self >>> >> externalCallFailed.' >>> >> >>> >> Argument Types >>> >> Â Â Â - must be names of ExternalTypes, either: >>> >> Â Â Â Â Â Â Â - atomic types (see ExternalType >>> >> class>>initializeFFIConstants and >>> >> ExternalType class>>initializeAtomicTypes): >>> >> Â Â Â Â Â Â Â Â Â Â Â void >>> >> Â Â Â Â Â Â Â Â Â Â Â bool >>> >> Â Â Â Â Â Â Â Â Â Â Â byte (unsigned) >>> >> Â Â Â Â Â Â Â Â Â Â Â sbyte (signed) >>> >> Â Â Â Â Â Â Â Â Â Â Â ushort (16-bit unsigned) >>> >> Â Â Â Â Â Â Â Â Â Â Â short (16-bit signed) >>> >> Â Â Â Â Â Â Â Â Â Â Â ulong (32-bit unsigned) >>> >> Â Â Â Â Â Â Â Â Â Â Â long (32-bit signed) >>> >> Â Â Â Â Â Â Â Â Â Â Â ulonglong (64-bit unsigned) >>> >> Â Â Â Â Â Â Â Â Â Â Â longlong (64-bit signed) >>> >> Â Â Â Â Â Â Â Â Â Â Â char (unsigned) >>> >> Â Â Â Â Â Â Â Â Â Â Â schar (signed) >>> >> Â Â Â Â Â Â Â Â Â Â Â float (single-precision float) >>> >> Â Â Â Â Â Â Â Â Â Â Â double (double-precision float) >>> >> >>> >> Structure Types [4] >>> >> Â Â Â - subclass of ExternalStructure >>> >> Â Â Â Â Â Â Â - class>>fields that returns an array of field >>> >> descriptions (see below) >>> >> Â Â Â Â Â Â Â Â Â Â Â - Example: >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â fields >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^#((red Â 'byte')(green >>> >> 'byte')(blue Â 'byte')) >>> >> Â Â Â Â Â Â Â - class>>initialize which includes "self defineFields" >>> >> (which must be >>> >> called before using the class) >>> >> Â Â Â - refer to as MyExternalStructure* (to indicate that the argument >>> >> or return >>> >> is a pointer to that structure) >>> >> >>> >> Field description [4] >>> >> Â Â Â - 2-element array (or three but that does something else, I'm not >>> >> sure >>> >> what): >>> >> Â Â Â Â Â Â Â - first element is the field name >>> >> Â Â Â Â Â Â Â - second is the type >>> >> >>> >> Mac Memory Allocation Issues [4] (not sure about this) >>> >> >>> >> If you allocate external structures, those with memory outside the >>> >> Squeak >>> >> process space, you may need to increase the amount of memory that is >>> >> reserved outside the object heap for such use. The Mac OS (9 and >>> >> previous) >>> >> needs this, other platforms may be able to dynamically get more memory >>> >> from >>> >> the OS. To see how much memory is currently reserved printIt 'Smalltalk >>> >> extraVMMemory'. To change it, execute 'Smalltalk extraVMMemory: >>> >> someNumberofBytes' Then save your image and quit. When you next start >>> >> up, >>> >> the amount of memory you requested will be reserved. (JMM) Note the OSX >>> >> versions of the VM ignore extraVMMemory because the memory model for >>> >> OS-X/unix applications is quite different. >>> >> >>> >> Module Name >>> >> - depends on the platform >>> >> Â Â Â - Mac >>> >> Â Â Â Â Â Â Â - pre Snow Leopard: flexible, can eliminate leading lib >>> >> or extension e.g. >>> >> 'libc.dylib' becomes 'libc', 'c.dylib', or 'c' >>> >> Â Â Â Â Â Â Â - Snow Leopard >>> >> Â Â Â Â Â Â Â Â Â Â Â - file name must be exact including extension >>> >> (unless Info.plist is >>> >> altered as in 'Library Location' below) >>> >> Â Â Â Â Â Â Â - With pre-mach-o VMs >>> >> Â Â Â Â Â Â Â Â Â Â Â - For Classic applications, use 'InterfaceLib' >>> >> Â Â Â Â Â Â Â Â Â Â Â - For Carbon libs, use 'CarbonLib' >>> >> >>> >> Module Location - where the external library file lives >>> >> Â Â Â - depends on the platform >>> >> Â Â Â Â Â Â Â - Mac >>> >> Â Â Â Â Â Â Â Â Â Â Â - pre Snow Leopard >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - checks VM path and common library paths >>> >> Â Â Â Â Â Â Â Â Â Â Â - Snow Leopard >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - only looks in VM bundle's Resources >>> >> file, you must either [5]: >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - store all external libraries >>> >> there >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - ln -s path/to/library >>> >> path/to/VM/Resources/library_name >>> >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - Change the VM's Info.plist >>> >> "SqueakPluginsBuiltInOrLocalOnly" key from >>> >> "true" to "false." >>> >> Caveats >>> >> Â Â Â - security >>> >> Â Â Â Â Â Â Â - malicious users could call arbitrary functions in the >>> >> OS e.g. Â "format >>> >> c:" from "system.dll" [7] >>> >> Â Â Â Â Â Â Â - VMs do not protect against buffer overflow from bad >>> >> parameters [8]: >>> >> Â Â Â Â Â Â Â Â Â Â Â "this would require an attacker to execute >>> >> arbitrary Smalltalk >>> >> Â Â Â Â Â Â Â Â Â Â Â code on your server. Of course if they can do >>> >> that they own you >>> >> Â Â Â Â Â Â Â Â Â Â Â anyway, especially if you allow FFi or use the >>> >> OSProcess plugin" - John >>> >> McIntosh >>> >> >>> >> * difficulty >>> >> Â Â Â - if you make a mistake you'll not drop into the debugger but >>> >> Squeak will >>> >> just crash [2] >>> >> Â Â Â - If you crash Squeak when it is running the garbage collector, >>> >> then you >>> >> know your FFI code is leaking bits into object memory [2] >>> >> >>> >> What do I need to use FFI with Squeak? >>> >> >>> >> You need the FFI plugin, which is included with most VM's as of Squeak >>> >> 3.6 >>> >> or so. >>> >> >>> >> You can also build the plugin yourself. See VMMaker. >>> >> >>> >> References: >>> >> [1] http://wiki.squeak.org/squeak/1414 >>> >> [2] http://wiki.squeak.org/squeak/2424 >>> >> [3] http://wiki.squeak.org/squeak/5716 >>> >> [4] http://wiki.squeak.org/squeak/2426 >>> >> [5] >>> >> >>> >> http://forum.world.st/squeak-dev-Alien-Squeak-FFI-issues-on-Snow-Leopard-td… >>> >> [6] http://wiki.squeak.org/squeak/5846 >>> >> [7] http://forum.world.st/FFI-Callbacks-td54056.html#a54073 >>> >> [8] http://forum.world.st/Security-td99624.html#a99635: >>> >> >>> >> Other choices: >>> >> In the fall of 2008, Alien the FFI interface (written by Cadence Design >>> >> Systems, Inc.) was put into squeaksource: >>> >> http://www.squeaksource.com/Alien.html. This API allows the primitive >>> >> to >>> >> call back to Smalltalk Code, and return error code information, and >>> >> apparently is much faster due to a less complex call sequence. >>> >> Â Â Â * if you need callbacks >>> >> Â Â Â * mac-only? >>> >> >>> >> Plugins - write external code and dynamically link it to the VM >>> >> Â Â Â Pros: >>> >> Â Â Â Â Â Â Â * safest - users are limited to using the functionality >>> >> you provide and >>> >> can not call other external functions e.g. system rm / >>> >> Â Â Â Â Â Â Â * fast - faster than FFI >>> >> Â Â Â Â Â Â Â * you can create new functionality that doesn't exist in >>> >> any library >>> >> Â Â Â Cons: >>> >> Â Â Â Â Â Â Â * harder to write >>> >> Â Â Â Â Â Â Â * plugin must be distributed with the Smalltalk code - >>> >> there can be >>> >> complications with platforms >>> >> >>> >> Primitive method - invokes behavior in the VM or a plugin [3] >>> >> >>> >> Questions: >>> >> * why would you want to build the FFI plugin yourself? >>> >> * api prefix or no for method names? >>> >> * not sure about pre Snow Leopard library search >>> >> * OSProcess - how does this fit into the bigger picture? >>> >> * "^self externalCallFailed." or "self externalCallFailed." i.e. return >>> >> self >>> >> or return the result, or doesn't matter? >>> >> * why would a field description have three elements? >>> >> * Mac Memory Allocation Issues? >>> >> -- >>> >> View this message in context: >>> >> http://forum.world.st/FFI-Documentation-tp2225148p2225148.html >>> >> 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 >>> > >>> > >>> > _______________________________________________ >>> > 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 >> >> _______________________________________________ >> 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 > > _______________________________________________ > 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.

May 26, 2010

Re: [Pharo-project] old method #withInheritanceTraitCompositionIncludes: , equivalence?

by nullPointer

I donÂ´t know if is important. Perhaps no. I use it for know if a instance have in some class parent the use of a trait. Always I could use the same code from old method. Regards. -- View this message in context: http://forum.world.st/old-method-withInheritanceTraitCompositionIncludes-eq… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 26, 2010

Re: [Pharo-project] #and:and:and: deprecated on 1.1, why?

by nullPointer

But I donÂ´t understand why the methods #and:and:and: AND #and:and:and:and: must be deprecateds... what is the equivalence now for that messages? is possible create a #&& and #|| messages? Regards -- View this message in context: http://forum.world.st/and-and-and-deprecated-on-1-1-why-tp2230786p2231198.h… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 26, 2010

Re: [Pharo-project] [update 1.1] #11371

by Mariano Martinez Peck

The problem is that Adrian said and more: 1) Update stream only manages Core packages. The packages you have in the Core image that are found in the Pharo squeaksource repository. PharoDev is build on top of PharoCore and loads external packages which have their own maintainers. 2) When we change something in PharoCore, suppose we rename or remove a method, all senders are fixed for example. Here the scope is Core, not external packages. This is a task of the external packages developers. 3) When you update your image, it will bring the new version of the new package. Now...suppose the update stream renamed the method String >> contact: to contactTo: The fixes of core packages will be automatically updated. But what happens with the external code that was using (senders) contact: ?? -> lots of DNU Even worst...the overrides. Most of the times, they are evil, but they still exist. Suppose an external package XXX that defined String >> contact: with category *XXX and do something different. When you load such package, the method is overridden. But then, if you update a new version of such package from the update stream, it will be put again the original one. This leads problems difficult to debug and trace. All these continues with people reporting problems, people trying to debug and understand problems...etc....in summary: a wast of time. PharoDev are quite periodically. So, wait and get a new version of the Dev image. Maybe in a future this whole thing may be fixed and the update stream can handle external dependencies too, but I think this is not very easy. Cheers Mariano On Tue, May 25, 2010 at 11:11 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > not really :) > we prefer to keep it but that the user cannot use it by accident. > > Stef > > On May 25, 2010, at 11:07 PM, Guillermo Polito wrote: > > > Should that method be deprecated in the current Dev Image so no one makes > a mistake? I don't know how the current "branches" are mantained to allow > something like that... :/ > > > > 2010/5/25 Carla F. Griggio <carla.griggio(a)gmail.com> > > :O > > So I guess that's why it actually didn't update anything... :P > > > > > > On Tue, May 25, 2010 at 5:15 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > > The reason why we have turned it off is because updating Pharo images > repeatedly caused problems (in contrast to PharoCore). People then reported > issues. Unless this feature is working properly, we shouldn't enable it > again. One possible cause of the problems are overrides by external packages > in core code. But I think nobody has analyzed the problem in depth so far. > > > > Cheers, > > Adrian > > > > > > On May 25, 2010, at 21:48 , Carla F. Griggio wrote: > > > > > That annoyed me too. Shouldn't that option be checked by default? > > > > > > On Tuesday, May 25, 2010, laurent laffont <laurent.laffont(a)gmail.com> > wrote: > > >> World Menu -> System -> Software Update > > >> Cheers,Laurent Laffont > > >> > > >> http://pharocasts.blogspot.com/ > > >> http://magaloma.blogspot.com/ > > >> > > >> > > >> 2010/5/25 Guillermo Polito <guillermopolito(a)gmail.com> > > >> > > >> > > >> I'm sorry but i can't find how to update my 1.1 image. Can I update my > image with this changes? Can someone enlight me? :) > > >> > > >> Guille, the newbie > > >> > > >> > > >> > > >> On Mon, May 24, 2010 at 5:16 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > >> 11371 > > >> ----- > > >> - Issue 1281: Button in TestRunner to fileout the test results. Thanks > Laurent. > > >> - Issue 2468: Better method trailer method creation. Part One. Thanks > Igor. > > >> - Issue 2406: MovieMorph should be removed from the core. Thanks > Alain. > > >> - Issue 2467: AlllocationTest#testOutOfMemorySignal fails. Thanks > Laurent > > >> - Issue 2331: Reuse test unload - Now there is an SUnitUnloader. > Thanks Guillermo. > > >> > > >> Stef > > >> _______________________________________________ > > >> 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 > > > > _______________________________________________ > > 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 >

May 26, 2010

Re: [Pharo-project] Problem with Demo mode [WAS] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by StÃ©phane Ducasse

ok good to know. may be we should get a fallback for a mac demo mode :) Stef On May 26, 2010, at 9:43 AM, Serge Stinckwich wrote: > It look likes the problem is related to the fact that Deja Vu fonts is > only in 9 and 12pt under Mac OS X. > > On Mon, May 24, 2010 at 11:02 PM, Alain Plantec <alain.plantec(a)free.fr> wrote: >> Le 24/05/2010 16:53, Mariano Martinez Peck a Ã©crit : >>> >>> >>> On Mon, May 24, 2010 at 11:56 AM, Serge Stinckwich >>> <serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com>> wrote: >>> >>> When i switch to demo mode, method selector in System Browser are no >>> more bold in the bottom pane. >>> >>> >>> I didn't understand you. Could you please attach both screenshots: how it >>> should be and how is it ? >>> >>> Alain do you know about this ? >> >> Hi, >> Strange, I've tested and all is ok here. >> could you try with >> -------- >> StandardFonts setDemoFonts >> -------- >> >> Alain >>> >>> Cheers >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 26, 2010

Re: [Pharo-project] Problem with Demo mode [WAS] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Serge Stinckwich

It look likes the problem is related to the fact that Deja Vu fonts is only in 9 and 12pt under Mac OS X. On Mon, May 24, 2010 at 11:02 PM, Alain Plantec <alain.plantec(a)free.fr> wrote: > Le 24/05/2010 16:53, Mariano Martinez Peck a Ã©crit : >> >> >> On Mon, May 24, 2010 at 11:56 AM, Serge Stinckwich >> <serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com>> wrote: >> >> Â Â When i switch to demo mode, method selector in System Browser are no >> Â Â more bold in the bottom pane. >> >> >> I didn't understand you. Could you please attach both screenshots: how it >> should be and how is it ? >> >> Alain do you know about this ? > > Hi, > Strange, I've tested and all is ok here. > could you try with > -------- > StandardFonts setDemoFonts > -------- > > Alain >> >> Cheers > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

May 26, 2010