CosTime_UTO(3)

💖 CosTime_UTO 💖

okay bestie, welcome to the CosTime_UTO manual page — it lives in the Erlang Module Definition section and it's literally the whole OMG CosTime::UTO interface 🫶

---

✨ NAME ✨

CosTime_UTO — this module implements the OMG CosTime::UTO interface. periodt 💅

---

🌸 DESCRIPTION 🌸

so like, to actually get access to the record definitions for the structures, you gotta use:

-include_lib("cosTime/include/*.hrl").

that's the vibe check, no cap 🎀

---

👑 EXPORTS 👑

💜 '_get_time'(UTO) -> ulonglong()

Types:

UTO = #objref

this operation returns the time associated with the target object ✨

---

💜 '_get_inaccuracy'(UTO) -> ulonglong()

Types:

UTO = #objref

this operation returns the inaccuracy associated with the target object. it's giving... precision, but make it honest 😭

---

💜 '_get_tdf'(UTO) -> short()

Types:

UTO = #objref

this operation returns the time displacement factor associated with the target object 🌈

---

💜 '_get_utc_time'(UTO) -> UtcT

Types:

UTO = #objref
Utc = #'TimeBase_UtcT'{time, inacclo, inacchi, tdf}
time = ulonglong()
inacclo = ulong()
inacchi = ushort()
tdf = short()

this operation returns the data associated with the target object, but in Utc form 🦋 like the same info, just dressed up different, iconic honestly

---

💜 absolute_time(UTO) -> OtherUTO

Types:

UTO = OtherUTO = #objref

this operation creates a new UTO object representing the time in the target object added to the current time (UTC). the time base is 15 october 1582 00:00 🕰️ and ngl, comparing two time objects that use different time bases is, by obvious reasons, pointless 💀

it raises DATA_CONVERSION if it causes an overflow. and fr fr, this operation is only useful if the target object represents a relative time — don't come for me, that's just how it is 🙈

---

💜 compare_time(UTO, ComparisonType, OtherUTO) -> Reply

Types:

UTO = OtherUTO = #objref
ComparisonType = 'IntervalC' | 'MidC'
Reply = 'TCEqualTo' | 'TCLessThan' | 'TCGreaterThan' |
'TCIndeterminate'

this operation compares the time associated with the target object and the given UTO object 🔥 and the different ComparisonTypes are, bestie:

• 'MidC' — only compares the time represented by each object. and also, the target object is always used as the first parameter in the comparison, i.e., if the target object's time is larger, 'TCGreaterThan' will be returned 👑
• 'IntervalC' — this one also takes the inaccuracy into consideration, i.e., if the two objects' interval overlaps, 'TCIndeterminate' is returned, otherwise it's the same as for 'MidC' 🌟

---

💜 time_to_interval(UTO, OtherUTO) -> TIO

Types:

UTO = OtherUTO = TIO = #objref

this operation returns a TIO representing the interval between the target object and the given UTO midpoint times. the inaccuracy in the objects is not taken into consideration 🎀 (she said what she said)

---

💜 interval(UTO) -> TIO

Types:

UTO = TIO = #objref

this operation creates a TIO object representing the error interval around the time value represented by the target object, i.e.:

TIO.upper_bound = UTO.time+UTO.inaccuracy
TIO.lower_bound = UTO.time-UTO.inaccuracy

math queen behavior, we love to see it 💅✨

---

and that's the whole page bestie, you ate it 🍓

🌟 sign-off, main character style: brought to you by Ericsson AB, cosTime version 5.2.2, and this lil page is CosTime_UTO(3) — slay, bye 🫶💖🧚