diagnostic.c: Fix typos in comments.

2000-12-01  Phil Edwards  <pme@sources.redhat.com>

	* diagnostic.c:  Fix typos in comments.
	* diagnostic.h:  Likewise.

From-SVN: r37923
This commit is contained in:
Phil Edwards 2000-12-01 19:31:01 +00:00
parent 815d683eb8
commit c4765d18f2
3 changed files with 17 additions and 12 deletions

View File

@ -1,3 +1,8 @@
2000-12-01 Phil Edwards <pme@sources.redhat.com>
* diagnostic.c: Fix typos in comments.
* diagnostic.h: Likewise.
2000-11-30 Phil Edwards <pme@sources.redhat.com>
* rtl.texi (Machine Modes): Document BImode and OImode.

View File

@ -147,7 +147,7 @@ diagnostic_finalizer_fn lang_diagnostic_finalizer;
int diagnostic_message_length_per_line;
/* Used to control every diagnostic message formatting. Front-ends should
call set_message_prefixing_rule to set up their politics. */
call set_message_prefixing_rule to set up their policies. */
static int current_prefixing_rule;
/* Prevent recursion into the error handler. */
@ -373,7 +373,7 @@ output_clear (buffer)
clear_diagnostic_info (buffer);
}
/* Finishes to construct a NULL-terminated character string representing
/* Finishes constructing a NULL-terminated character string representing
the BUFFERed message. */
const char *
@ -636,7 +636,7 @@ maybe_wrap_text (buffer, start, end)
}
/* Append a STRING to BUFFER; the STRING maybe be line-wrapped if in
/* Append a STRING to BUFFER; the STRING might be line-wrapped if in
appropriate mode. */
void
@ -661,7 +661,7 @@ output_to_stream (buffer, file)
/* Format a message pointed to by output_buffer_text_cursor (BUFFER) using
output_buffer_format_args (BUFFER) as appropriate. The following format
specifiers are recognized as being language independent:
specifiers are recognized as being language independent:
%d, %i: (signed) integer in base ten.
%u: unsigned integer in base ten.
%o: unsigned integer in base eight.
@ -1696,7 +1696,7 @@ See %s for instructions.\n",
exit (FATAL_EXIT_CODE);
}
/* Setup DC for reporting a diagnostic MESSAGE (an error of a WARNING),
/* Setup DC for reporting a diagnostic MESSAGE (an error or a WARNING),
using arguments pointed to by ARGS_PTR, issued at a location specified
by FILE and LINE. */
void

View File

@ -40,13 +40,13 @@ typedef diagnostic_starter_fn diagnostic_finalizer_fn;
everything goes well. */
typedef int (*printer_fn) PARAMS ((output_buffer *));
/* This data structure encapulates an output_buffer's state. */
/* This data structure encapsulates an output_buffer's state. */
typedef struct
{
/* The prefix for each new line. */
const char *prefix;
/* The real upper bound of number of characters per line, taking into
accompt the case of a very very looong prefix. */
account the case of a very very looong prefix. */
int maximum_length;
/* The ideal upper bound of number of characters per line, as suggested
by front-end. */
@ -96,7 +96,7 @@ struct output_buffer
#define output_message_text(BUFFER) \
((const char *) obstack_base (&(BUFFER)->obstack))
/* This data structure bundles altogether any information relevent to
/* This data structure bundles altogether any information relevant to
the context of a diagnostic message. */
struct diagnostic_context
{
@ -104,7 +104,7 @@ struct diagnostic_context
const char *message;
/* A pointer to a variable list of the arguments necessary for the
purpose of message formatting. */
purpose of message formatting. */
va_list *args_ptr;
/* The name of the source file involved in the diiagnostic. */
@ -113,11 +113,11 @@ struct diagnostic_context
/* The line-location in the source file. */
int line;
/* Is it message a warning? */
/* Is this message a warning? */
int warn;
/* This function is called before any message is printed out. It is
respondible for preparing message prefix and such. For example, it
responsible for preparing message prefix and such. For example, it
might say:
In file included from "/usr/local/include/curses.h:5:
from "/home/gdr/src/nifty_printer.h:56:
@ -160,7 +160,7 @@ extern int diagnostic_message_length_per_line;
/* This output buffer is used by front-ends that directly output
diagnostic messages without going through `error', `warning',
and simillar functions. In general, such usage should be
and similar functions. In general, such usage should be
avoided. This global buffer will go away, once all such usage
has been removed. */
extern output_buffer *diagnostic_buffer;