Be the first to post a text review of Sunifdef. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Forum thread added

  imkinghan created the Sunifdef relaunched as Coan forum thread

  posted by imkinghan 1 days ago

• Forum thread added

  thulasidhar created the #define inside source file forum thread

  posted by thulasidhar 441 days ago

• Tracker comment added

  imkinghan commented on the Filter option seems to act unexpectedly artifact

  posted by imkinghan 700 days ago

• Tracker comment added

  imkinghan commented on the constant parse error artifact

  posted by imkinghan 700 days ago

• Sunifdef 3.1.3 (stable) released.

  Six bugs are fixed in this release. Five of these fixes tackle longstanding defects of sunifdef's parsing and evaluation of integer constants - a niche that has received little scrutiny since the tool branched from unifdef. This version provides robust parsing of hex, decimal and octal numerals and arithmetic on them, plus safe integer overflow handling. However, sunifdef still evaluates all integer constants as ints and performs signed integer arithmetic uponthem. This still falls short of emulating the C preprocessor's arithmetic fully, which is an unfixed defect.

  posted by imkinghan 703 days ago

• sunifdef 3.1.3 file released: sunifdef.exe.3.1.3

  sunifdef v3.1.3 Mike Kinghan 2008-01-19 *Fix: DEF0041: When -DSYM=VAL is specified with VAL a hex integer constant, rather than a decimal constant, sunifdef would fail to resolve SYM in expressions unless the --constant eval was specified, which should be unnecessary. The anomaly ocurred because eval_symbol() anticipated constant values only as decimal constants and, upon encountering a hex-prefix "0x" or "OX" would attempt to parse the token as an expression, invoking eval_table() and ultimately eval_unary(). The latter function _would_ resolve a hex constant, but only if --constant eval is in effect, since the function is assumed to operate on source text rather than on the definiens of -DSYM=VAL. The fix consists in recognising hex constants as such in eval_symbol(). *Fix: DEF0042: When -DSYM=VAL is specified with VAL a soluble expression containing at least one integer constant operand, sunifdef would fail to resolve SYM in expressions unless --constant eval was specified. The reason is the same as in bug DEF0041. The fix consists in recording the origin of the text upon which eval_unary() is called - source text or else the definiens of a --defined symbol - and always resolving integer contstants in the latter case. *Fix: DEF0043: sunifdef did not distinguish octal numerals as integer constants and evaluated them as decimal numerals. *Fix: DEF0044: sunifdef did not recognise the suffixes u/U, l/L as belonging to integer constants. These suffixes are now recognised; however, sunifdef still evaluates all integer constants as ints and performs signed integer arithmetic upon them. This is unfixed bug. *Fix: DEF0045: sunifdef did not detect integer overflow in evaluating constants. Now detects overflow whenever the value of a constant will exceed INT_MAX and leaves the constant unresolved with a warning to that effect. *Fix: DEF0046: The --help message contained an occurrence of '--constants' that ought to have been '--constant'.

  posted 703 days ago

• sunifdef 3.1.3 file released: sunifdef-3.1.3.tar.gz

  sunifdef v3.1.3 Mike Kinghan 2008-01-19 *Fix: DEF0041: When -DSYM=VAL is specified with VAL a hex integer constant, rather than a decimal constant, sunifdef would fail to resolve SYM in expressions unless the --constant eval was specified, which should be unnecessary. The anomaly ocurred because eval_symbol() anticipated constant values only as decimal constants and, upon encountering a hex-prefix "0x" or "OX" would attempt to parse the token as an expression, invoking eval_table() and ultimately eval_unary(). The latter function _would_ resolve a hex constant, but only if --constant eval is in effect, since the function is assumed to operate on source text rather than on the definiens of -DSYM=VAL. The fix consists in recognising hex constants as such in eval_symbol(). *Fix: DEF0042: When -DSYM=VAL is specified with VAL a soluble expression containing at least one integer constant operand, sunifdef would fail to resolve SYM in expressions unless --constant eval was specified. The reason is the same as in bug DEF0041. The fix consists in recording the origin of the text upon which eval_unary() is called - source text or else the definiens of a --defined symbol - and always resolving integer contstants in the latter case. *Fix: DEF0043: sunifdef did not distinguish octal numerals as integer constants and evaluated them as decimal numerals. *Fix: DEF0044: sunifdef did not recognise the suffixes u/U, l/L as belonging to integer constants. These suffixes are now recognised; however, sunifdef still evaluates all integer constants as ints and performs signed integer arithmetic upon them. This is unfixed bug. *Fix: DEF0045: sunifdef did not detect integer overflow in evaluating constants. Now detects overflow whenever the value of a constant will exceed INT_MAX and leaves the constant unresolved with a warning to that effect. *Fix: DEF0046: The --help message contained an occurrence of '--constants' that ought to have been '--constant'.

  posted 703 days ago

