in reply to Standalone Code Tag
I can see where this would be desireable (after all, no one wants to type more than necessary), but two thoughts come to mind:
Any good editor provides shortcuts that can help.
If you compose off-line, as I often do, try using your editor to design a short macro/template/whatever that a) adds <CODE> </CODE> tags, b) positions the cursor between them, and c) binds the results to a control sequence. You'd get the same benefit without adding work to Fearless's ToDo list.
Given the shift toward a more strict SGML base in HTML and so on, closing tags are a good habit to get into. For example, certain browsers will not apply styles to paragraphs unless you supply the </P> tag.
At the very least, closing tags help make nodes a little easier to process using XML.
Saving time is a good thing. However, we often tell people to use warnings and to use strict for very good reasons. It's extra code (or extra work in the macros/templates/etc), but good practice. To my mind, closing tags are just as good practice.
--f
|
|---|