| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
This removes PuglContextType and allows the user to pass a backend directly.
Normally this would come from one of the two accessors declared in the headers,
but it would be possible to add backends without changing any of the existing
code at all.
Unfortunately, it is not possible to preserve backwards compatibility and
achieve the ultimate goal of linking only to the required dependencies, so
puglInitContextType() has just been removed.
|
|
These need to be symmetric because sometimes different things need to happen in
either situation when entering the context as well.
|
|
Towards making them opaque and exposing them to the user to decouple the core
library from backends.
The general names mean that it won't be possible to build multiple backends for
one platform into the same binary, but that seems reasonable for now, and it
will make things simpler without needing to add a bunch of dispatch code. That
will still be possible if it's ever needed, though.
|
|
|
|
This name was pretty confusing since there is already the concept of a
"context".
|
|
|
|
|
|
Weird convention, that.
|
|
|
|
|
|
|
|
|
