Reindeer - Tasks: task #10279, Backend specific information in...
You are not allowed to post comments on this tracker with your current authentication level.
task #10279: Backend specific information in ren_reindeer_new
Submitter: | Patrik Olsson <peo> | ||
Submitted: | Wed 17 Mar 2010 01:04:12 PM UTC | ||
Should Start On: | Tue 16 Mar 2010 11:00:00 PM UTC | Should be Finished on: | Thu 29 Apr 2010 10:00:00 PM UTC |
Category: | libreindeer | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | None | Percent Complete: | 0% |
Open/Closed: | Open | Planned Release: | 0.1 |
Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-f8d8.
Corresponding source code
Some backends need to know the native context to do their thing in virtual Reindeer functions. The function ren_reindeer_new should take a void pointer whose meaning is backend specific. The application needs to look up in the reference documentation what it is supposed to point to here (backend specific headers could help here). It is recommended that backends make it easy for themselves to change the meaning of this pointer while still allowing old code to use the old meaning (binary compatibility). In practice this means making the pointer point to a struct where the first field is an integer specifying the version of the rest of the struct.