/usr/share/perl5/App/Info/Request.pm is in libapp-info-perl 0.57-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 | package App::Info::Request;
=head1 NAME
App::Info::Request - App::Info event handler request object
=head1 SYNOPSIS
# In an App::Info::Handler subclass:
sub handler {
my ($self, $req) = @_;
print "Event Type: ", $req->type;
print "Message: ", $req->message;
print "Error: ", $req->error;
print "Value: ", $req->value;
}
=head1 DESCRIPTION
Objects of this class are passed to the C<handler()> method of App::Info event
handlers. Generally, this class will be of most interest to App::Info::Handler
subclass implementers.
The L<event triggering methods|App::Info/"Events"> in App::Info each construct
a new App::Info::Request object and initialize it with their arguments. The
App::Info::Request object is then the sole argument passed to the C<handler()>
method of any and all App::Info::Handler objects in the event handling chain.
Thus, if you'd like to create your own App::Info event handler, this is the
object you need to be familiar with. Consult the
L<App::Info::Handler|App::Info::Handler> documentation for details on creating
custom event handlers.
Each of the App::Info event triggering methods constructs an
App::Info::Request object with different attribute values. Be sure to consult
the documentation for the L<event triggering methods|App::Info/"Events"> in
App::Info, where the values assigned to the App::Info::Request object are
documented. Then, in your event handler subclass, check the value returned by
the C<type()> method to determine what type of event request you're handling
to handle the request appropriately.
=cut
use strict;
use vars qw($VERSION);
use Carp;
$VERSION = '0.57';
##############################################################################
=head1 INTERFACE
The following sections document the App::Info::Request interface.
=head2 Constructor
=head3 new
my $req = App::Info::Request->new(%params);
This method is used internally by App::Info to construct new
App::Info::Request objects to pass to event handler objects. Generally, you
won't need to use it, other than perhaps for testing custom App::Info::Handler
classes.
The parameters to C<new()> are passed as a hash of named parameters that
correspond to their like-named methods. The supported parameters are:
=over 4
=item type
=item message
=item error
=item value
=item callback
=back
See the object methods documentation below for details on these object
attributes.
=cut
sub new {
my $pkg = shift;
# Make sure we've got a hash of arguments.
Carp::croak("Odd number of parameters in call to " . __PACKAGE__ .
"->new() when named parameters expected" ) if @_ % 2;
my %params = @_;
# Validate the callback.
if ($params{callback}) {
Carp::croak("Callback parameter '$params{callback}' is not a code ",
"reference")
unless UNIVERSAL::isa($params{callback}, 'CODE');
} else {
# Otherwise just assign a default approve callback.
$params{callback} = sub { 1 };
}
# Validate type parameter.
if (my $t = $params{type}) {
Carp::croak("Invalid handler type '$t'")
unless $t eq 'error' or $t eq 'info' or $t eq 'unknown'
or $t eq 'confirm';
} else {
$params{type} = 'info';
}
# Return the request object.
bless \%params, ref $pkg || $pkg;
}
##############################################################################
=head2 Object Methods
=head3 key
my $key = $req->key;
Returns the key stored in the App::Info::Request object. The key is used by
the App::Info subclass to uniquely identify the information it is harvesting,
such as the path to an executable. It might be used by request handlers,
for example, to see if an option was passed on the command-line.
=cut
sub key { $_[0]->{key} }
##############################################################################
=head3 message
my $message = $req->message;
Returns the message stored in the App::Info::Request object. The message is
typically informational, or an error message, or a prompt message.
=cut
sub message { $_[0]->{message} }
##############################################################################
=head3 error
my $error = $req->error;
Returns any error message associated with the App::Info::Request object. The
error message is typically there to display for users when C<callback()>
returns false.
=cut
sub error { $_[0]->{error} }
##############################################################################
=head3 type
my $type = $req->type;
Returns a string representing the type of event that triggered this request.
The types are the same as the event triggering methods defined in App::Info.
As of this writing, the supported types are:
=over
=item info
=item error
=item unknown
=item confirm
=back
Be sure to consult the App::Info documentation for more details on the event
types.
=cut
sub type { $_[0]->{type} }
##############################################################################
=head3 callback
if ($req->callback($value)) {
print "Value '$value' is valid.\n";
} else {
print "Value '$value' is not valid.\n";
}
Executes the callback anonymous subroutine supplied by the App::Info concrete
base class that triggered the event. If the callback returns false, then
C<$value> is invalid. If the callback returns true, then C<$value> is valid
and can be assigned via the C<value()> method.
Note that the C<value()> method itself calls C<callback()> if it was passed a
value to assign. See its documentation below for more information.
=cut
sub callback {
my $self = shift;
my $code = $self->{callback};
local $_ = $_[0];
$code->(@_);
}
##############################################################################
=head3 value
my $value = $req->value;
if ($req->value($value)) {
print "Value '$value' successfully assigned.\n";
} else {
print "Value '$value' not successfully assigned.\n";
}
When called without an argument, C<value()> simply returns the value currently
stored by the App::Info::Request object. Typically, the value is the default
value for a confirm event, or a value assigned to an unknown event.
When passed an argument, C<value()> attempts to store the the argument as a
new value. However, C<value()> calls C<callback()> on the new value, and if
C<callback()> returns false, then C<value()> returns false and does not store
the new value. If C<callback()> returns true, on the other hand, then
C<value()> goes ahead and stores the new value and returns true.
=cut
sub value {
my $self = shift;
if ($#_ >= 0) {
# grab the value.
my $value = shift;
# Validate the value.
if ($self->callback($value)) {
# The value is good. Assign it and return true.
$self->{value} = $value;
return 1;
} else {
# Invalid value. Return false.
return;
}
}
# Just return the value.
return $self->{value};
}
1;
__END__
=head1 SUPPORT
This module is stored in an open L<GitHub
repository|http://github.com/theory/app-info/>. Feel free to fork and
contribute!
Please file bug reports via L<GitHub
Issues|http://github.com/theory/app-info/issues/> or by sending mail to
L<bug-App-Info@rt.cpan.org|mailto:bug-App-Info@rt.cpan.org>.
=head1 AUTHOR
David E. Wheeler <david@justatheory.com>
=head1 SEE ALSO
L<App::Info|App::Info> documents the event triggering methods and how they
construct App::Info::Request objects to pass to event handlers.
L<App::Info::Handler:|App::Info::Handler> documents how to create custom event
handlers, which must make use of the App::Info::Request object passed to their
C<handler()> object methods.
The following classes subclass App::Info::Handler, and thus offer good
exemplars for using App::Info::Request objects when handling events.
=over 4
=item L<App::Info::Handler::Carp|App::Info::Handler::Carp>
=item L<App::Info::Handler::Print|App::Info::Handler::Print>
=item L<App::Info::Handler::Prompt|App::Info::Handler::Prompt>
=back
=head1 COPYRIGHT AND LICENSE
Copyright (c) 2002-2011, David E. Wheeler. Some Rights Reserved.
This module is free software; you can redistribute it and/or modify it under the
same terms as Perl itself.
=cut
|