GSSAPI::Status(3)

✨ NAME ✨

Okay so this is GSSAPI::Status — yes, GSSAPI::Status(3) from the User Contributed Perl Documentation section, hiii 👋 — and it's literally all about methods for handling GSSAPI statuses. Bestie, it's giving “error info but make it structured” 💅.

---

🫶 SYNOPSIS 🫶

Here's the vibe in code, no cap:

  use GSSAPI;

  $status = GSSAPI::Status->new(GSS_S_COMPLETE, 0);

  if (GSS_ERROR($status->major)) {
    die "a horrible death";
  }
  if (! $status) {                      # another way of writing the above
    die "a horrible death";
  }

  $status = $some_GSSAPI->someop($args1, etc);
  if ($status) {
    foreach ($status->generic_message, $status->specific_message) {
      print "GSSAPI error: $_\n";
    }
    die "help me";
  }

---

💅 DESCRIPTION 💅

So GSSAPI::Status objects are returned by most other GSSAPI operations. Iconic. They consist of a GSSAPI generic code and, for most operations, a mechanism specific code 🌀.

Those numeric codes are accessible through the major and minor methods:

• major — grabs the generic code, bestie.
• minor — grabs the mechanism specific code when there is one.

The standard textual messages that go with the current status can be obtained with these methods:

• generic_message — returns the generic message text.
• specific_message — returns the specific message text.

Each of these returns a list of text which should presumably be displayed in order. Yes, in order — don't just scramble them like a playlist on shuffle 🙈.

The generic code part of a GSSAPI::Status is composed of three subfields that can be accessed with the GSS_CALLING_ERROR, GSS_ROUTINE_ERROR, and GSS_SUPPLEMENTARY_INFO functions. The returned values can be compared against the constants whose names start with GSS_S_ if your code wants to handle particular errors itself. Very choose-your-own-adventure of it 💖.

The GSS_ERROR function returns true if and only if the given generic code contains neither a calling error nor a routine error. Like, both have to be absent for it to be true — that's the whole rule, periodt.

When evaluated in a boolean context, a GSSAPI::Status object will be true if and only if the major status code is GSS_S_COMPLETE ✅.

When evaluated in a string context, a GSSAPI::Status object will return the generic and specific messages all joined together with newlines. This may or may not make die $status work usefully — that's the actual caveat, bestie, don't come for me 😭.

---

💀 BUGS 💀

The base objects are currently implemented as a blessed C structure containing the major and minor status codes. It should probably be a blessed array or hash instead, thereby cutting down on the amount of C code involved and making it more flexible. Like, it works, but the glow-up potential is real 🦋.

---

👑 AUTHOR 👑

Philip Guenther <pguen@cpan.org> — the main character who wrote this 🫶.

---

🌈 SEE ALSO 🌈

• perl(1)
• RFC2743

---

byeee 🎀 — this page is from perl v5.42.2, dated 2025-06-30 💖