ldas-tools-frameAPI  2.5.1
Public Member Functions | Protected Types | Protected Member Functions | Protected Attributes | List of all members
FrameFile Class Reference

#include <filereader.hh>

Inheritance diagram for FrameFile:
FileReader FileWriter

Public Member Functions

 FrameFile (const std::string &Filename, unsigned int size, char *buffer, bool EnableMemoryMappedIO, std::ios::openmode Mode, const char *BufferFilname=(const char *) NULL)
 
virtual ~FrameFile ()
 
const std::string & GetFilename () const
 ret: const std::string& - Name of the file More...
 

Protected Types

typedef LDASTools::AL::filebuf filebuf
 

Protected Member Functions

void finish ()
 

Protected Attributes

FrameCPP::Common::FrameBuffer< filebuf > * m_frame_buf
 

Member Typedef Documentation

◆ filebuf

typedef LDASTools::AL::filebuf FrameFile::filebuf
protected

Constructor & Destructor Documentation

◆ FrameFile()

FrameFile::FrameFile ( const std::string &  Filename,
unsigned int  size,
char *  buffer,
bool  EnableMemoryMappedIO,
std::ios::openmode  Mode,
const char *  BufferFilname = (const char*)NULL 
)
inline

◆ ~FrameFile()

FrameFile::~FrameFile ( )
inlinevirtual

Member Function Documentation

◆ finish()

void FrameFile::finish ( )
inlineprotected
Todo:
Need to understand why this causes instability in the frameAPI. Use libumem to quickly raise the issue.

◆ GetFilename()

const std::string & FrameFile::GetFilename ( ) const
inline

ret: const std::string& - Name of the file

Member Data Documentation

◆ m_frame_buf

FrameCPP::Common::FrameBuffer< filebuf >* FrameFile::m_frame_buf
protected

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