gedcom-parse-devel

RE: [Gedcom-parse-devel] Re: Gedcom-parse

[Geert V. <Gee...@ad...>]

>===== Original Message From Peter Verthez <Pet...@ad...> =====
>Geert Vantienen wrote:
>>
>> Hello Peter,
>>
>> In the callbacks you now pass the tag as a char*,
>> is it possible to pass them as enum value as they
>> are defined in the gedcom.h file ?
>
>No problem, but then you'll need both, because if I just pass
>e.g. ELT_SUB_INDIV_GEN, then you won't know which tag it really
>was.
>
>Or did you mean passing them as TAG_BIRT, TAG_DEAT, ... ?  Those
>are not defined in gedcom.h, but in the header generated by
>YACC.  But maybe that would even be better.

I was talking about TAG_DEAT, ... they were not defined in gedcom.h ?
oops, I thought they were ...

 I'll see whether
>I can move these to gedcom.h.  But then also, you'll need the
>original char* value to, at least for the user-defined tags.

That is not a problem ...

Thanks,
Geert

Re: [Gedcom-parse-devel] Re: Gedcom-parse

[Peter V. <Pet...@ad...>]

Hi Geert,

I've added an argument to the callbacks: the parsed tag value.
I've updated the docs also (usage.html).

The #define's are in gedcom-tags.h, but you won't find it
in CVS: it's autogenerated when you do 'make'.

Cheers,
Peter.

PS. Don't do too much on xref's yet.  I'm now going to make an
interface for it (=E0 la GEDCOM_DATE, but then GEDCOM_XREF_PTR)
and implement checking.


Geert Vantienen wrote:
>=20
> >=3D=3D=3D=3D=3D Original Message From Peter Verthez <Peter.Verthez@adv=
alvas.be> =3D=3D=3D=3D=3D
> >Geert Vantienen wrote:
> >>
> >> Hello Peter,
> >>
> >> In the callbacks you now pass the tag as a char*,
> >> is it possible to pass them as enum value as they
> >> are defined in the gedcom.h file ?
> >
> >No problem, but then you'll need both, because if I just pass
> >e.g. ELT_SUB_INDIV_GEN, then you won't know which tag it really
> >was.
> >
> >Or did you mean passing them as TAG_BIRT, TAG_DEAT, ... ?  Those
> >are not defined in gedcom.h, but in the header generated by
> >YACC.  But maybe that would even be better.
>=20
> I was talking about TAG_DEAT, ... they were not defined in gedcom.h ?
> oops, I thought they were ...
>=20
>  I'll see whether
> >I can move these to gedcom.h.  But then also, you'll need the
> >original char* value to, at least for the user-defined tags.
>=20
> That is not a problem ...
>=20
> Thanks,
> Geert
>=20
> _______________________________________________
> Gedcom-parse-devel mailing list
> Ged...@li...
> https://lists.sourceforge.net/lists/listinfo/gedcom-parse-devel

--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Peter Verthez                                     Software engineer
Email at work:                      mailto:Pet...@al...
      at home:                     mailto:Pet...@ad...
WWW:                          http://gallery.uunet.be/Peter.Verthez
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Customer: "What do you mean, other tape? When it said second
volume, I just hit enter again."