Not Match: Difference between revisions

Jump to navigation Jump to search
407 bytes added ,  13:48, 17 January 2020
Blink issue
(Created page with "{{Built-in|Not Match|≢}} (sometimes '''Natch''') is the negation of Match. Thus, it returns 0 when its arguments match, and 1 when they do not. Like Match...")
 
(Blink issue)
Line 1: Line 1:
{{Built-in|Not Match|≢}} (sometimes '''Natch''') is the [[Negate|negation]] of [[Match]]. Thus, it returns 0 when its [[argument]]s match, and 1 when they do not. Like Match, it is a [[dyadic]] [[primitive function]].
{{Built-in|Not Match|≢}} (sometimes '''Natch''') is the [[Negate|negation]] of [[Match]]. Thus, it returns 0 when its [[argument]]s match, and 1 when they do not. Like Match, it is a [[dyadic]] [[primitive function]].
Some rendering engines (like Blink, the rendering engine of Chromium based browsers like Chrome, Edge, and Opera) tend to render <code>≢</code> as <code>≡/</code> if the selected font  does not have the <code>≢</code> character (U+2262), but does have <code>≡</code> (U+2261) and <code> ̸</code> (U+0338). This issue can be avoided by selecting [[fonts|a font which is more appropriate]] for APL.


{{APL built-ins}}
{{APL built-ins}}

Navigation menu