You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From a VMOD developer perspective, there should be clear and concise documentation about exactly what is allowed for $ABI vrt, namely which includes can be used. I guess the main question is really about cache.h, is it part of VRT or not? If it is was not, we would have changed the VRT version quite often in the past for no good reason (but we already know that and the decision was made as a safety measure). Also, there will be almost no VMOD which does not make use of the workspace API, so $ABI vrt would probably be quite useless for all practical purposes.
Right now, our documentation is either vague or contradictory. Some findings:
From a VMOD developer perspective, there should be clear and concise documentation about exactly what is allowed for
$ABI vrt
, namely which includes can be used. I guess the main question is really aboutcache.h
, is it part of VRT or not? If it is was not, we would have changed the VRT version quite often in the past for no good reason (but we already know that and the decision was made as a safety measure). Also, there will be almost no VMOD which does not make use of the workspace API, so$ABI vrt
would probably be quite useless for all practical purposes.Right now, our documentation is either vague or contradictory. Some findings:
Yes, but which files constitute that API?
good level of detail (namely, includes the actual file names), but out of sync with reality
Might suggest that
cache.h
was part of the ABIThe text was updated successfully, but these errors were encountered: