Very Computer

Hello All,

Is the only way to copy a file from one directory to another by using the
copy module...?

Would anyone have a snipet of code copying a file from one dir to another...

Any assistance would be appreciated...

Thank you,
Mike

------------------------------------------------

my $result = `cp $file $newfile`;

Or you could do the really tedious, open the file for reading, open the new file for writing, read the contents of the read file and print to the write file, close both files. But why would you want to do that?  Is there a particular reason for avoiding File::Copy?

http://danconia.org

Quote:

> Is the only way to copy a file from one directory to another
> by using the
> copy module...?

> Would anyone have a snipet of code copying a file from one
> dir to another...

> Any assistance would be appreciated...

one example:
--------
use strict;
use File::Copy;

# a bunch of file with foo*
foreach (glob '/home/foo*')
{
        next if ! -f $_;   # copy files only, not directories
        print "Copying $_ ...\n";
        copy ($_, '/where/to') or warn "Failed to copy $_ : $!\n";

Quote:}

link (sourcefile, destination);

Creates a hard link to an existing file. A hard link is a new inode that
points to an existing data stream; that is, it's a duplicate directory entry
for an existing file. The duplicate has a different name and different
permissions and access times. Only the inode field (from the stat function)
is identical to the original.

Quote:

> > Is the only way to copy a file from one directory to another
> > by using the
> > copy module...?

Quote:

> one example:
> --------
> use strict;
> use File::Copy;

> # a bunch of file with foo*
> foreach (glob '/home/foo*')
> {
>         next if ! -f $_;   # copy files only, not directories
>         print "Copying $_ ...\n";
>         copy ($_, '/where/to') or warn "Failed to copy $_ : $!\n";
> }

Quote:> You could shell out to the system
> copy as Wiggins mentioned. But why not use the module ?

Works great...

Have a wonderful weekend..

Mike

If you don't mind, I think there are still some of us that are wondering;
why don't you want to use File::Copy?

/R

Being a Perl nubie....and not having alot of experience in installing and
using Perl modules...I decided to go the route of using the system
function..

I took a look at CPAN and what was involved in installing the module and
using it (was confused)...looked pretty involved..at least for me, rather
than just putting:

system ('copy d:\server\vsiwork\*.tag d:\server\vsiout');

in the code...

Thank you to all who responded...

Regards,
Mike

/R

--

------------------------------------------------

http://danconia.org

Quote:> Tim/Rob/All,

> Being a Perl nubie....and not having alot of experience in installing
> and using Perl modules...I decided to go the route of using the system
> function..

> I took a look at CPAN and what was involved in installing the module
> and using it (was confused)...looked pretty involved..at least for me,
> rather than just putting:

> system ('copy d:\server\vsiwork\*.tag d:\server\vsiout');

> in the code...

Jenda

When it comes to wine, women and song, wizards are allowed
to get drunk and croon as much as they like.
        -- Terry Pratchett in Sourcery

By the way, if you're using ActivePerl (perl -V will tell you)
it's very easy to install pre-built modules with the ppm
utility. Just

    ppm install File::Copy

would have done it if it wasn't already installed.

It might be a good idea, now that you have a working
program, to re-implement it using the module. That way
it won't be so scary next time.

Cheers, and well done,

Rob

Quote:> > Being a Perl nubie....and not having alot of experience in
> > installing and using Perl modules...

> While this may be a valid reason not to use a module it's not
> applicable to File::Copy.
> The module is part of the core, you already have it! Just like
> anybody else.

Try this to check:

  perl -MFile::Copy -e 'print "found\n"'

It will print "found" if it's available, or self-destruct if it's not.
:)

Installs aren't that bad, though.
Start with something simple and nonvital like The Damian's amusing
Acme::Bleach (but don't use it on important code! lol!) and you can't
hurt much. ;o]

__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com

Quote:> system ('copy d:\server\vsiwork\*.tag d:\server\vsiout');

 system qw/ copy d:\server\vsiwork\*.tag d:\server\vsiout /;

or to be more visually explicit for nuB's,

 system ('copy','d:\server\vsiwork\*.tag','d:\server\vsiout');

To be honest, however, on our system the security isn't such an issue,
so I occasionally use the originally given single-string syntax as
well. :)

Since you're obviously on a WinDOZE system, though, make sure you don't
use doublequotes around file paths; "d:\server\vsiwork\*.tag"
interpolates the backslashes, so you end up with a string that looks
like d:servervsiwork*.tag

Luck and fun, bud.
Paul

__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com