Re: including modules during runtime and dealing with OS specific (constants) code block

First, the functions, SetAttributes and GetAttributes, must be specifically requested:

use Win32::File qw(:DEFAULT SetAttributes GetAttributes);
[download]

Second, since you're using Win32::File, it doesn't do any good to try darwin. I eliminated darwin, and I deleted the eval. There was also a problem with &error_dialog being undefined, so I deleted that. Here's what I have so far:


#!perl

BEGIN {
    $|  = 1;
    $^W = 1;
}

use strict;
use warnings;
use Win32::File qw(
    :DEFAULT
    SetAttributes
    GetAttributes
);
        
my $name = '/root/Desktop/foo.txt';
my $attr = 0;

Win32::File::SetAttributes( $name, $attr );
Win32::File::GetAttributes( $name, $attr );
if ( $attr & SYSTEM ) {
    print "$name has SYSTEM set.\n";
}
if ( $attr & HIDDEN ) {
    print "$name is hidden.\n";
}
[download]

Comment on Re: including modules during runtime and dealing with OS specific (constants) code block Select or Download Code

Replies are listed 'Best First'.
Re^2: including modules during runtime and dealing with OS specific (constants) code block by armstd (Friar) on Aug 02, 2011 at 17:26 UTC
First, the functions, SetAttributes and GetAttributes, must be specifically requested: `use Win32::File qw(:DEFAULT SetAttributes GetAttributes);` [download] That would not actually make any difference here. The only difference it would make is allowing this syntax: `GetAttributes()` [download] Instead of this: `Win32::File::GetAttributes()` [download] ...which is not being attempted here. That specification just tells import() what to bring into the current package namespace from the module. The issue in play here is the 'eval', which gives the compiler no idea what will be available at runtime. So it fails at compile time. In your 'fixed' example, it's working not because of your added imports, its working because you removed the 'eval'. --Dave	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: including modules during runtime and dealing with OS specific (constants) code block
by armstd (Friar) on Aug 02, 2011 at 17:26 UTC

First, the functions, SetAttributes and GetAttributes, must be specifically requested:
use Win32::File qw(:DEFAULT SetAttributes GetAttributes);
[download]

That would not actually make any difference here. The only difference it would make is allowing this syntax:

GetAttributes()
[download]

Instead of this:

Win32::File::GetAttributes()
[download]

...which is not being attempted here. That specification just tells import() what to bring into the current package namespace from the module.

The issue in play here is the 'eval', which gives the compiler no idea what will be available at runtime. So it fails at compile time. In your 'fixed' example, it's working not because of your added imports, its working because you removed the 'eval'.

--Dave

[reply]
[d/l]
[select]