Ticket #160 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

Sequence of conditional logic in <IF> bvlock

Reported by: forthmedia Owned by: scorfield
Type: defect Priority: normal
Milestone: Fusebox 5.1 Component: Fuxebox 4.1 Compatibility
Version: 5.0 Severity: normal
Keywords: Cc:

Description

In <IF>..</IF> blocks the <TRUE><FALSE> blocks must be coded in this order. Otherwise if coded <FALSE> then <TRUE> the <TRUE> block is ignored (not compiled into the parsed files). If this is a syntax requirement then it impacts backward compatibility becasue FB41 doesn't care about the order.

I also heard that both <TRUE> and <FALSE> where required (optional in FB41) however my tests demonstrate that <TRUE> or <FALSE> blocks coded by themselves perform as expected.

Attachments

Change History

Changed 2 years ago by scorfield

  • owner changed from sean@corfield.org to scorfield
  • status changed from new to assigned
  • milestone set to Fusebox 5.1

Verified.

Changed 2 years ago by scorfield

  • status changed from assigned to closed
  • resolution set to fixed

(In [257]) Fixes #160 by pushing generation of condition down into true/false. Added test case.

Changed 2 years ago by scorfield

(In [305]) Fixes #177 by putting parentheses around the condition in the no-if case.
This was a leftover bug from changelist [257] which attempted to fix #160.

Note: See TracTickets for help on using tickets.