Anthony Scarpino wrote: >> >>> - What about C_GetSlotList()? My inituition says this is safe >>> either >>> way, but there are no clear docs. >> >> It is safe either way and the output can only grow, never shrink, >> unless you call C_Finalize() and C_Initalize() again. Prior to v2.20 >> it could never change - the v2.20 revision was one I asked for. > > The additions for v2.20 C_GetSlotList fell below the the line when we > implemented v2.20 changes.. Today the list is still locked to when > C_Initialize is first called.
Correct, we haven't yet done anything to make C_GetSlotList actually expand even though v2.20 allows for it and we asked for it! Given the way that hardware acceleration is going (ie becoming a CPU chip feature) I can't see us actually doing anything much about this in the future either. -- Darren J Moffat
