[pdf-devel] [flyspray] Type checking in type 4 functions

[GNU PDF Library]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Jose E. Marchesi (jemarch) 

Attached to Project - GNU PDF Library
Summary - Type checking in type 4 functions
Task Type - Sporadic Task
Category - FP Arithmetic Module
Status - NEXT
Assigned To - 
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - START
Due in Version - BASE-LAYER-0
Due Date - Undecided
Details - The type 4 functions implementation in pdf-fp-func.[ch] uses a stack 
of
real values.  Specific real values are used to represent TRUE, FALSE and the 
integer values.

Several problems with that approach have been identified:

- Some of the functions implemented (such as mod) requires operands of a 
specific types,
 while others (such as and,or,xor,not) have a different behavior depending on 
the type
 of the arguments.

- The resulting values in the stack left by the PDF function evaluation shall be
 real values (maybe coerced from integer values), and not booleans.  The latter shall be 
 considered an error, and reported by pdf_fp_eval as such.

To fix those problems we need to tag the elements of the stack with a explicit 
type.

See http://lists.gnu.org/archive/html/pdf-devel/2010-01/msg00016.html for more 
information.



More information can be found at the following URL:
http://gnupdf.org/flyspray/index.php?do=details&task_id=109

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.