[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [External] : Re: master 6eeab90632: Don't accept whitespace or hex f
From: |
Drew Adams |
Subject: |
RE: [External] : Re: master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs |
Date: |
Mon, 7 Mar 2022 16:06:05 +0000 |
> If the happenstance doesn't cause trouble, there is no need to get rid
> of it.
As I suggested, mentioning other, similar contexts:
But if you want/need to know _whether_ some
data is well-formed ______ according to the
standard, then you don't want to allow data
that's not well-formed.
Whether or not you want to support such a use case,
i.e., _checking_ whether something is ONLY an rgbi
code and not something that also includes whitespace,
is up to you. But it's easy to provide users with
both behaviors, by adding an optional arg (LAX or
STRICT), depending on what you want the default
behavior to be.
- Re: master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs, (continued)
- Re: master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs, Mattias Engdegård, 2022/03/06
- Re: master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs, Mattias Engdegård, 2022/03/07
- Re: master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs, Po Lu, 2022/03/07
- Re: master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs, Mattias Engdegård, 2022/03/07
- Re: master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs, Po Lu, 2022/03/07
- RE: [External] : Re: master 6eeab90632: Don't accept whitespace or hex floats in rgbi: colour specs,
Drew Adams <=