The FMMAP_NOFILE option creates an anonymous mapping: it's just a virtual memory allocation without a specific backing file (the system swap is used if needed).
It's not different from what the intrinsic ALLOCATE() does, so the question is "should it be kept?", as it's redundant.
I basically introduced it for flexibility: the same code could perform a named or anonymous mapping depending on the needs, by just switching this option.
The
FMMAP_NOFILEoption creates an anonymous mapping: it's just a virtual memory allocation without a specific backing file (the system swap is used if needed).It's not different from what the intrinsic
ALLOCATE()does, so the question is "should it be kept?", as it's redundant.I basically introduced it for flexibility: the same code could perform a named or anonymous mapping depending on the needs, by just switching this option.