Codeunit 3035 "DotNet_Buffer"

Base Application · System.Utilities · BC23-30 · source at ea08af5e · facts from BC29

Procedures

• BlockCopy(var Source_DotNet_Array: Codeunit DotNet_Array; SourceOffset: Integer; var Destination_DotNet_Array: Codeunit DotNet_Array; DestinationOffset: Integer; Count: Integer)
• ByteLength(var DotNet_Array: Codeunit DotNet_Array): Integer
• GetByte(var DotNet_Array: Codeunit DotNet_Array; Index: Integer): Integer
• SetByte(var DotNet_Array: Codeunit DotNet_Array; Index: Integer; Value: Integer)

Triggers

OnRun

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 3000 “DotNet_Array” (4 calls: BlockCopy → GetArray, ByteLength → GetArray, GetByte → GetArray, …)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "DotNet_Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.