layout: restructure into src/ tests/ android/ scripts/ tools/
- extension/src/{port,platform,codepage} -> src/; native_render -> src/host
(+ dxt, shaders/); libgr2 -> src/gr2; extension/third_party -> third_party
- extension/tests -> tests/port, libgr2/tests -> tests/gr2
- android-native -> android (build.sh, push-client.sh moved in)
- script -> scripts; tools/40250 -> tools/server; oracle -> tools/granny-oracle;
perf tools -> tools/perf
- all build trees under build/ (native, release, android, port-gate)
- xrender:: CMake aliases -> mt::; port-map ledger impl paths rewritten
No code changes. ctest 15/15, port_gate macos+android PASS, port_map check 0 errors.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
70710477cf
commit
a46093104c
@@ -0,0 +1,28 @@
|
||||
|
||||
/* Range object interface */
|
||||
|
||||
#ifndef Py_RANGEOBJECT_H
|
||||
#define Py_RANGEOBJECT_H
|
||||
#ifdef __cplusplus
|
||||
extern "C" {
|
||||
#endif
|
||||
|
||||
/* This is about the type 'xrange', not the built-in function range(), which
|
||||
returns regular lists. */
|
||||
|
||||
/*
|
||||
A range object represents an integer range. This is an immutable object;
|
||||
a range cannot change its value after creation.
|
||||
|
||||
Range objects behave like the corresponding tuple objects except that
|
||||
they are represented by a start, stop, and step datamembers.
|
||||
*/
|
||||
|
||||
PyAPI_DATA(PyTypeObject) PyRange_Type;
|
||||
|
||||
#define PyRange_Check(op) (Py_TYPE(op) == &PyRange_Type)
|
||||
|
||||
#ifdef __cplusplus
|
||||
}
|
||||
#endif
|
||||
#endif /* !Py_RANGEOBJECT_H */
|
||||
Reference in New Issue
Block a user