drmaa_viter(3)

πŸ“¦ version 6.1.3, in epel 9

πŸ’… drmaa_viter(3) πŸ’…

okay bestie, welcome to the drmaa_viter(3) page from the torque manual. it’s giving β€œshort but mighty” vector iteration realness, and every detail is about to get its moment. no cap. πŸ¦‹

🌸 NAME 🌸

  • drmaa_viter β€” Vector iteration functions.
  • The drmaa_get_next_X() functions SHALL take up to value_len bytes of the next thing β€” attribute name / attribute value / job identifier β€” from the values opaque string vector and put it in the value buffer.

✨ SYNOPSIS ✨

okay so the synopsis is literally pointing you at the detailed description, so let’s go straight into the tea. πŸ’–

πŸ’– Detailed Description πŸ’–

So the drmaa_get_next_X() functions SHALL move up to value_len bytes of the next attribute name / attribute value / job identifier out of the values opaque string vector and into the value buffer. yes, this is the same rule as up top β€” it’s important enough to repeat, bestie. ✨

After that, the opaque string vector’s internal iterator SHALL get moved forward to the next entry. slay, iterator, do your thing. πŸ”₯

If there are literally no more values, those functions return DRMAA_ERRNO_INVALID_ARGUMENT β€” but plot twist, that behavior is outside DRMAA specification. iykyk. πŸ’€

The drmaa_get_num_X() functions SHALL stash the number of elements in the space you handed over as size.

The drmaa_release_X() functions free the memory used by the values opaque string vector. Every bit of memory used by the strings contained therein is freed too. full clean-up, no leftovers, periodt. 🧚

πŸŽ€ Author πŸŽ€

Generated automatically by Doxygen for torque from the source code. not me writing it by hand, it’s the auto-gen life. πŸ’…


🫢 Version 6.1.3, dated Sat Jan 21 2023, for drmaa_viter(3) β€” that’s the cute sign-off, bestie. mwah πŸ’‹
πŸ“¦ where this page comes from