[Pharo-project] Unicode depending on Zinc

Stéphane Ducasse stephane.ducasse at inria.fr
Fri Mar 16 07:14:44 EDT 2012


I would prefer to have a method that contains this data.
Because any 
	Smalltalk at:….
		will lead to dead code when ring is not loaded.

Stef


On Mar 16, 2012, at 12:18 AM, Guillermo Polito wrote:

> That's why I generated a method from the file, and then put the link in the comment...
> 
> On Thu, Mar 15, 2012 at 8:17 PM, Guillermo Polito <guillermopolito at gmail.com> wrote:
> But what if I want to have an image without Zinc?  Ok, I will not use that method, but I'll get an Undeclared entry and therefore a dirty image... :/
> 
> 
> On Thu, Mar 15, 2012 at 12:37 PM, Sven Van Caekenberghe <sven at beta9.be> wrote:
> Hi Guillermo,
> 
> On 15 Mar 2012, at 16:25, Guillermo Polito wrote:
> 
> > Of course with a nice comment saying something like:
> >
> > "Initialize the mappings from unicode lower to upper case and vice versa.  sourceCodes and destinyCodes contains the unicode values for the mappings, and they match one by one.
> > The source of this mapping can be found at: http://www.unicode.org/Public/UNIDATA/CaseFolding.txt' "
> 
> Have a look at what I did with http://code.google.com/p/pharo/issues/detail?id=4187
> 
> The spec tables are constants, like in your latest example, but I added a method that can generate these from an internet accessible resource (using Zn as HTTP client). That way, there is some kind of dependency, but not really at run time. I think it is cool to literally use these public spec documents.
> 
> Sven
> 
> 
> 





More information about the Pharo-dev mailing list