G'Day John,
 
-=> Quoting John Gardeniers to Frank Adam <=-
 
 FA> I could ask, why in god's name you don't use system(copy
 FA> ),  but i won't:)
 JG> The answer is that my compiler has nothing like it, although I
Fair enough, lucky i didn't ask :)

 JG> acceptable to PCC.  What I now have is a routine which fully expands
 JG> the source filename but won't (yet) do the same for the destination
 JG> filename. The problem here is with wildcards in the destination.  At
 JG> least I now have a good start and will get back to it as soon as I've
Is it a good idea to allow wildcards in the destination ?
I mean as a simple copy function, especially with the use of '/y' could be 
disastrous.

Suppose a similar sort of algorhythm as my code could be used to build a 
filename, and then both the source and destination paths sent to another 
routine to make the necessary changes to the destination.
Eg: break up the destination string into drv,path,name,ext 
    if(!drv) set default drive or drive defined in sourcepath
    if(!path) same as above 
    if(name contains '*') this will need some thinking
    if(name = '*') set name = sourcename
    if(name contains '?') again this won't be too easy
    same goes for the extension.


I may just play with this, and let you know:)
Does PCC support fnsplit ? It would make your life a bit easier.
                         

  L8r Frank (fadam{at}ozemail.com.au).
                           

--- Maximus 3.01