<div dir="ltr">Cool :) That looks good.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 3 May 2016 at 13:51, Joe Leslie-Hurd <span dir="ltr"><<a href="mailto:joe@gilith.com" target="_blank">joe@gilith.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Ramana,<br>
<br>
Following your suggestion I've written documentation for the<br>
interpretation files:<br>
<br>
<a href="http://www.gilith.com/research/opentheory/interpretation.html" rel="noreferrer" target="_blank">http://www.gilith.com/research/opentheory/interpretation.html</a><br>
<br>
I've also converted all of my theories on the Gilith repo to use<br>
interpretation files rather than interpret: lines, because it's easier<br>
to read and keep in sync with my HOL Light source theories.<br>
<br>
Cheers,<br>
<br>
Joe<br>
<div class="HOEnZb"><div class="h5"><br>
On Mon, Apr 25, 2016 at 11:54 PM, Joe Leslie-Hurd <<a href="mailto:joe@gilith.com">joe@gilith.com</a>> wrote:<br>
> Yes, the documentation could definitely be improved by describing<br>
> interpretation files. Your reverse engineering is quite correct, plus<br>
> comments are also allowed. For an example take a look at the<br>
> interpretation file used by the latest version of the byte-def theory:<br>
><br>
> <a href="http://opentheory.gilith.com/opentheory/packages/byte-def-1.98/word.int" rel="noreferrer" target="_blank">http://opentheory.gilith.com/opentheory/packages/byte-def-1.98/word.int</a><br>
><br>
> Cheers,<br>
><br>
> Joe<br>
><br>
><br>
><br>
> On Mon, Apr 25, 2016 at 11:30 PM, Ramana Kumar <<a href="mailto:ramana@member.fsf.org">ramana@member.fsf.org</a>> wrote:<br>
>> Hi Joe,<br>
>><br>
>> Thanks for implementing this!<br>
>><br>
>> I think the documentation isn't very clear about what interpretation files<br>
>> should contain. However, I think I figured it out to some extent: They<br>
>> should have lines like the "interpret:" lines except without the leading<br>
>> "interpret:", and blank lines are allowed.<br>
>><br>
>> I'm trying it out more now, and will let you know if I run into anything.<br>
>><br>
>> Cheers,<br>
>> Ramana<br>
>><br>
>> On 24 April 2016 at 16:58, Joe Leslie-Hurd <<a href="mailto:joe@gilith.com">joe@gilith.com</a>> wrote:<br>
>>><br>
>>> Hi Ramana,<br>
>>><br>
>>> The latest version of the opentheory tool (release 20160423) now<br>
>>> includes support for<br>
>>><br>
>>> interpretation: "<a href="http://file.int" rel="noreferrer" target="_blank">file.int</a>"<br>
>>><br>
>>> lines in theory files, as documented here:<br>
>>><br>
>>> <a href="http://www.gilith.com/research/opentheory/theory.html" rel="noreferrer" target="_blank">http://www.gilith.com/research/opentheory/theory.html</a><br>
>>><br>
>>> It's lightly tested, so please let me know if you discover anything<br>
>>> odd with the new feature.<br>
>>><br>
>>> Cheers,<br>
>>><br>
>>> Joe<br>
>>><br>
>>> On Wed, Apr 20, 2016 at 9:37 PM, Ramana Kumar <<a href="mailto:ramana@member.fsf.org">ramana@member.fsf.org</a>><br>
>>> wrote:<br>
>>> > Cool. Thanks!<br>
>>> ><br>
>>> > On 21 April 2016 at 02:40, Joe Leslie-Hurd <<a href="mailto:joe@gilith.com">joe@gilith.com</a>> wrote:<br>
>>> >><br>
>>> >> By the way, I am working on adding this feature, but for various<br>
>>> >> technical reasons of how the code is structured it's turning out to be<br>
>>> >> non-trivial. I'll let you know when the feature is added.<br>
>>> >><br>
>>> >> Cheers,<br>
>>> >><br>
>>> >> Joe<br>
>>> >><br>
>>> >> On Sun, Apr 3, 2016 at 10:16 PM, Joe Leslie-Hurd <<a href="mailto:joe@gilith.com">joe@gilith.com</a>><br>
>>> >> wrote:<br>
>>> >> > Sure thing, I'll work on adding this feature.<br>
>>> >> ><br>
>>> >> > Cheers,<br>
>>> >> ><br>
>>> >> > Joe<br>
>>> >> ><br>
>>> >> > On Fri, Apr 1, 2016 at 3:41 PM, Ramana Kumar <<a href="mailto:ramana@member.fsf.org">ramana@member.fsf.org</a>><br>
>>> >> > wrote:<br>
>>> >> >> Hi Joe,<br>
>>> >> >><br>
>>> >> >> I would like to reopen this request. It seems like I'm going to be<br>
>>> >> >> copying<br>
>>> >> >> interpretations around a lot again.<br>
>>> >> >><br>
>>> >> >> Cheers,<br>
>>> >> >> Ramana<br>
>>> >> >><br>
>>> >> >> On 4 March 2016 at 12:14, Ramana Kumar <<a href="mailto:ramana@member.fsf.org">ramana@member.fsf.org</a>><br>
>>> >> >> wrote:<br>
>>> >> >>><br>
>>> >> >>> Hi Joe,<br>
>>> >> >>><br>
>>> >> >>> It turns out this is not so urgent for me since Michael and I came<br>
>>> >> >>> up<br>
>>> >> >>> with<br>
>>> >> >>> another method:<br>
>>> >> >>> Put all the article-combination stuff into one file<br>
>>> >> >>> uninterpreted.thy<br>
>>> >> >>> (main block is a union), then turn that into uninterpreted.art, and<br>
>>> >> >>> finally<br>
>>> >> >>> do the interpretation all at once (so it only appears in one file)<br>
>>> >> >>> in<br>
>>> >> >>> interpreted.thy, whose main block is an article block for<br>
>>> >> >>> "uninterpreted.art".<br>
>>> >> >>><br>
>>> >> >>> However, interpretations from files would probably still be good<br>
>>> >> >>> for<br>
>>> >> >>> other<br>
>>> >> >>> scenarios. I would tweak your suggested syntax to use<br>
>>> >> >>> "interpretation"<br>
>>> >> >>> rather than "interpret-file", to match "article" (which also takes<br>
>>> >> >>> a<br>
>>> >> >>> filename).<br>
>>> >> >>><br>
>>> >> >>> Cheers,<br>
>>> >> >>> Ramana<br>
>>> >> >>><br>
>>> >> >>> On 5 March 2016 at 05:51, Joe Leslie-Hurd <<a href="mailto:joe@gilith.com">joe@gilith.com</a>> wrote:<br>
>>> >> >>>><br>
>>> >> >>>> Hi Ramana,<br>
>>> >> >>>><br>
>>> >> >>>> I agree with you that it would be good for theory files to support<br>
>>> >> >>>> pulling in interpretations from files. How about the following<br>
>>> >> >>>> syntax:<br>
>>> >> >>>><br>
>>> >> >>>> interpret-file: "<a href="http://file.int" rel="noreferrer" target="_blank">file.int</a>"<br>
>>> >> >>>><br>
>>> >> >>>> inside a theory block? It probably makes sense to allow multiple<br>
>>> >> >>>> of<br>
>>> >> >>>> these, just like multiple<br>
>>> >> >>>><br>
>>> >> >>>> interpret: type/const "X" as "Y"<br>
>>> >> >>>><br>
>>> >> >>>> lines are allowed, but raise an error if the same symbol is<br>
>>> >> >>>> interpreted in multiple ways.<br>
>>> >> >>>><br>
>>> >> >>>> Cheers,<br>
>>> >> >>>><br>
>>> >> >>>> Joe<br>
>>> >> >>>><br>
>>> >> >>>> On Thu, Mar 3, 2016 at 4:21 PM, Ramana Kumar<br>
>>> >> >>>> <<a href="mailto:ramana@member.fsf.org">ramana@member.fsf.org</a>><br>
>>> >> >>>> wrote:<br>
>>> >> >>>> > Is it possible to include an interpretation in a theory file,<br>
>>> >> >>>> > rather<br>
>>> >> >>>> > than<br>
>>> >> >>>> > having to write it out inline? Since I sometimes want to include<br>
>>> >> >>>> > a<br>
>>> >> >>>> > rather<br>
>>> >> >>>> > large interpretation within multiple blocks within the same<br>
>>> >> >>>> > theory<br>
>>> >> >>>> > file, I<br>
>>> >> >>>> > end up having to write a template file and then generate the<br>
>>> >> >>>> > real<br>
>>> >> >>>> > .thy<br>
>>> >> >>>> > file<br>
>>> >> >>>> > from that, to avoid lots of copy-pasting. Is mine the<br>
>>> >> >>>> > recommended<br>
>>> >> >>>> > approach,<br>
>>> >> >>>> > or is there a better way?<br>
>>> >> >>>> ><br>
>>> >> >>>> > _______________________________________________<br>
>>> >> >>>> > opentheory-users mailing list<br>
>>> >> >>>> > <a href="mailto:opentheory-users@gilith.com">opentheory-users@gilith.com</a><br>
>>> >> >>>> > <a href="http://www.gilith.com/opentheory/mailing-list" rel="noreferrer" target="_blank">http://www.gilith.com/opentheory/mailing-list</a><br>
>>> >> >>>> ><br>
>>> >> >>>><br>
>>> >> >>>> _______________________________________________<br>
>>> >> >>>> opentheory-users mailing list<br>
>>> >> >>>> <a href="mailto:opentheory-users@gilith.com">opentheory-users@gilith.com</a><br>
>>> >> >>>> <a href="http://www.gilith.com/opentheory/mailing-list" rel="noreferrer" target="_blank">http://www.gilith.com/opentheory/mailing-list</a><br>
>>> >> >>><br>
>>> >> >>><br>
>>> >> >><br>
>>> >> >><br>
>>> >> >> _______________________________________________<br>
>>> >> >> opentheory-users mailing list<br>
>>> >> >> <a href="mailto:opentheory-users@gilith.com">opentheory-users@gilith.com</a><br>
>>> >> >> <a href="http://www.gilith.com/opentheory/mailing-list" rel="noreferrer" target="_blank">http://www.gilith.com/opentheory/mailing-list</a><br>
>>> >> >><br>
>>> >><br>
>>> >> _______________________________________________<br>
>>> >> opentheory-users mailing list<br>
>>> >> <a href="mailto:opentheory-users@gilith.com">opentheory-users@gilith.com</a><br>
>>> >> <a href="http://www.gilith.com/opentheory/mailing-list" rel="noreferrer" target="_blank">http://www.gilith.com/opentheory/mailing-list</a><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > _______________________________________________<br>
>>> > opentheory-users mailing list<br>
>>> > <a href="mailto:opentheory-users@gilith.com">opentheory-users@gilith.com</a><br>
>>> > <a href="http://www.gilith.com/opentheory/mailing-list" rel="noreferrer" target="_blank">http://www.gilith.com/opentheory/mailing-list</a><br>
>>> ><br>
>>><br>
>>> _______________________________________________<br>
>>> opentheory-users mailing list<br>
>>> <a href="mailto:opentheory-users@gilith.com">opentheory-users@gilith.com</a><br>
>>> <a href="http://www.gilith.com/opentheory/mailing-list" rel="noreferrer" target="_blank">http://www.gilith.com/opentheory/mailing-list</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> opentheory-users mailing list<br>
>> <a href="mailto:opentheory-users@gilith.com">opentheory-users@gilith.com</a><br>
>> <a href="http://www.gilith.com/opentheory/mailing-list" rel="noreferrer" target="_blank">http://www.gilith.com/opentheory/mailing-list</a><br>
>><br>
<br>
_______________________________________________<br>
opentheory-users mailing list<br>
<a href="mailto:opentheory-users@gilith.com">opentheory-users@gilith.com</a><br>
<a href="http://www.gilith.com/opentheory/mailing-list" rel="noreferrer" target="_blank">http://www.gilith.com/opentheory/mailing-list</a><br>
</div></div></blockquote></div><br></div>