fclose — Close file identifiers opened by fopen.
fclose closes registered files and returns double status 0 on success or -1 for an invalid identifier. MATLAB-compatible mode accepts a scalar double identifier or character-vector 'all'; broader RunMat forms have independent extension gates.
Syntax
status = fclose()
status = fclose(fid)
status = fclose("all")
[status, msg] = fclose(...)Inputs
fid- Type
Any- Required
- Yes
- Description
- File identifier scalar, vector, cell list, or keyword "all".
mode- Type
StringScalar- Required
- Yes
- Default
"all"- Description
- Close all open user file identifiers.
Returns
status- Type
NumericScalar- Description
- 0 on success, -1 on failure.
msg- Type
StringScalar- Description
- Failure message when status is -1.
Returned values from fclose depend on how many outputs the caller requests.
Errors
RunMat:fclose:InvalidInput- When
- Input argument count or file identifier value/type is invalid.
- Message
fclose: invalid input arguments
RunMat:fclose:InvalidIdentifier- When
- The provided file identifier does not refer to an open file.
- Message
fclose: invalid file identifier. Use fopen to generate a valid file ID.
RunMat:fclose:IoFailure- When
- Closing an open file failed due to I/O error.
- Message
fclose: failed to close file
- When
- Internal runtime control-flow or conversion failed.
- Message
fclose: internal error
Forms and status
status = fclose(fid) closes one registered file. status = fclose('all') closes every open nonstandard file. A finite integer-valued double scalar is the compatible identifier form; identifiers 0, 1, and 2 leave standard streams open and return success.
Typed integer, logical, collection, string-scalar 'all', resident identifier, no-input close-all, and second diagnostic-message output forms are separately gated RunMat extensions. All identifiers in a collection are validated before any close side effect.
The first close removes the registry entry. Repeating it returns -1 with an invalid-identifier diagnostic. Closing flushes buffered writes; a failed flush preserves the registry entry for a later retry. The process cannot close file handles opened by another process.
Placement and ownership
The file handle and registry are host-owned; there is no GPU kernel or fusion route. An admitted resident numeric identifier passes its compatibility and class checks before gathering through its owning provider, then follows the same host close path. GPU residency does not remove the caller's responsibility to close a handle.
Examples
Close a file after writing text
[fid, msg] = fopen('results.txt', 'w');
assert(fid >= 3, msg);
fprintf(fid, 'Simulation complete\n');
status = fclose(fid);
statusExpected output:
status = 0Close all nonstandard files
fid1 = fopen('a.txt', 'r');
fid2 = fopen('b.txt', 'r');
assert(fid1 >= 3 && fid2 >= 3);
status = fclose('all');
statusExpected output:
status = 0Handle an invalid identifier
status = fclose(9999);
statusExpected output:
status = -1Using fclose with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how fclose changes the result.
Run a small fclose example, explain the result, then change one input and compare the output.
FAQ
What values can I pass?⌄
A scalar double file identifier or character-vector 'all' in MATLAB-compatible mode. Other RunMat forms are separately extension-gated.
What does status mean?⌄
Double 0 means success and -1 means failure; the diagnostic second output is a RunMat extension.
Does it close standard streams?⌄
No. Identifiers 0, 1, and 2 are accepted as successful no-ops.
Can I close the same identifier twice?⌄
Yes, but the second call returns -1 because the registry entry was removed.
Are buffered writes flushed?⌄
Yes. A flush failure returns a failure status and keeps the registry entry for retry.
Do GPU arrays change handle ownership?⌄
No. Resident identifiers are gathered only in extension mode; the caller still closes the host handle.
Can it close another process's file?⌄
No. It only addresses this RunMat process's file registry.
Related Io functions
Filetext
feof · fgetl · fgets · fileread · filewrite · fopen · fprintf · fread · frewind · fwrite · readlines · writelines
Repl Fs
addpath · cd · copyfile · delete · dir · exist · fileattrib · fileparts · filesep · fullfile · genpath · getenv · getpref · isenv · isfile · isfolder · ispref · ls · matlabroot · memmapfile · memmapfile.subsasgn · memmapfile.subsref · mkdir · movefile · open · opentoline · path · pathsep · pcode · pwd · readstruct · rehash · restoredefaultpath · rmdir · rmpath · run · savepath · setenv · setpref · system · tempdir · tempname · uigetdir · uigetfile · uiputfile · unsetenv · userpath · what · winqueryreg · xmlread · xmlwrite
Tabular
arrayDatastore · csvread · csvwrite · detectImportOptions · dlmread · dlmwrite · fileDatastore · getvaropts · parquetDatastore · parquetinfo · parquetread · readcell · readmatrix · readtable · readtimetable · setvaropts · setvartype · spreadsheetImportOptions · writecell · writematrix · writetable · writetimetable · xlsread · xlswrite
Data
commit · data.copy · data.create · data.delete · data.exists · data.export · data.import · data.inspect · data.list · data.move · data.open · DataArray.chunk_shape · DataArray.codec · DataArray.dtype · DataArray.fill · DataArray.name · DataArray.rank · DataArray.read · DataArray.resize · DataArray.shape · DataArray.write · Dataset.array · Dataset.arrays · Dataset.attrs · Dataset.begin · Dataset.get_attr · Dataset.has_array · Dataset.id · Dataset.path · Dataset.refresh · Dataset.set_attr · Dataset.set_attrs · Dataset.snapshot · Dataset.version · DataTransaction.abort · DataTransaction.commit · DataTransaction.create_array · DataTransaction.delete_array · DataTransaction.fill · DataTransaction.id · DataTransaction.resize · DataTransaction.set_attr · DataTransaction.set_attrs · DataTransaction.status · DataTransaction.write
Import
Json
Source you can read
Every RunMat function's source is public. Read exactly how fclose is executed, line by line, in Rust.
- View the source for fclose in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.