Bio::B...hReport(3pm)

πŸ’– Bio::Biblio::TechReport β€” the perl man page, but make it cute πŸ’–

okay bestie, gather round 🫢 this is Bio::Biblio::TechReport from the User Contributed Perl Documentation section (3pm), and it is exactly what it sounds like: a little storage object that holds one (1) technical report. that's it. that's the whole job. and it does it beautifully. πŸ‘‘


✨ NAME ✨

Bio::Biblio::TechReport β€” a representation of a technical report. no cap, that's the whole description. iconic minimalism. πŸ’…


🌸 VERSION 🌸

version 1.70 β€” she's been around, she's stable, she's thriving. πŸ¦‹


✨ SYNOPSIS ✨

here's the vibe check, code verbatim because we do NOT mess with code:

$obj = Bio::Biblio::TechReport->new
              (-authors => [
                   Bio::Biblio::Person->new(-lastname => 'Hasek'),
                   Bio::Biblio::Person->new(-lastname => 'Jagr'),
                   Bio::Biblio::Organisation->new(-name => 'NHL'),
                           ]
               -title => 'Pinned in the corner');

look at her go πŸ₯Ή you got Bio::Biblio::Person objects and a Bio::Biblio::Organisation chillin' in the -authors array, and then a -title. and yes, bestie, we are passing that exactly as written, comma situation and all, because the facts do not change. 😌


πŸ’œ DESCRIPTION πŸ’œ

a storage object for a technical report. she holds stuff. she keeps it safe. she's a whole container for your report metadata.

and if you wanna see where she sits in the class hierarchy (her family tree, her lineage, her ancestry.com moment), it's right here:

http://www.ebi.ac.uk/~senger/openbqs/images/bibobjects_perl.gif

πŸŽ€ Attributes πŸŽ€

there are no specific attributes in this class. zero. none. nada. πŸ™ˆ

however β€” and this is the part that matters β€” you can set and get all the attributes that are defined in the parent classes. so she's not empty, she's just inheriting her whole personality from her family. main character energy by proxy. πŸ‘‘


🌈 SEE ALSO 🌈

go click around, it's giving resource hub. ✨


🫢 FEEDBACK 🫢

πŸ’Œ Mailing lists

user feedback is an integral part of the evolution of this and other Bioperl modules. like, genuinely β€” they want to hear from you. send your comments and suggestions preferably to the Bioperl mailing list. your participation is much appreciated. πŸ’–

bioperl-l@bioperl.org                  - General discussion
http://bioperl.org/wiki/Mailing_lists  - About the mailing lists

🧚 Support

please direct usage questions or support issues to the mailing list:

bioperl-l@bioperl.org

rather than to the module maintainer directly. why? because there are many experienced and responsive experts who will be able to look at the problem and quickly address it. so many smart people, one mailing list, zero reason to DM the maintainer personally. πŸ™

and please include a thorough description of the problem with code and data examples if at all possible. the more context, the faster the glow-up. ✨

πŸ› Reporting bugs

report bugs to the Bioperl bug tracking system to help them keep track of the bugs and their resolution. bug reports can be submitted via the web:

https://redmine.open-bio.org/projects/bioperl/

⭐ Authors

  • Martin Senger <senger@ebi.ac.uk>
  • Heikki Lehvaslaiho <heikki@bioperl.org>

this software is Copyright (c) by 2002 European Bioinformatics Institute and released under the license of the same terms as the perl 5 programming language system itself.

so like, same license as perl 5 itself. keep that in mind if you're out here redistributing, bestie. πŸ’…

and that's the whole page!! 🌸 written by the perl v5.36.0 crew, dated 2023-02-14 (yes, valentine's day, how romantic of them πŸŽ€), from the Bio::B...hReport(3pm) page in the User Contributed Perl Documentation. mwah, slay, periodt. πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from