data::section::simple(3pm) [debian man page]

Data::Section::Simple(3pm)				User Contributed Perl Documentation				Data::Section::Simple(3pm)

NAME

       Data::Section::Simple - Read data from __DATA__

SYNOPSIS

	 use Data::Section::Simple qw(get_data_section);

	 # Functional interface -- reads from caller package __DATA__
	 my $all = get_data_section; # All data in hash reference
	 my $foo = get_data_section('foo.html');

	 # OO - allows reading from other packages
	 my $reader = Data::Section::Simple->new($package);
	 my $all = $reader->get_data_section;

	 __DATA__

	 @@ foo.html
	 <html>
	  <body>Hello</body>
	 </html>

	 @@ bar.tt
	 [% IF true %]
	   Foo
	 [% END %]

DESCRIPTION

       Data::Section::Simple is a simple module to extract data from "__DATA__" section of the file.

LIMITATIONS

       As the name suggests, this module is a simpler version of the excellent Data::Section. If you want more functionalities such as merging
       data sections or changing header patterns, use Data::Section instead.

       This module does not implement caching (yet) which means in every "get_data_section" or "get_data_section($name)" this module seeks and re-
       reads the data section. If you want to avoid doing so for the better performance, you should implement caching in your own caller code.

BUGS

   __DATA__ appearing elsewhere
       If you data section has literal "__DATA__" in the data section, this module might be tricked by that. Although since its pattern match is
       greedy, "__DATA__" appearing before the actual data section (i.e. in the code) might be okay.

       This is by design -- in theory you can "tell" the DATA handle before reading it, but then reloading the data section of the file (handy for
       developing inline templates with PSGI web applications) would fail because the pos would be changed.

       If you don't like this design, again, use the superior Data::Section.

   utf8 pragma
       If you enable utf8 pragma in the caller's package (or the package you're inspecting with the OO interface), the data retrieved via
       "get_data_section" is decoded, but otherwise undecoded. There's no reliable way for this module to programmatically know whether utf8
       pragma is enabled or not: it's your responsibility to handle them correctly.

AUTHOR

       Tatsuhiko Miyagawa <miyagawa@bulknews.net>

COPYRIGHT

       Copyright 2010- Tatsuhiko Miyagawa

       The code to read DATA section is based on Mojo::Command get_all_data: Copyright 2008-2010 Sebastian Riedel

LICENSE

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

SEE ALSO

       Data::Section Inline::Files

perl v5.12.4							    2011-09-18						Data::Section::Simple(3pm)

Check Out this Related Man Page

Data(3) 						User Contributed Perl Documentation						   Data(3)

NAME

       Gimp::Data - Set and get state data.

SYNOPSIS

	 use Gimp::Data;

	 $Gimp::Data{'value1'} = "Hello";
	 print $Gimp::Data{'value1'},", World!!
";

DESCRIPTION

       With this module, you can access plugin-specific (or global) data in Gimp, i.e. you can store and retrieve values that are stored in the
       main Gimp application.

       An example would be to save parameter values in Gimp, so that on subsequent invocations of your plug-in, the user does not have to set all
       parameter values again (Gimp::Fu does this already).

%Gimp::Data
       You can store and retrieve anything you like in this hash. It's contents will automatically be stored in Gimp, and can be accessed in later
       invocations of your plug-in. Be aware that other plug-ins store data in the same "hash", so better prefix your key with something unique,
       like your plug-in's name. As an example, the Gimp::Fu module uses "function_name/_fu_data" to store its data.

       This module might use a persistant implementation, i.e. your data might survive a restart of the Gimp application, but you cannot count on
       this.

       "Gimp::Data" will try to freeze your data when you pass in a reference. On retrieval, the data is thawed again. See Storable for more info.
       This might be implemented through either Storable or Data::Dumper, or not implemented at all (i.e. silently fail) ;)

PERSISTANCE

       "Gimp::Data" contains the following functions to ease applications where persistence for perl data structures is required:

       Gimp::Data::freeze(reference)
	   Freeze (serialize) the reference.

       Gimp::Data::thaw(data)
	   Thaw (unserialize) the dsata and return the original reference.

LIMITATIONS

       You cannot store references, and you cannot (yet) iterate through the keys (with "keys", "values" or "each").

AUTHOR

       Marc Lehmann <pcg@goof.com>

SEE ALSO

       perl(1), Gimp.

perl v5.8.0							    2001-12-06								   Data(3)

Linux and UNIX Man Pages

data::section::simple(3pm) [debian man page]

Check Out this Related Man Page