MkBufferC_ATL_API

MkBufferC - the abstract class known as buf or buffer is used to create and manage dynamic, generic, mixed typed data. … More...

Collaboration diagram for MkBufferC_ATL_API:

Topics
	MkBufferC_Class_ATL_API
	MkBufferC - define the class …
	MkBufferC_TOR_ATL_API
	MkBufferC - various functions to create, initialize and destroy a MkBufferC …
	MkBufferC_Get_ATL_API
	MkBufferC - various functions to get buffer-data …
	MkBufferC_Set_ATL_API
	MkBufferC - various functions to set buffer-data …
	MkBufferC_Info_ATL_API
	MkBufferC - various functions to get information out of buffer-data …
	MkBufferC_Access_ATL_API
	MkBufferC - various functions to access buffer-data …
	MkBufferC_Misc_ATL_API
	MkBufferC - various functions to work on buffer-data …

Detailed Description

MkBufferC - the abstract class known as buf or buffer is used to create and manage dynamic, generic, mixed typed data. …

The MkBufferC is used to store PRIMITIVE TYPE data. If atlmkkernel is working on data… atlmkkernel is working on an MkBufferC object or on a list of MkBufferC objects called MkBufferListC.

MkBufferC CLASS

The ABSTRACT-CLASS used to store a native-type-data-item defined by PRIMITIVE TYPE …

C-Kernel-Details

The ABSTRACT-CLASS MkBufferS is used to store MkTypeE data in an MkBufferS::storage …

A new MkBufferS is always preallocated with the predefined ILS-storage (MkBufferS::ils_data), but can switch to a MALLOC-storage if the storage requirements of the user exceed the predefined MkBufferS::ilsS::size.

‍A MkBufferS never run out of storage.

The basic goal of the ILS-storage technology is to minimize the usage of MALLOC, this mean that the MkBufferS::ilsS::size should be large enought to be sufficient for the user needs.

The following conditions must always be met for the ILS memory:

• The MkBufferS::ils_data have to be always the last item in the last subclass of MkBufferS
• The MkBufferS::ilsS::offset is calculated as: MkBufferSPtr->ils_data - MkBufferSPtr.

The ABSTRACT-CLASS MkBufferS is missing the ILS-storage, the FINAL-CLASSES are:

‍MkBuffer64C, MkBuffer256C and MkBuffer1024C

See also

MkBufferListC, MkBufferStreamC

MkBufferC CTOR / DTOR

command	synonmym
(constructor,static) MkBufferC [MkBufferC::Create ?size:int32=0?]	myooX::NewN ::MkBufferC ?size:W=0?
(destructor) MkBufferC::Delete $buf	myooX::DestroyN $buf

Example from server.atl → read a buffer-object and convert single-char-type-identifer to string.

  proc Ot_BUF2 { myNs } {
    SendSTART $myNs

    foreach i {1 2 3} {
      set buf [ReadBUF $myNs]
      SendSTR $myNs [MkBufferC::GetType1 $buf]
      SendBUF $myNs $buf
      myooX::DestroyN $buf
    }

    SendRETURN $myNs
  }

See also

BufferGetType1 BufferGetType2 BufferGetType3