Some senseless babbling from Peter Knapper to Harry Bush
on 11-24-99  20:29 about Copying files and EA's......

 PK> Hi Harry,
 
 PK> So as far as REXX is concerned, I guess that using 
 PK> SysCopyObject() with full path/filenames for copying 
 PK> over the LAN would probably be reasonably
 PK> safe, as far as copying EA's are concerned?
 
 HB> Do you mean using full path name kinda 
 HB> \\computer\directory\file instead of Object ID?  

 PK> Hmmm, I was actually thinking of copying using drive letters rather
 PK> than a UNC, however I am now not sure that I would want EA's copied in
 PK> all cases..;-) I see others have comented on this also, so I guess I
 PK> need to actually do some tests myself to see what happens.
 PK> For example, the EA's for a REXX script may contain machine specific
 PK> data (EG: drive letters) that would probably need to change on another
 PK> platform. Without EA's REXX would automatically re-build it anyway, but
 PK> if the REXX code HAD to change then there is not much point in copying
 PK> EA's... 

The tokenization code doesn't contain any hard-coded values that aren't
also in the source.

That is, if you don't have the drive letter hard-coded in, but retrieve it
from a function or user input, there's no need to retokenize the code.

Of course, I think the primary point you seem to be trying hard to miss is
that EA's are taken care of automatically, and short of creating a new file
to which you write all of the data from the old file, you can't avoid
copying them when they are capable of being copied.

The upshot is, you're wasting your time thinking about a non-issue.

Mike Ruskai
thannymeister@yahoo.com


... Excuse me, miss?  Miss!?  Sorry, I have a cold.

___ Blue Wave/QWK v2.20
--- Platinum Xpress/Win/Wildcat5! v3.0pr2