Ticket #23 (closed bug: wontfix)

Opened 4 months ago

Last modified 4 months ago

True conditions

Reported by: loki Owned by:
Priority: normal Milestone: 3.9.1 alpha 2
Component: rhostmush Version: 3.9.1 alpha
Severity: bug Keywords: boolean
Cc:

Description 

> think ifelse(abc,true,false)
false
> think t(abc)
1
> think or(abc,0)
0
> think and(abc,1)
0

I think t() is the only one that follows expected behaviour.

Change History

Changed 4 months ago by Ashen-Shugar

  • status changed from new to closed
  • resolution set to wontfix

Loki, this is actually expected behavior for Rhost.

In Rhost, and like how MUX, TinyMUSH, and Penn _USED_ to behave, strings in boolean logic is seen as a false case. This is intentional for backward compatability.

To make it how it works like the 'new' codebases, it would require breaking backword compatibility and would require existing codebases that have used this condition to basically rewrite significant portions of their softcode.

I refuse to do this.

t() works as it is intended to work that way and can then be used for 'compatibility' with the current mux/tm3/penn codebases that had changed their own compatibility to make this work.

Note: See TracTickets for help on using tickets.