Codeunit 491 "Memory Mapped File"
Base Application · System.IO
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · System.IO · BC23-30 · source at ea08af5e · facts from BC29
Procedures
CreateMemoryMappedFileFromTempBlob(var TempBlob: Codeunit "Temp Blob"; Name: Text)OpenMemoryMappedFile(Name: Text)ReadTextFromMemoryMappedFile(var Text: Text)ReadTextWithSeparatorsFromMemoryMappedFile(var Text: Text)GetName(): TextDispose()
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 4100 “Temp Blob” (5 calls:
CreateMemoryMappedFileFromTempBlob → CreateInStream,CreateMemoryMappedFileFromTempBlob → HasValue,CreateMemoryMappedFileFromTempBlob → Length, …) - Codeunit 10 “Type Helper” (2 calls:
ReadTextWithSeparatorsFromMemoryMappedFile → LFSeparator,ReadTextWithSeparatorsFromMemoryMappedFile → ReadAsTextWithSeparator)
Called by
- Codeunit 8626 “Config. Import Table in Backgr” (3 calls:
OnRun → Dispose,OnRun → OpenMemoryMappedFile,OnRun → ReadTextWithSeparatorsFromMemoryMappedFile)
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: "Memory Mapped File"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.