Re: heredoc usage [WAS: <OPTION]
| From: | tedd | Date: | Fri, 27 Oct 2006 16:01:32 +0000 |
| Subject: | Re: heredoc usage [WAS: <OPTION] | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-243751@lists.php.net to get a copy of this message | ||
At 10:23 AM -0700 10/26/06, Paul Novitski wrote:
At 10/26/2006 08:24 AM, tedd wrote:My bad -- spans just remind me of the old "How do we slip things in" days instead of figuring out a way to work around it. I realize that they are both tags, but as Stut reminded me, one is block and the other is line element.I think a <div> would work just as well -- <span> seems so old-world to me. :-)By default, div is a block element and span is inline, so span seemed like the natural fit for a sentence fragment. I don't think there's anything old-world (!) about spans, Tedd, they're just tags. I use both in my markup with a clear conscience.
If you want "a completely unambiguous demarcation" then use xml with a defined schema. I don't think you can get any more defined than that, right? Cheers, tedd -- ------- http://sperling.com http://ancientstones.com http://earthstones.comHowever, if you used preg_match_all, I think you could do away with the spans all together by matching FIRSTNAME to your first name variable. That way your document would simply read:That's true, and in tighly-defined micro-contexts that might work just fine. For a robust general CMS, though, I want a completely unambiguous demarcation of replacable content. All-caps tags will work in some circumstances but certainly won't in others.Hello FIRSTNAME