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

πŸ’– Bio::Biblio::Proceeding β€” bestie edition πŸ’–

okay so this is a Perl module, manual page Bio::B...ceeding(3pm) (the name got squished by the formatter, it's Bio::Biblio::Proceeding, iykyk), and it lives in the User Contributed Perl Documentation corner of the man pages. sit down, grab a boba, we're gonna talk about conference proceedings πŸŽ€


✨ NAME ✨

Bio::Biblio::Proceeding β€” it's a representation of a conference proceeding. that's it, that's the vibe. πŸ’…


🌸 VERSION 🌸

version 1.70 β€” she's on 1.70, no cap.


πŸ¦‹ SYNOPSIS πŸ¦‹

two ways to do the thing, pick your fighter:

$obj = Bio::Biblio::Proceeding->new(-title => 'JavaONE');

and then, the other option:

#--- OR ---

$obj = Bio::Biblio::Proceeding->new();
$obj->title ('JavaONE');

literally either one. constructor with args, or construct empty and set title after. both ate. ✨


πŸ‘‘ DESCRIPTION πŸ‘‘

it's a storage object for a conference proceeding. like, it holds the info. that's its whole job and she does it well.

you can see where she sits in the class hierarchy right here:

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

(go look, it's giving family tree energy 🌳)

🌈 Attributes 🌈

okay so here's the tea: there are no specific attributes in this class. none. zero. nada.

however β€” and this is the important part β€” you can still set and get all the attributes defined in the parent classes. so like, the inheritance is doing the heavy lifting. main character energy from the ancestors fr fr. πŸ’œ


πŸ’€ BUGS AND LIMITATIONS πŸ’€

real talk: this class should probably be somewhere else in the class hierarchy, because a proceeding is actually a collection of resources. (the original literally spells it "actrually" and we're keeping that energy, no notes 😭)

perhaps this will be changed in the future. perhaps not. we simply do not know. πŸ™ˆ


πŸŽ€ SEE ALSO πŸŽ€

go click around, it's a whole ecosystem bestie. 🌸


🫢 FEEDBACK 🫢

πŸ’Œ Mailing lists πŸ’Œ

user feedback is an integral part of the evolution of this and other Bioperl modules. like, genuinely. so send your comments and suggestions β€” preferably to the Bioperl mailing list. your participation is much appreciated. (we mean it!! πŸ₯Ή)

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 so many experienced and responsive experts who will be able to look at the problem and quickly address it. (the original says "reponsive" and honestly? relatable spelling, keeping it. πŸ’€)

and please include a thorough description of the problem with code and data examples if at all possible. the more deets, the better. slay. ✨

πŸ› Reporting bugs πŸ›

report bugs to the Bioperl bug tracking system so we can 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.


no cap: every option, every URL, every email, every typo we lovingly preserved. the facts did not change, only the vibe. 🫢

and that's the whole page bestie!! πŸ’– this one shipped as perl v5.36.0, dated 2023-02-14 (yes, valentine's day, she's a romantic πŸ’Œ). go forth and proceed β€” literally, it's a Proceeding module. periodt. πŸ’…βœ¨πŸŽ€πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from