Project

General

Profile

Bug #667 » 0058-Correct-preceed.-to-preced.patch

S3_2 - Marko Lindqvist, 05/22/2024 10:14 PM

View differences:

client/gui-gtk-3.22/chatline.c
}
/* Now we just need to check that it is not a private
* message. If we encounter a space then the preceeding
* message. If we encounter a space then the preceding
* text could not have been a user/player name (the
* quote check above eliminated names with spaces) so
* it must be a public message. Otherwise if we encounter
client/gui-gtk-3.22/editprop.c
should be freed by property_filter_free when no longed needed.
The filter string is '|' ("or") separated list of '&' ("and") separated
lists of patterns. A pattern may be preceeded by '!' to have its result
lists of patterns. A pattern may be preceded by '!' to have its result
negated.
NB: If you change the behaviour of this function, be sure to update
client/gui-gtk-4.0/chatline.c
}
/* Now we just need to check that it is not a private
* message. If we encounter a space then the preceeding
* message. If we encounter a space then the preceding
* text could not have been a user/player name (the
* quote check above eliminated names with spaces) so
* it must be a public message. Otherwise if we encounter
client/gui-gtk-4.0/editprop.c
should be freed by property_filter_free when no longed needed.
The filter string is '|' ("or") separated list of '&' ("and") separated
lists of patterns. A pattern may be preceeded by '!' to have its result
lists of patterns. A pattern may be preceded by '!' to have its result
negated.
NB: If you change the behaviour of this function, be sure to update
server/ruleset.c
}
/**********************************************************************//**
This function loads a city name list from a section file. The file and
This function loads a city name list from a section file. The file and
two section names (which will be concatenated) are passed in.
**************************************************************************/
static bool load_city_name_list(struct section_file *file,
......
/* Each string will be of the form "<cityname> (<label>, <label>, ...)".
* The cityname is just the name for this city, while each "label" matches
* a terrain type for the city (or "river"), with a preceeding ! to negate
* a terrain type for the city (or "river"), with a preceding ! to negate
* it. The parentheses are optional (but necessary to have the settings,
* of course). Our job is now to parse it. */
for (j = 0; j < dim; j++) {
server/settings.c
}
/************************************************************************//**
Verify that a given allowtake string is valid. See
game.allow_take.
Verify that a given allowtake string is valid.
See game.allow_take.
****************************************************************************/
static bool allowtake_callback(const char *value,
struct connection *caller,
......
int len = strlen(value), i;
bool havecharacter_state = FALSE;
/* We check each character individually to see if it's valid. This
/* We check each character individually to see if it's valid. This
* does not check for duplicate entries.
*
* We also track the state of the machine. havecharacter_state is
* true if the preceeding character was a primary label, e.g.
* NHhAadb. It is false if the preceeding character was a modifier
* We also track the state of the machine. havecharacter_state is
* true if the preceding character was a primary label, e.g.
* NHhAadb. It is false if the preceding character was a modifier
* or if this is the first character. */
for (i = 0; i < len; i++) {
translations/core/check_po.pl
print " $name \"", join("\"\n \"", @_), "\"\n";
}
# Print a problem (args like print()), preceeded by entry unless
# Print a problem (args like print()), preceded by entry unless
# we have already printed that: label, and msgid and msgstr.
#
sub print_problem {
utility/inputfile.c
The tokens recognised are as follows:
(Single quotes are delimiters used here, but are not part of the
actual tokens/strings.)
Most tokens can be preceeded by optional whitespace; exceptions
Most tokens can be preceded by optional whitespace; exceptions
are section_name and entry_name.
section_name: '[foo]'
......
/*******************************************************************//**
Get a flag token of a single character, with optional
preceeding whitespace.
preceding whitespace.
***********************************************************************/
static const char *get_token_white_char(struct inputfile *inf,
char target)
(2-2/3)