Not Match: Difference between revisions
Jump to navigation
Jump to search
(Blink issue) |
m (Text replacement - "{{APL built-ins}}" to "{{APL built-ins}}Category:Primitive functions") |
||
Line 3: | Line 3: | ||
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. | 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}}[[Category:Primitive functions]] |
Revision as of 13:43, 30 April 2020
≢
|
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, 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 ≢
as ≡/
if the selected font does not have the ≢
character (U+2262), but does have ≡
(U+2261) and ̸
(U+0338). This issue can be avoided by selecting a font which is more appropriate for APL.