mirror of
https://github.com/curl/curl.git
synced 2026-08-25 14:53:34 +03:00
code: language cleanup in comments
Based on the standards and guidelines we use for our documentation. - expand contractions (they're => they are etc) - host name = > hostname - file name => filename - user name = username - man page => manpage - run-time => runtime - set-up => setup - back-end => backend - a HTTP => an HTTP - Two spaces after a period => one space after period Closes #14073
This commit is contained in:
parent
9b683577e1
commit
c074ba64a8
213 changed files with 1719 additions and 1715 deletions
26
lib/file.c
26
lib/file.c
|
|
@ -147,7 +147,7 @@ static CURLcode file_setup_connection(struct Curl_easy *data,
|
|||
|
||||
/*
|
||||
* file_connect() gets called from Curl_protocol_connect() to allow us to
|
||||
* do protocol-specific actions at connect-time. We emulate a
|
||||
* do protocol-specific actions at connect-time. We emulate a
|
||||
* connect-then-transfer protocol and "connect" to the file here
|
||||
*/
|
||||
static CURLcode file_connect(struct Curl_easy *data, bool *done)
|
||||
|
|
@ -177,18 +177,18 @@ static CURLcode file_connect(struct Curl_easy *data, bool *done)
|
|||
return result;
|
||||
|
||||
#ifdef DOS_FILESYSTEM
|
||||
/* If the first character is a slash, and there's
|
||||
/* If the first character is a slash, and there is
|
||||
something that looks like a drive at the beginning of
|
||||
the path, skip the slash. If we remove the initial
|
||||
the path, skip the slash. If we remove the initial
|
||||
slash in all cases, paths without drive letters end up
|
||||
relative to the current directory which isn't how
|
||||
relative to the current directory which is not how
|
||||
browsers work.
|
||||
|
||||
Some browsers accept | instead of : as the drive letter
|
||||
separator, so we do too.
|
||||
|
||||
On other platforms, we need the slash to indicate an
|
||||
absolute pathname. On Windows, absolute paths start
|
||||
absolute pathname. On Windows, absolute paths start
|
||||
with a drive letter.
|
||||
*/
|
||||
actual_path = real_path;
|
||||
|
|
@ -308,7 +308,7 @@ static CURLcode file_upload(struct Curl_easy *data)
|
|||
bool eos = FALSE;
|
||||
|
||||
/*
|
||||
* Since FILE: doesn't do the full init, we need to provide some extra
|
||||
* Since FILE: does not do the full init, we need to provide some extra
|
||||
* assignments here.
|
||||
*/
|
||||
|
||||
|
|
@ -331,7 +331,7 @@ static CURLcode file_upload(struct Curl_easy *data)
|
|||
|
||||
fd = open(file->path, mode, data->set.new_file_perms);
|
||||
if(fd < 0) {
|
||||
failf(data, "Can't open %s for writing", file->path);
|
||||
failf(data, "cannot open %s for writing", file->path);
|
||||
return CURLE_WRITE_ERROR;
|
||||
}
|
||||
|
||||
|
|
@ -343,7 +343,7 @@ static CURLcode file_upload(struct Curl_easy *data)
|
|||
if(data->state.resume_from < 0) {
|
||||
if(fstat(fd, &file_stat)) {
|
||||
close(fd);
|
||||
failf(data, "Can't get the size of %s", file->path);
|
||||
failf(data, "cannot get the size of %s", file->path);
|
||||
return CURLE_WRITE_ERROR;
|
||||
}
|
||||
data->state.resume_from = (curl_off_t)file_stat.st_size;
|
||||
|
|
@ -413,13 +413,13 @@ out:
|
|||
* file_do() is the protocol-specific function for the do-phase, separated
|
||||
* from the connect-phase above. Other protocols merely setup the transfer in
|
||||
* the do-phase, to have it done in the main transfer loop but since some
|
||||
* platforms we support don't allow select()ing etc on file handles (as
|
||||
* platforms we support do not allow select()ing etc on file handles (as
|
||||
* opposed to sockets) we instead perform the whole do-operation in this
|
||||
* function.
|
||||
*/
|
||||
static CURLcode file_do(struct Curl_easy *data, bool *done)
|
||||
{
|
||||
/* This implementation ignores the host name in conformance with
|
||||
/* This implementation ignores the hostname in conformance with
|
||||
RFC 1738. Only local files (reachable via the standard file system)
|
||||
are supported. This means that files on remotely mounted directories
|
||||
(via NFS, Samba, NT sharing) can be accessed through a file:// URL
|
||||
|
|
@ -518,7 +518,7 @@ static CURLcode file_do(struct Curl_easy *data, bool *done)
|
|||
* of the stream if the filesize could be determined */
|
||||
if(data->state.resume_from < 0) {
|
||||
if(!fstated) {
|
||||
failf(data, "Can't get the size of file.");
|
||||
failf(data, "cannot get the size of file.");
|
||||
return CURLE_READ_ERROR;
|
||||
}
|
||||
data->state.resume_from += (curl_off_t)statbuf.st_size;
|
||||
|
|
@ -526,7 +526,7 @@ static CURLcode file_do(struct Curl_easy *data, bool *done)
|
|||
|
||||
if(data->state.resume_from > 0) {
|
||||
/* We check explicitly if we have a start offset, because
|
||||
* expected_size may be -1 if we don't know how large the file is,
|
||||
* expected_size may be -1 if we do not know how large the file is,
|
||||
* in which case we should not adjust it. */
|
||||
if(data->state.resume_from <= expected_size)
|
||||
expected_size -= data->state.resume_from;
|
||||
|
|
@ -570,7 +570,7 @@ static CURLcode file_do(struct Curl_easy *data, bool *done)
|
|||
if(!S_ISDIR(statbuf.st_mode)) {
|
||||
while(!result) {
|
||||
ssize_t nread;
|
||||
/* Don't fill a whole buffer if we want less than all data */
|
||||
/* Do not fill a whole buffer if we want less than all data */
|
||||
size_t bytestoread;
|
||||
|
||||
if(size_known) {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue