[redland-dev] [Raptor RDF Parsing and Serializing Library 0000351]: raptor_iostream_write_string returns incorrect value

Mantis Bug Tracker mantis-bug-sender at librdf.org
Thu Feb 18 06:56:46 CET 2010


The following issue has been SUBMITTED. 
====================================================================== 
http://bugs.librdf.org/mantis/view.php?id=351 
====================================================================== 
Reported By:                JoeAndrieu
Assigned To:                
====================================================================== 
Project:                    Raptor RDF Parsing and Serializing Library
Issue ID:                   351
Category:                   api
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Syntax Name:                 
====================================================================== 
Date Submitted:             2010-02-18 05:56
Last Modified:              2010-02-18 05:56
====================================================================== 
Summary:                    raptor_iostream_write_string returns incorrect value
Description: 
Using raptor_iostream_write_string returns failure when it appears to be
working.

In particular, it's return is given by 
=========
  return (raptor_iostream_write_bytes(iostr, string, 1, len) !=
(int)len);
=========

However, raptor_iostream_write_bytes eventually calls
raptor_stringbuffer_append_string_common which ends with the following
code:
=========
  stringbuffer->length += length;

  return 0;
=========

Which means that raptor_iostream_write_bytes is never == len unless len ==
0.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-18 05:56 JoeAndrieu     New Issue                                    
======================================================================



More information about the redland-dev mailing list