ONVIF::...es::Time(3)

📦 version 1.38.6, in nixpkgs unstable

✨ ONVIF::Analytics::Types::Time — bestie, it's a time class 🕐

Okay so picture this: you're deep in the ONVIF::...es::Time(3) page from the User Contributed Perl Documentation, and it turns out the whole thing is just... a time. Three little ints. That's the vibe. And honestly? Iconic of it. 💅

🌸 NAME 🌸

ONVIF::Analytics::Types::Time — literally right there in the name, no notes, we move.

🦋 DESCRIPTION 🦋

So this is a Perl data type class for the XML Schema defined complexType Time, and the namespace it calls home is:

http://www.onvif.org/ver10/schema

That's it, that's the whole personality. It's a Perl class wrapper for that schema type, periodt. ✨

🎀 PROPERTIES 🎀

These are the properties you can reach with the get_PROPERTY / set_PROPERTY methods — yes, the naming convention is exactly that, get_Hour, set_Hour, iykyk:

  • Hour — the hour one, bestie 🕐
  • Minute — the minute one, obviously
  • Second — and the second one, we love a complete set 💖

🌈 METHODS 🌈

💜 new

Constructor time, for real for real. Here's the data structure you may pass to new() — and yeah, I'm giving it to you verbatim because code is sacred:

 { # ONVIF::Analytics::Types::Time
   Hour =>  $some_value, # int
   Minute =>  $some_value, # int
   Second =>  $some_value, # int
 },

So Hour, Minute, and Second all get an int, and that's genuinely the whole thing. Clean, minimal, main character energy. 👑

🫶 AUTHOR 🫶

Generated by SOAP::WSDL — no cap, it made this itself, it's built different. 🤖

💀 real talk: the only danger here is forgetting that Hour, Minute and Second all want ints. No undefined behaviour lore, no deprecated warnings, just three integers chilling. Slay.

and that's the tea, bestie 🍓 — this gem was served fresh from perl v5.42.3, dated 1980-01-01 (yes, that date is real, and yes, it's giving time-traveling icon 🧚). See you in the next manpage, mwah. 💖

📦 where this page comes from