[gjs: 1/8] boxed: Update outdated comment
- From: Cosimo Cecchi <cosimoc src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gjs: 1/8] boxed: Update outdated comment
- Date: Thu, 31 May 2018 23:54:11 +0000 (UTC)
commit 3361f04d4b66a1e59ac271870201cd416d48166d
Author: Philip Chimento <philip chimento gmail com>
Date: Sat May 12 12:21:12 2018 -0700
boxed: Update outdated comment
gi/boxed.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/gi/boxed.cpp b/gi/boxed.cpp
index 69b221c7..6fb6c66b 100644
--- a/gi/boxed.cpp
+++ b/gi/boxed.cpp
@@ -827,14 +827,14 @@ define_boxed_class_fields(JSContext *cx,
* error message. If we omitted fields or defined them read-only
* we'd:
*
- * - Storing a new property for a non-accessible field
+ * - Store a new property for a non-accessible field
* - Silently do nothing when writing a read-only field
*
* Which is pretty confusing if the only reason a field isn't
* writable is language binding or memory-management restrictions.
*
* We just go ahead and define the fields immediately for the
- * class; doing it lazily in boxed_new_resolve() would be possible
+ * class; doing it lazily in boxed_resolve() would be possible
* as well if doing it ahead of time caused to much start-up
* memory overhead.
*/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]