X-Git-Url: https://git.dlugolecki.net.pl/?a=blobdiff_plain;f=doc%2Finterface.html;h=c27e3d07664a6cc826670865b420eddb2b47700b;hb=5c54a356fc4542790b2667edcd369ed99f688712;hp=74d5aadd0886d5fac92f5dcaa297705f68efd05a;hpb=1316fee80103b38bf682f5c626c0abaa525db41c;p=gedcom-parse.git diff --git a/doc/interface.html b/doc/interface.html index 74d5aad..c27e3d0 100644 --- a/doc/interface.html +++ b/doc/interface.html @@ -1,11 +1,9 @@ - - -
-GEDCOM_STRING(val)
is always the same as the
+raw_value
passed to the start callback, and is thus in fact redundant.-These are represented by 2 serial day numbers (- sdn1
andsdn2
) and aDate_type
equal +These are represented by 2 serial day numbers (sdn1
andsdn2
) and aDate_type
equal toDATE_BOUNDED
.
For example, the Gregorian date "MAR 1990" is represented by the serial @@ -2124,16 +2121,17 @@ with the cross-reference, and then later extracted when the cross-reference is used or defined again in the file. This relieves the application from the burden of maintaining the mapping between cross-references and objects.
- The parser checks whether all cross-references that are used are defined -(if not, an error is produced) and whether all cross-references that are defined -are used (if not, a warning is produced). It also checks whether the -type of the cross-reference is the same on definition and use (if not, an -error is produced).
+ The parser checks whether all cross-references that are used are defined + (if not, an error is produced) and whether all cross-references that are +defined are used (if not, a warning is produced). It also checks whether +the type of the cross-reference is the same on definition and use (if not, +an error is produced). The first two checks are done at the end of +the parsing, because cross-references can be defined after their usage in +GEDCOM.
$Id$
$Name$
- - + \ No newline at end of file