ROSE  0.11.145.0
Public Member Functions | List of all members
Rose::BinaryAnalysis::AsmUnparser::DataBlockBody Class Reference

Description

Functor to emit each data statement of the block.

This is a no-op except when output is organized by AST.

Definition at line 644 of file AsmUnparser.h.

#include <backend/asmUnparser/AsmUnparser.h>

Inheritance diagram for Rose::BinaryAnalysis::AsmUnparser::DataBlockBody:
Inheritance graph
[legend]
Collaboration diagram for Rose::BinaryAnalysis::AsmUnparser::DataBlockBody:
Collaboration graph
[legend]

Public Member Functions

virtual bool operator() (bool enabled, const DataBlockArgs &args)
 Default callbacks. More...
 
- Public Member Functions inherited from Rose::BinaryAnalysis::AsmUnparser::UnparserCallback
virtual bool operator() (bool, const InsnArgs &)
 Default callbacks. More...
 
virtual bool operator() (bool, const BasicBlockArgs &)
 Default callbacks. More...
 
virtual bool operator() (bool, const StaticDataArgs &)
 Default callbacks. More...
 
virtual bool operator() (bool, const FunctionArgs &)
 Default callbacks. More...
 
virtual bool operator() (bool, const InterpretationArgs &)
 Default callbacks. More...
 

Member Function Documentation

virtual bool Rose::BinaryAnalysis::AsmUnparser::DataBlockBody::operator() ( bool  ,
const DataBlockArgs  
)
virtual

Default callbacks.

The default is to abort, because if these are called it means one of three things:

  1. The arguments are wrong in the subclass and the subclass therefore isn't providing an implementation when it thinks it is.
  2. The wrong type was used for the second argument. Instruction callbacks use InsnArgs, basic block callbacks use BasicBlockArgs, etc.
  3. The functor was added to the wrong callback list. For instance, an instruction functor was accidently added to one of the function callback lists.

Reimplemented from Rose::BinaryAnalysis::AsmUnparser::UnparserCallback.


The documentation for this class was generated from the following file: