>>Did this actually change, ... Yes, it did. I took a look at the source code of ATS-Postiats. The option -IATS seems to have been disabled. I will try to find more on this.
>>Would I need to#include these if I chose to share them between files? My own practice is to put infix declarations in a HATS file and then include the file in places where the declarations are needed. On Monday, April 2, 2018 at 6:32:22 PM UTC-4, M88 wrote: > > I have two questions... > > The first is that path resolution seems to have changed from ATS2 0.3.7 > and 0.3.9. > I used to be able to write 'staload "sats/foo.sats"' in "dats/foo.dats" > and running patscc from the project root would find the file. Now it > seems I need to > write 'staload "./../sats/foo.sats"'. Did this actually change, or am I > missing something? > Strangely, -IATS with the project root doesn't seem to be working for me > either -- at least with patscc. > I've tried both relative and absolute paths. > > The second is that infix operators consisting of non-alpha symbols (eg, > '|>') are not imported > from .sats files during staload. I can declare them in .dats files. > Would I need to > #include these if I chose to share them between files? > -- You received this message because you are subscribed to the Google Groups "ats-lang-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to ats-lang-users+unsubscr...@googlegroups.com. To post to this group, send email to ats-lang-users@googlegroups.com. Visit this group at https://groups.google.com/group/ats-lang-users. To view this discussion on the web visit https://groups.google.com/d/msgid/ats-lang-users/b1fd0c5c-46e9-4e5d-8422-592652f19d43%40googlegroups.com.
