> Levi Pearson wrote:
>
>> This version should address the issues from the review of the previous
>> patch.  I've tested this one a bit more and it seems pretty solid to me.
>
> This is probably a very uncommon use case: Since the "0x" prefix is used
> for specifying keys in hex format you cannot encode keys that actually
> start with a literal "0x" in string format. This is probably a very
> uncommon use case, but you should still fall back to hex syntax in this
> case. Otherwise format_kg() might format a key in a way that can't be
> read by parse_kg().

I had thought about this as well.  Thinking that perhaps an escape
character could be used to escape the '0x'.  But like you said, it is an
extremely unlikely use case and figured the tradeoff/effort wasn't worth
it.

Al

> Cheers,
> Ingo
>
>
> _______________________________________________
> Freeipmi-devel mailing list
> Freeipmi-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/freeipmi-devel
>


-- 
Albert Chu
[EMAIL PROTECTED]
925-422-5311
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory



_______________________________________________
Freeipmi-devel mailing list
Freeipmi-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/freeipmi-devel

Reply via email to