GFileMonitor: Don't accept negative values for rate-limit
authorMatthias Clasen <mclasen@redhat.com>
Sun, 28 Nov 2010 22:14:49 +0000 (17:14 -0500)
committerMatthias Clasen <mclasen@redhat.com>
Sun, 28 Nov 2010 22:14:49 +0000 (17:14 -0500)
Patch by Alksander Morgado,
https://bugzilla.gnome.org/show_bug.cgi?id=635768

gio/gfilemonitor.c
gio/gfilemonitor.h

index 38a0493..726cd62 100644 (file)
@@ -327,21 +327,21 @@ g_file_monitor_cancel (GFileMonitor* monitor)
 /**
  * g_file_monitor_set_rate_limit:
  * @monitor: a #GFileMonitor.
- * @limit_msecs: a integer with the limit in milliseconds to 
- * poll for changes.
+ * @limit_msecs: a non-negative integer with the limit in milliseconds
+ *     to poll for changes
  *
  * Sets the rate limit to which the @monitor will report
- * consecutive change events to the same file. 
- * 
- **/
+ * consecutive change events to the same file.
+ */
 void
 g_file_monitor_set_rate_limit (GFileMonitor *monitor,
-                              int           limit_msecs)
+                               gint          limit_msecs)
 {
   GFileMonitorPrivate *priv;
-  
+
   g_return_if_fail (G_IS_FILE_MONITOR (monitor));
-  
+  g_return_if_fail (limit_msecs >= 0);
+
   priv = monitor->priv;
   if (priv->rate_limit_msec != limit_msecs)
     {
index cf6f6be..8e27d22 100644 (file)
@@ -81,7 +81,7 @@ GType    g_file_monitor_get_type       (void) G_GNUC_CONST;
 gboolean g_file_monitor_cancel         (GFileMonitor      *monitor);
 gboolean g_file_monitor_is_cancelled   (GFileMonitor      *monitor);
 void     g_file_monitor_set_rate_limit (GFileMonitor      *monitor,
-                                        int                limit_msecs);
+                                        gint               limit_msecs);
 
 
 /* For implementations */