Conversation

Notices

1. Embed this notice
   rqsd (rq@borg.social)'s status on Tuesday, 08-Aug-2023 02:54:11 JST rqsd

   in reply to

   (A) The default umber of units commensurate with the license granted.ha ha found a typo

   • kaia likes this.
   • Embed this notice
     rqsd (rq@borg.social)'s status on Tuesday, 08-Aug-2023 02:54:13 JST rqsd

     in reply to

     The spec would've greatly benefitted from some kind of diagram that gives an overview of when in the lifecycle of a program's execution which functions are roughly expected to be called in what order...

   • Embed this notice
     rqsd (rq@borg.social)'s status on Tuesday, 08-Aug-2023 02:54:14 JST rqsd

     in reply to

     Oh God, this has weird complexities. Apparently LSRelease() only releases per license unit resources and the license handle and associated context is released separately with LSFreeHandle(). I guess it makes sense if you need to keep track of every license individually (e.g. a CAL) and mid-operation one of the CALs expires...

   • Embed this notice
     rqsd (rq@borg.social)'s status on Tuesday, 08-Aug-2023 02:54:15 JST rqsd

     *This is now the big LSAPI thread; mute replies if you don't want me to liveblog reading this spec*
     A valid license handle is always returned by this function whether valid license resources are granted or not. This handle must always be released with LSFreeHandle() when the application has completed execution.I'm not sure how I feel about this, honestly. On one hand, it makes it easier to just always clean up everything, but on the other hand, I feel like you would bail and return early anyway. I wonder if this has some non-obvious practical use...