If a GsFile is open for read/write, e.g. when using GsFile class >> openUpdateOnServer: (mode r+), then after invoking atEnd, the file position is incorrect; GsFile >> position will return 0. Subsequent writes will be in the correct location.
If GsFile >> position: is sent, followed by GsFile >> atEnd, a subsequent write may not be in the correct location.
Last updated: 6/15/21