in reply to Re^7: Regex result being defined when it shouldn't be(?)
in thread Regex result being defined when it shouldn't be(?)

A year ago, I said:

(BTW: Sorry about my use of -1 in an earlier post: I had misremembered that c defaulted to -1 for TRUE... But before making this post, I did a quickie in gcc, and saw that 1==1 really did return 1. Maybe I'm remembering some ancient compiler I used 20+ years ago. Or my memory is making this up.)

I finally figured it out.

I recently rescued and resurrected my family's old TI99-4/A (Mom was about to sell it in a garage sale!), and was reminded: In TI-BASIC, TRUE is represented by -1. You can go to http://js99er.net/, select TI BASIC, and type PRINT 1=1 to see that oddity for yourself.

  • Comment on My memory isn't as bad as I thought (Re^8: Regex result being defined when it shouldn't be(?))
  • Download Code

Replies are listed 'Best First'.
Re: My memory isn't as bad as I thought (Re^8: Regex result being defined when it shouldn't be(?))
by haukex (Archbishop) on Oct 24, 2018 at 12:52 UTC

    I have a dim memory of seeing #define TRUE (-1) somewhere, and IIRC, the accompanying documentation explained how that value was used because even if you mask it with an & or shift the value, it's still true. Haven't seen it anywhere since then, though.

Re: My memory isn't as bad as I thought (Re^8: Regex result being defined when it shouldn't be(?))
by LanX (Saint) on Oct 23, 2018 at 20:46 UTC
    Good old TI99-4/A ... after 4 hours of usage I had to put an ice pack on top to cool it down ...

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery FootballPerl is like chess, only without the dice