Lines Matching refs:SB

4 The SB APIs constitute the stable C++ API that lldb presents to external
10 The classes in the SB API's are all called SB<SomeName>, where SomeName is in
14 All the SB API classes are non-virtual, single inheritance classes. They should
15 only include SBDefines.h or other SB headers as needed. There should be no
20 or remove ivars without breaking binary compatibility. In some cases, the SB
25 is included in SBDefines.h. So if you need an SB class to wrap an lldb_private
27 opaque declaration in the SB classes .h file.
29 If the SB Class needs some state of its own, as well as the backing object,
30 don't include that as a direct ivar in the SB Class. Instead, make an Impl
31 class in the SB's .cpp file, and then make the SB object hold a shared or
33 more state in the SB object, those needs are likely to change over time, and
40 all the SB objects. Since the ivars of the classes are all pointers of one sort
43 something reasonable. We also always have an "IsValid" method on all the SB
46 Another piece of the SB API infrastructure is the Python (or other script
50 straight C++ header file. These files are called SB<ClassName>.i, and live in
55 C++ API's for an SB class, you have to copy the interface to the .i file.