Thanks, folks, my mistake again. Looking upon <a href=""> as a datatype delimited by <
and > was smart, thanks. It makes sense now. I no longer consider my workaround as a
workaround, but as the way to do it. (To print a tag followed by a linebreak: print
join form <a href=""> "^/").
~H
Dixit Carl Read (00.43 27.01.2002):
>On 27-Jan-02, Hallvard Ystad wrote:
>
>> Hi again
>
>> OK, so I accept that RT wants all characters in tags to be
>> accessible, so that <a href=""> and <a href = ""> are not alike. But
>> how about this:
>
>>>> print <a href="">
>> <a href="">
>>>> print join <a href=""> "^/"
>> <a href=""
>>>
>>>>
>
>> It seems JOIN <a href=""> "^/" puts in the linebreak too early. Or
>> am I mistaken again? If I FORM or MOLD the TAG!, it seems to work
>> fine...
>
>You're mistaken again. (: 'join determines the type of what's returned
>by the first value it's given, (in certain cases), so this returns a
>tag...
>
>>> a: join <a href=""> "^/"
>== <a href=""
>>
>>> type? a
>== tag!
>
>and this a string...
>
>>> a: join "^/" <a href="">
>== {
><a href="">}
>>> type? a
>== string!
>
>I said "in certain cases" as it returns a string where joining to a
>datatype doesn't make sense, as with numbers...
>
>>> join 10 20
>== "1020"
>
>HTH.
>
>--
>Carl Read
>
>--
>To unsubscribe from this list, please send an email to
>[EMAIL PROTECTED] with "unsubscribe" in the
>subject, without the quotes.
Pr�tera censeo Carthaginem esse delendam
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
