> On 17 Nov 2018, at 16:04, Hans-Martin wrote:
>
> Hi, I've stumbled upon a 7.0 incompatibility with regards to how file names
> are treated.
> In 6.1, I can use Strings and FileLocators interchangeably to create and
> read Zip archives. That's because StandardFileStream does the magic behind
Ok here's an example:
ZipArchive isZipArchive: FileLocator temp / 'nonexist.zip'
In 6.1, this brings up the nonexistant file dialog if the file does not
exist, otherwise it returns true or false depending on whether the file is a
zip archive.
In 7.0, you get an error "Instance of FileLocator did
ok, I had a quick look.
the whole ZIP archive code has quite close ties with File (and vice versa: a
lot of methods on File are only used by that code), while I don't think this is
strictly necessary.
I know that this has historical reasons.
some more work needs to be done here.
> O
I found a related problem which indicates that the depreciation of
StandardFileStream in favor of File is incomplete and probably premature:
When a ZipArchive is written, in 7.0 it uses
(File named: aFileName)
writeStreamDo: [...]
In 6.1, it uses
StandardFileStream
Hi Hans,
Sorry for the late reply.
On Sun, Nov 25, 2018 at 9:30 PM Hans-Martin wrote:
> I found a related problem which indicates that the depreciation of
> StandardFileStream in favor of File is incomplete and probably premature:
> When a ZipArchive is written, in 7.0 it uses
> (File