Description

Functor to emit basic block separation in output organized by address.

This does nothing if the output is organized by AST since the basic block callbacks handle it in that case.

Definition at line 380 of file AsmUnparser.h.

Inheritance diagram for Rose::BinaryAnalysis::AsmUnparser::InsnBlockSeparation:

[legend]

Collaboration diagram for Rose::BinaryAnalysis::AsmUnparser::InsnBlockSeparation:

[legend]

Public Member Functions
virtual bool	operator() (bool enabled, const InsnArgs &args)
	Default callbacks.

Public Member Functions inherited from Rose::BinaryAnalysis::AsmUnparser::UnparserCallback
virtual bool	operator() (bool, const BasicBlockArgs &)
	Default callbacks.

virtual bool	operator() (bool, const StaticDataArgs &)
	Default callbacks.

virtual bool	operator() (bool, const DataBlockArgs &)
	Default callbacks.

virtual bool	operator() (bool, const FunctionArgs &)
	Default callbacks.

virtual bool	operator() (bool, const InterpretationArgs &)
	Default callbacks.

Constructor & Destructor Documentation

Rose::BinaryAnalysis::AsmUnparser::InsnBlockSeparation::InsnBlockSeparation ( )

inline

Definition at line 383 of file AsmUnparser.h.

virtual bool Rose::BinaryAnalysis::AsmUnparser::InsnBlockSeparation::operator()	(	bool	,
		const InsnArgs &
	)

virtual

Default callbacks.

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

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

SgAsmBlock* Rose::BinaryAnalysis::AsmUnparser::InsnBlockSeparation::prev_block

Definition at line 382 of file AsmUnparser.h.

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