Why is </> a TAG! and not a PATH! (or WORD!)?

This strikes me as being odd. It’s not a valid closing tag in HTML or XML, for instance. I find it natural to interpret this as ‘path from < to >’.

Generally speaking we want slashes in TAG! to work.

For close tags of course:

<head> </head>

But I don't see anything wrong with:

</head/>

I use TAG! for module relative path filenames, e.g. import <subdir/file.r> and I can imagine reasonable applications that would be directories.

The TAG! usages are plentiful and useful, and override the value of being able to call a function < with a refinement >, which never happens.

1 Like