[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: [ddlm-group] A modest addition to the DDLm spec. .
- To: Group finalising DDLm and associated dictionaries <ddlm-group@iucr.org>
- Subject: Re: [ddlm-group] A modest addition to the DDLm spec. .
- From: "Bollinger, John C" <John.Bollinger@STJUDE.ORG>
- Date: Thu, 30 Sep 2010 10:11:46 -0500
- Accept-Language: en-US
- acceptlanguage: en-US
- In-Reply-To: <a06240804c8ca43f92cc2@[192.168.2.104]>
- References: <4C471374.6000100@mcmaster.ca><alpine.BSF.2.00.1007211307460.37813@epsilon.pair.com><AANLkTinyxmyKFOt=A6Cpdq=8LVsSR4+Js9xDOG+JEF--@mail.gmail.com><AANLkTimTab=b9u6nsUjd6UitRni-OgMTJNZYt1EMjrhE@mail.gmail.com><a06240804c8ca43f92cc2@[192.168.2.104]>
On Thursday, September 30, 2010 8:59 AM, Herbert J. Bernstein wrote: >The following issue came up during the encodings group discussion, but >is more properly a DDLm issue. In order to simplify algorithmic >conversion of existing CIF1 quoted strings to valid CIF2 strings, >I propose the addition of the python string concatenation operator, "+", >in CIF2 documents. The main value of this addition is to permit a >simple algorithmic conversion of CIF1 strings with embedded quote >marks to CIF2 strings that end on the first occurrence of the initial >quote. While the use of text fields will suffice in many cases, >for regular expressions it is clearer and simpler to just break the >string, insert the terminal quote mark, insert a "+" and then restart >the string with a different quote mark. > >Formally the proposal is: > >When a quoted string is given as a data value in a CIF2 document, >it may be presented as multiple quoted strings concatenated by the >"+" operator. [...] Would this issue be addressed well enough by converting single-quoted strings to triple-quoted form? I guess that wouldn't allow for breaking up regexes, so maybe it's addressed by the remark about text fields. I recognize that from time to time it is convenient to break up long, single-line values, but I'm not yet persuaded that that is sufficient justification for this feature. Adopting it would add an incremental complication to CIF parsing, and would add another incompatibility with CIF1, so the benefit should offset those costs. If breaking up regexes in particular is the motivation for this suggestion, then could that objective adequately be met by having DDLm use a regex language that allows non-significant whitespace, as Perl's comments mode does? Regards, John -- John C. Bollinger, Ph.D. Department of Structural Biology St. Jude Children's Research Hospital Email Disclaimer: www.stjude.org/emaildisclaimer _______________________________________________ ddlm-group mailing list ddlm-group@iucr.org http://scripts.iucr.org/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
- Follow-Ups:
- Re: [ddlm-group] A modest addition to the DDLm spec. . (Herbert J. Bernstein)
- References:
- [ddlm-group] import and loops in ddlm (David Brown)
- Re: [ddlm-group] import and loops in ddlm (Herbert J. Bernstein)
- Re: [ddlm-group] import and loops in ddlm (James Hester)
- Re: [ddlm-group] import and loops in ddlm (James Hester)
- [ddlm-group] A modest addition to the DDLm spec (Herbert J. Bernstein)
- Prev by Date: [ddlm-group] A modest addition to the DDLm spec
- Next by Date: Re: [ddlm-group] A modest addition to the DDLm spec
- Prev by thread: [ddlm-group] A modest addition to the DDLm spec
- Next by thread: Re: [ddlm-group] A modest addition to the DDLm spec. .
- Index(es):