Maple Professional
Maple Academic
Maple Student Edition
Maple Personal Edition
Maple Player
Maple Player for iPad
MapleSim Professional
MapleSim Academic
Maple T.A. - Testing & Assessment
Maple T.A. MAA Placement Test Suite
Möbius - Online Courseware
Machine Design / Industrial Automation
Aerospace
Vehicle Engineering
Robotics
Power Industries
System Simulation and Analysis
Model development for HIL
Plant Modeling for Control Design
Robotics/Motion Control/Mechatronics
Other Application Areas
Mathematics Education
Engineering Education
High Schools & Two-Year Colleges
Testing & Assessment
Students
Financial Modeling
Operations Research
High Performance Computing
Physics
Live Webinars
Recorded Webinars
Upcoming Events
MaplePrimes
Maplesoft Blog
Maplesoft Membership
Maple Ambassador Program
MapleCloud
Technical Whitepapers
E-Mail Newsletters
Maple Books
Math Matters
Application Center
MapleSim Model Gallery
User Case Studies
Exploring Engineering Fundamentals
Teaching Concepts with Maple
Maplesoft Welcome Center
Teacher Resource Center
Student Help Center
fclose - closes a buffered file
close - closes an unbuffered file
Calling Sequence
fclose(file ...)
close(file ...)
Parameters
file
-
one or more names or file descriptors of open files to be closed
Description
The functions close and fclose are equivalent, and can be used interchangeably.
Closes the specified file, which is assumed to have been opened either implicitly or by fopen or open.
fclose and close do not return anything.
Closing a file ensures that all data is actually written to disk.
When exiting Maple by the quit, done, or stop command, all open files are automatically closed.
Closing a file which exists but is not open is harmless.
The number of open files allowed is system specific.
When writing many files, you must fclose() each of them to ensure that you do not run out of file handles.
Thread Safety
The fclose and close commands are thread safe as of Maple 15. Care must be taken when closing files that are used by multiple threads in parallel.
Parallel calls to file i/o commands on the same file descriptor will be serialized in an arbitrary order. If you need the commands to execute in a particular order you must use Maple's synchronization tools to enforce this. See Threads:-Mutex.
For more information on thread safety, see index/threadsafe.
Examples
See Also
file_types, fopen, IO_errors, open
Download Help Document