mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2024-11-23 22:00:10 +00:00
662548c826
Instead of maintaining separate swig interface files, we can use the API headers directly. They implement the exact same C++ APIs and we can conditionally include the python extensions as needed. To remove the swig extensions from the API headers when building the LLDB framework, we can use the unifdef tool when it is available. Otherwise we just copy them as-is. Differential Revision: https://reviews.llvm.org/D142926
21 lines
1001 B
OpenEdge ABL
21 lines
1001 B
OpenEdge ABL
%feature("docstring",
|
|
"Represents a file specification that divides the path into a directory and
|
|
basename. The string values of the paths are put into uniqued string pools
|
|
for fast comparisons and efficient memory usage.
|
|
|
|
For example, the following code ::
|
|
|
|
lineEntry = context.GetLineEntry()
|
|
self.expect(lineEntry.GetFileSpec().GetDirectory(), 'The line entry should have the correct directory',
|
|
exe=False,
|
|
substrs = [self.mydir])
|
|
self.expect(lineEntry.GetFileSpec().GetFilename(), 'The line entry should have the correct filename',
|
|
exe=False,
|
|
substrs = ['main.c'])
|
|
self.assertTrue(lineEntry.GetLine() == self.line,
|
|
'The line entry's line number should match ')
|
|
|
|
gets the line entry from the symbol context when a thread is stopped.
|
|
It gets the file spec corresponding to the line entry and checks that
|
|
the filename and the directory matches what we expect.") lldb::SBFileSpec;
|