Roxen.git/ server/ etc/ modules/ RXML.pmod/ module.pmod

2001-08-14

2001-08-14 17:05:42 by Martin Stjernholm <mast@lysator.liu.se>

• 69e4a4f446332a6d73fd3ccf14ee5247f89fc1d6 (15 lines) (+5/-10) ^{[ Show | Annotate ]}
  Branch: 5.2

Updated the API stability blurb.

Rev: server/etc/modules/RXML.pmod/module.pmod:1.222

2:   //   // Created 1999-07-30 by Martin Stjernholm.   // - // $Id: module.pmod,v 1.221 2001/08/14 16:59:13 mast Exp $ + // $Id: module.pmod,v 1.222 2001/08/14 17:05:42 mast Exp $      // Kludge: Must use "RXML.refs" somewhere for the whole module to be   // loaded correctly.
22:   //! namespaces. The currently implemented system is inadequate then   //! and will probably be removed.   //! @item - //! The semantics for caching and reuse of Frame objects is - //! deliberatily documented vaguely (see the class doc for the - //! Frame class). The currently implemented behavior will change - //! when the cache system becomes reality. So never assume that - //! you'll always get fresh Frame instances every time a tag is - //! evaluated. - //! @item +    //! The RXML parser module currently doesn't stream data according   //! to the interface for streaming tags (but the implementation   //! still follows the documented API for it). Therefore there's a
2389:   //! A tag instance. A new frame is normally created for every parsed   //! tag in the source document. It might be reused both when the   //! document is requested again and when the tag is reevaluated in a - //! loop, but it's not certain in either case. Therefore, be careful - //! about using variable initializers. + //! loop, but it's not certain in either case (see also @[save] and + //! @[restore]). Therefore, be careful about using variable + //! initializers.   {    constant is_RXML_Frame = 1;    constant is_RXML_encodable = 1;