From 20548539644cc4729b7e18ba2eefbf1956752abf Mon Sep 17 00:00:00 2001 From: Joshua Haberman Date: Sun, 4 Sep 2011 23:05:30 -0700 Subject: Header tweaking. --- upb/def.h | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'upb/def.h') diff --git a/upb/def.h b/upb/def.h index f6af798..93c0d7d 100644 --- a/upb/def.h +++ b/upb/def.h @@ -20,14 +20,14 @@ * not be used for any purpose except to set its properties (it can't be * used to parse anything, create any messages in memory, etc). * - * 2. IMMUTABLE: after being added to a symtab (which links the defs together) - * the defs become thread-safe and immutable. Programs may only access defs - * through a CONST POINTER during this stage -- upb_symtab will help you out - * with this requirement by only vending const pointers, but you need to - * make sure not to use any non-const pointers you still have sitting - * around. In practice this means that you may not call any setters on the - * defs (or functions that themselves call the setters). If you want to - * modify an existing immutable def, copy it with upb_*_dup(), modify the + * 2. FINALIZED: after being added to a symtab (which links the defs together) + * the defs become finalized (thread-safe and immutable). Programs may only + * access defs through a CONST POINTER during this stage -- upb_symtab will + * help you out with this requirement by only vending const pointers, but + * you need to make sure not to use any non-const pointers you still have + * sitting around. In practice this means that you may not call any setters + * on the defs (or functions that themselves call the setters). If you want + * to modify an existing immutable def, copy it with upb_*_dup(), modify the * copy, and add the modified def to the symtab (replacing the existing * def). * -- cgit v1.2.3