[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] mh-format and components with empty content
From: |
Ken Hornstein |
Subject: |
Re: [Nmh-workers] mh-format and components with empty content |
Date: |
Wed, 25 Feb 2015 21:41:59 -0500 |
>> It does occur to me that by simply adding an instruction that checked
>> to see if the "str" register was a NULL pointer or not would suffice
>> for your needs.
>
>That's what I was thinking, perhaps an `exist' function? %{exist(foo)}
I think you mean %(exist{foo}), but yeah. I was thinking that we would
want a more generic function to check to see if str == NULL ... but thinking
more about it, that's really an artifact of the current implementation.
%(exist) (and %(notexist)) would be better for the long run.
--Ken
- [Nmh-workers] mh-format and components with empty content, norm, 2015/02/25
- Re: [Nmh-workers] mh-format and components with empty content, Ken Hornstein, 2015/02/25
- Re: [Nmh-workers] mh-format and components with empty content, Ralph Corderoy, 2015/02/25
- Re: [Nmh-workers] mh-format and components with empty content,
Ken Hornstein <=
- Re: [Nmh-workers] mh-format and components with empty content, David Levine, 2015/02/25
- Re: [Nmh-workers] mh-format and components with empty content, Ken Hornstein, 2015/02/25
- Re: [Nmh-workers] mh-format and components with empty content, norm, 2015/02/26
- Re: [Nmh-workers] mh-format and components with empty content, Ken Hornstein, 2015/02/26
- Re: [Nmh-workers] mh-format and components with empty content, David Levine, 2015/02/26
- Re: [Nmh-workers] mh-format and components with empty content, norm, 2015/02/27
- Re: [Nmh-workers] mh-format and components with empty content, David Levine, 2015/02/27