Juman::MList(3pm)

okay bestie, you went looking for Juman::MList(3pm) in the User Contributed Perl Documentation and honestly? taste. 💅 this is the little object that holds a whole morpheme list and doesn't make it weird. let's go.

---

📛 NAME 📛

Juman::MList — a morpheme sequence object (形態素列オブジェクト). on the page itself it's printed as å½¢æ…‹ç´ åˆ—ã‚ªãƒ–ã‚¸ã‚§ã‚¯ãƒˆ because of an encoding oopsie, and we'll get to that drama in POD ERRORS, don't worry 🫠

✨ SYNOPSIS ✨

  $result = new Juman::MList();

that's it. that's the whole vibe. so clean ✨

💖 DESCRIPTION 💖

it's an object that holds a morpheme sequence. that's the job. it holds the sequence. it does not elaborate. icon behavior honestly 👑

🧚 CONSTRUCTOR 🧚

• new ( [MRPHS] ) — spins up a brand new object holding the morpheme sequence you handed it. if you skip the argument, it starts life with an empty morpheme sequence as the initial value. lowkey generous of it 💜

👑 METHODS 👑

• mrph ( NUM ) — hands you back the morpheme sitting at position NUM. number one. the N-th one. you know the drill 💅
• mrph — no argument, no problem: returns the list of all the morphemes. the whole squad, front to back 🌈
• mrph_list — same energy, same promise: returns the list of all the morphemes. yes bestie, both of these do that. they're not fighting, they're just twins 🫶
• push_mrph ( @MRPH ) — appends the morpheme sequence you pass in to the end of the sentence. new morphemes, who dis 🌸
• set_readonly — locks it down: writing to the morpheme sequence is no longer permitted. after this, it's a look-don't-touch situation, fr fr 🙈
• spec — returns the entire string of the morpheme sequence. the result comes out in the same format as the output from Juman. no cap, identical formatting 🔥

🔍 SEE ALSO 🔍

• Juman::Result
• Juman::Morpheme

go read your siblings, they're family 🥰

✍️ AUTHOR ✍️

土屋 雅稔 <tsuchiya@pine.kuee.kyoto-u.ac.jp>

(as printed on the page: 土屋 雅稔 — again, encoding shenanigans, not a typo, be nice 😭)

💀 POD ERRORS 💀

so……… yeah. the doc had some coding errors and it's spilling the tea itself. here's exactly what it says:

• Around line 10: Non-ASCII character seen before =encoding in 'å½¢æ…‹ç´ åˆ—ã‚ªãƒ–ã‚¸ã‚§ã‚¯ãƒˆ'. Assuming CP1252
• Around line 135: =over without closing =back

so the POD parser saw non-ASCII characters before any =encoding declaration and just assumed CP1252 💀 and somewhere around line 135 there's an =over that never got its =back. not the pod doc being messy in public. we've all been there. it's giving unclosed parentheses in a text message. it's fine. it's FINE 🎀

---

and that's the whole page, bestie — straight out of perl v5.40.1, dated 2026-02-11. now go hold a morpheme sequence like a main character 🌟🦋💜