docs: Improve g_variant_loop() docs

Typo fix and changing "is not recommended" to the nice version of "don't
do this", aka "causes undefined behavior".
This commit is contained in:
Benjamin Otte 2011-10-16 12:58:29 -07:00
parent 14677e16d8
commit 7d1c7af1a6
2 changed files with 6 additions and 3 deletions

View File

@ -1439,7 +1439,10 @@ _g_local_file_info_get (const char *basename,
/* Avoid stat in trivial case */ /* Avoid stat in trivial case */
if (attribute_matcher == NULL) if (attribute_matcher == NULL)
{
g_file_info_unset_attribute_mask (info);
return info; return info;
}
#ifndef G_OS_WIN32 #ifndef G_OS_WIN32
res = g_lstat (path, &statbuf); res = g_lstat (path, &statbuf);

View File

@ -4778,7 +4778,7 @@ g_variant_iter_next (GVariantIter *iter,
* @iter: a #GVariantIter * @iter: a #GVariantIter
* @format_string: a GVariant format string * @format_string: a GVariant format string
* @...: the arguments to unpack the value into * @...: the arguments to unpack the value into
* @returns: %TRUE if a value was unpacked, or %FALSE if there as no * @returns: %TRUE if a value was unpacked, or %FALSE if there was no
* value * value
* *
* Gets the next item in the container and unpacks it into the variable * Gets the next item in the container and unpacks it into the variable
@ -4799,7 +4799,7 @@ g_variant_iter_next (GVariantIter *iter,
* function with a string constant for the format string and the same * function with a string constant for the format string and the same
* string constant must be used each time. Mixing calls to this * string constant must be used each time. Mixing calls to this
* function and g_variant_iter_next() or g_variant_iter_next_value() on * function and g_variant_iter_next() or g_variant_iter_next_value() on
* the same iterator is not recommended. * the same iterator causes undefined behavior.
* *
* See the section on <link linkend='gvariant-format-strings'>GVariant * See the section on <link linkend='gvariant-format-strings'>GVariant
* Format Strings</link>. * Format Strings</link>.