>>Stephane a ecrit:
>> TIFFImage has a class method
>> TIFFImage fromFileNamed: aString
>>         ^self fromFile: (Filename named: aString)
>>
>> where Filename doesn't exist as a class.

Bruce Badger wrote:
"Filename is a class in VisualWorks.  The idea is that this class
understands the symbolic identifiers for file - i.e. file names.
Other classes are used to access files in VisualWorks, the FileStream
subclasses in fact.  The classes supporting files in Squeak are quite
different."

"More recently I have put together the Sport library with the aim of being
able to write most code to a consistent portable >interface (that of Sport)
and then have different implementations of Sport for each dialect.  Sport is
a kludge, though.  What I'd really like to see the the Smalltalk ANSI
standard moved along to include 	file classes ...and all the other
things in Sport.  But that won't be happening for a while, I fear.  In the
short term the SPDF library should be changed to use Sport 	so we have a
single SPDF implementation that works with all Smalltalk dialects, but I
certainly don't have spare volunteer time to look at that.  I could find
time in 	my professional (i.e. paid for) calendar, and indeed I do
sometimes get paid to do things with the SPDF library - but not often, and
not lately."

Another option for inter-Smalltal portability is the Passport library that I
developed in order to make Chronos work on VisualWorks, Squeak and Dolphin.
It provides the class ResourcePath, which is similar in many ways to VW's
Filename class.

For more information, see my recent blog post on Passport:
http://chronos-st.blogspot.com/2007/01/filenames-and-inter-smalltalk.html