bornstein at designeq.com
Sat Jun 1 11:08:01 CDT 2002
>the size difference could be because the original files had resource forks
>that aren't being copied?
Yes, it turns out that this is exactly the case.
>the URL method could be slow because, even though you're not copying all
>the URLs into a variable and then putting it into a URL, using URL
>commands might mean each time through the engine parses through the entire
>file to find "after"
This also seems correct, as the process starts out reasonably fast and
then slows down more and more as it's copying files. So the URL method
isn't the preferable one for concactenating files. Fortunately
OPEN/READ/WRITE doesn't seem to suffer from this problem.
D E S I G N E Q
More information about the use-livecode