The various VPR abstraction interfaces are documented extensively, and readers are encouraged to review the VPR Programmer Reference (refer to the VPR website for more information).

The VPR class names follow a standard convention, and understanding this can be helpful in navigating the API documentation. Classes that wrap platform-specific interfaces are named as follows: vpr::<Type><Platform>. For example, the NSPR implementation of vpr::SocketStream is named vpr::SocketStreamNSPR. Here, <Type> is “SocketStream”, and <Platform> is “NSPR”. The full list of platform names (as spelled in the class names) is as follows: