Discussion List Archives

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CIF-JSON draft 2017-05-08

On 11 May 2017 at 08:28, James Hester <jamesrhester@gmail.com> wrote:> The problem with requiring that CIF numbers = JSON numbers is that it is not> generally possible for a CIF->JSON parser to know when a CIF value is a> number instead of simply a non-delimited string that looks like a number.
I forgot about it. Indeed, it's a valid argument.
When I started experimenting with CIF parser a few months ago Inoticed that some programs (I think cif2cif was one of them) justtreat what looks like a number as a number, ignoring the ambiguityleft in the CIF spec. But this indeed would not be fully specconforming. Forget about my previous email.
> The consumer of the JSON, on the other hand, will know which of the> datanames that it cares about are numeric and perform the conversion (as per> CIF rules, I don't know if the C++17 standard is relevant here).
I meant that there is no simple way to a write numb parser in C/C++ otherwise.
Marcin_______________________________________________cif-developers mailing listcif-developers@iucr.orghttp://mailman.iucr.org/cgi-bin/mailman/listinfo/cif-developers

Reply to: [list | sender only]
International Union of Crystallography

Scientific Union Member of the International Council for Science (admitted 1947). Member of CODATA, the ICSU Committee on Data. Member of ICSTI, the International Council for Scientific and Technical Information. Partner with UNESCO, the United Nations Educational, Scientific and Cultural Organization in the International Year of Crystallography 2014.

ICSU Scientific Freedom Policy

The IUCr observes the basic policy of non-discrimination and affirms the right and freedom of scientists to associate in international scientific activity without regard to such factors as ethnic origin, religion, citizenship, language, political stance, gender, sex or age, in accordance with the Statutes of the International Council for Science.