• sunifdef 3.1.3 file released: sunifdef-3.1.3-1.strudl.x86_64.rpm

  sunifdef v3.1.3 Mike Kinghan 2008-01-19 *Fix: DEF0041: When -DSYM=VAL is specified with VAL a hex integer constant, rather than a decimal constant, sunifdef would fail to resolve SYM in expressions unless the --constant eval was specified, which should be unnecessary. The anomaly ocurred because eval_symbol() anticipated constant values only as decimal constants and, upon encountering a hex-prefix "0x" or "OX" would attempt to parse the token as an expression, invoking eval_table() and ultimately eval_unary(). The latter function _would_ resolve a hex constant, but only if --constant eval is in effect, since the function is assumed to operate on source text rather than on the definiens of -DSYM=VAL. The fix consists in recognising hex constants as such in eval_symbol(). *Fix: DEF0042: When -DSYM=VAL is specified with VAL a soluble expression containing at least one integer constant operand, sunifdef would fail to resolve SYM in expressions unless --constant eval was specified. The reason is the same as in bug DEF0041. The fix consists in recording the origin of the text upon which eval_unary() is called - source text or else the definiens of a --defined symbol - and always resolving integer contstants in the latter case. *Fix: DEF0043: sunifdef did not distinguish octal numerals as integer constants and evaluated them as decimal numerals. *Fix: DEF0044: sunifdef did not recognise the suffixes u/U, l/L as belonging to integer constants. These suffixes are now recognised; however, sunifdef still evaluates all integer constants as ints and performs signed integer arithmetic upon them. This is unfixed bug. *Fix: DEF0045: sunifdef did not detect integer overflow in evaluating constants. Now detects overflow whenever the value of a constant will exceed INT_MAX and leaves the constant unresolved with a warning to that effect. *Fix: DEF0046: The --help message contained an occurrence of '--constants' that ought to have been '--constant'.

  posted 703 days ago

• sunifdef 3.1.3 file released: sunifdef-3.1.3-1.strudl.src.rpm

  sunifdef v3.1.3 Mike Kinghan 2008-01-19 *Fix: DEF0041: When -DSYM=VAL is specified with VAL a hex integer constant, rather than a decimal constant, sunifdef would fail to resolve SYM in expressions unless the --constant eval was specified, which should be unnecessary. The anomaly ocurred because eval_symbol() anticipated constant values only as decimal constants and, upon encountering a hex-prefix "0x" or "OX" would attempt to parse the token as an expression, invoking eval_table() and ultimately eval_unary(). The latter function _would_ resolve a hex constant, but only if --constant eval is in effect, since the function is assumed to operate on source text rather than on the definiens of -DSYM=VAL. The fix consists in recognising hex constants as such in eval_symbol(). *Fix: DEF0042: When -DSYM=VAL is specified with VAL a soluble expression containing at least one integer constant operand, sunifdef would fail to resolve SYM in expressions unless --constant eval was specified. The reason is the same as in bug DEF0041. The fix consists in recording the origin of the text upon which eval_unary() is called - source text or else the definiens of a --defined symbol - and always resolving integer contstants in the latter case. *Fix: DEF0043: sunifdef did not distinguish octal numerals as integer constants and evaluated them as decimal numerals. *Fix: DEF0044: sunifdef did not recognise the suffixes u/U, l/L as belonging to integer constants. These suffixes are now recognised; however, sunifdef still evaluates all integer constants as ints and performs signed integer arithmetic upon them. This is unfixed bug. *Fix: DEF0045: sunifdef did not detect integer overflow in evaluating constants. Now detects overflow whenever the value of a constant will exceed INT_MAX and leaves the constant unresolved with a warning to that effect. *Fix: DEF0046: The --help message contained an occurrence of '--constants' that ought to have been '--constant'.

  posted 703 days ago

• sunifdef 3.1.3 file released: sunifdef-3.1.3-1.strudl.i586.rpm

  sunifdef v3.1.3 Mike Kinghan 2008-01-19 *Fix: DEF0041: When -DSYM=VAL is specified with VAL a hex integer constant, rather than a decimal constant, sunifdef would fail to resolve SYM in expressions unless the --constant eval was specified, which should be unnecessary. The anomaly ocurred because eval_symbol() anticipated constant values only as decimal constants and, upon encountering a hex-prefix "0x" or "OX" would attempt to parse the token as an expression, invoking eval_table() and ultimately eval_unary(). The latter function _would_ resolve a hex constant, but only if --constant eval is in effect, since the function is assumed to operate on source text rather than on the definiens of -DSYM=VAL. The fix consists in recognising hex constants as such in eval_symbol(). *Fix: DEF0042: When -DSYM=VAL is specified with VAL a soluble expression containing at least one integer constant operand, sunifdef would fail to resolve SYM in expressions unless --constant eval was specified. The reason is the same as in bug DEF0041. The fix consists in recording the origin of the text upon which eval_unary() is called - source text or else the definiens of a --defined symbol - and always resolving integer contstants in the latter case. *Fix: DEF0043: sunifdef did not distinguish octal numerals as integer constants and evaluated them as decimal numerals. *Fix: DEF0044: sunifdef did not recognise the suffixes u/U, l/L as belonging to integer constants. These suffixes are now recognised; however, sunifdef still evaluates all integer constants as ints and performs signed integer arithmetic upon them. This is unfixed bug. *Fix: DEF0045: sunifdef did not detect integer overflow in evaluating constants. Now detects overflow whenever the value of a constant will exceed INT_MAX and leaves the constant unresolved with a warning to that effect. *Fix: DEF0046: The --help message contained an occurrence of '--constants' that ought to have been '--constant'.

  posted 703 days ago