[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Refreshed genx.h, plus some plans

• To: David Tolpin <dvd@d...>
• Subject: Re: Refreshed genx.h, plus some plans
• From: Rich Salz <rsalz@d...>
• Date: Sat, 24 Jan 2004 19:16:25 -0500 (EST)
• Cc: "xml-dev@l..." <xml-dev@l...>
• In-reply-to: <Pine.LNX.4.44L0.0401241910220.19941-100000@s...>

>
> Don't you want to know if genx is going to copy the pointers or copy the
> data pointed to by them?

doh, never mind that reason; typo/brain-damage.

I think it's useful to be able to know if an API is going to modify the
input parameters at all.  for example, without const, you don't know --
outside of reading the code, or perhaps the documentation -- if this will
segfault or not
    genxAddText(w, "asdfasdfasdf");
Now, that's unlikely, but the add bounded text might try to cheat and
temporarily insert a \0 byte and then replace it.  If the compiler puts
fixed text strings into read-only memory, as it is free to do, then such
a technique would probably segfault.
	/r$

--
Rich Salz                  Chief Security Architect
DataPower Technology       http://www.datapower.com
XS40 XML Security Gateway  http://www.datapower.com/products/xs40.html
XML Security Overview      http://www.datapower.com/xmldev/xmlsecurity.html

• Follow-Ups:
  • Re: Refreshed genx.h, plus some plans
    • From: David Tolpin <dvd@d...>

• References:
  • Re: Refreshed genx.h, plus some plans
    • From: Rich Salz <rsalz@d...>

• Prev by Date: RE: Microsoft files for XML patents, says C|Net
• Next by Date: Re: Refreshed genx.h, plus some plans
• Previous by thread: Re: Refreshed genx.h, plus some plans
• Next by thread: Re: Refreshed genx.h, plus some plans
• Index(es):
  • Date
  • Thread