POE::R...andles(3pm)

💖 NAME 💖

POE::Resource::FileHandles — the internal filehandle manager for POE::Kernel, bestie. She's the backstage crew, not the main character (yet).

---

✨ SYNOPSIS ✨

Okay so, real talk:

There is no public API. None. Zero. Nada. This is a backstage-pass-only situation. 🙈

---

🎀 DESCRIPTION 🎀

POE::Resource::FileHandles is a mix-in class for POE::Kernel. Like, she doesn't stand alone — she gets mixed in, iykyk.

She provides the low-level features to manage filehandles. Very behind-the-scenes, very "don't worry about it, I got it" energy. 💅

She is used internally by POE::Kernel, which means she has no public interface. So if you came here looking for something to call? Bestie. No. This is not the class for you. 🦋

---

🌈 SEE ALSO 🌸

• Wanna actually use file watchers? Go read "I/O Watchers (Selects)" in POE::Kernel for the public file watcher API. That's the one you want. 👑
• Curious about POE resources in general, publicly speaking? See "Resources" in POE::Kernel.
• Want the whole general discussion about resources and the classes that manage them? See POE::Resource. She's the vibe-setter for this whole little family. 💜

---

💀 BUGS 💀

Okay this one's important, so listen up. 🫶

POE watches I/O based on filehandles rather than file descriptors. And the way that can clash — yes, literally clash — between its API and an underlying descriptor-based event loop. 😭

Usually? Not a problem. Usually it's fine, it's giving peaceful coexistence. But in certain edge cases it may require a work-around. So if something's acting cursed at the descriptor level, this is probably why. Not me warning you in advance or anything. 🙈

---

💜 AUTHORS & COPYRIGHTS 💜

Please see POE for more information about authors and contributors. Credit where credit is due, always. ✨

---

Written by the Perl crew, documented for perl v5.34.0, dated 2022-03-25 — and this little POE::R...andles(3pm) era was truly iconic. Slay, and thanks for reading, bestie. 💅🎀💖