Menu
▾
▴
czt-devel — For programmers using the CZT code
This list is closed, nobody may subscribe to it.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(2) |
Feb
(15) |
Mar
(10) |
Apr
(1) |
May
(1) |
Jun
(4) |
Jul
(2) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2005 |
Jan
(3) |
Feb
(17) |
Mar
(6) |
Apr
(13) |
May
(17) |
Jun
(53) |
Jul
(36) |
Aug
(29) |
Sep
(17) |
Oct
(21) |
Nov
(37) |
Dec
(25) |
| 2006 |
Jan
|
Feb
(29) |
Mar
(85) |
Apr
(27) |
May
(25) |
Jun
(57) |
Jul
(3) |
Aug
(8) |
Sep
(24) |
Oct
(43) |
Nov
(22) |
Dec
(10) |
| 2007 |
Jan
(29) |
Feb
(38) |
Mar
(11) |
Apr
(29) |
May
(16) |
Jun
(1) |
Jul
(20) |
Aug
(25) |
Sep
(6) |
Oct
(25) |
Nov
(16) |
Dec
(14) |
| 2008 |
Jan
(18) |
Feb
(12) |
Mar
(3) |
Apr
(1) |
May
(23) |
Jun
(3) |
Jul
(7) |
Aug
|
Sep
(16) |
Oct
(27) |
Nov
(16) |
Dec
(7) |
| 2009 |
Jan
(1) |
Feb
(12) |
Mar
|
Apr
(16) |
May
(2) |
Jun
(4) |
Jul
|
Aug
(4) |
Sep
(7) |
Oct
(12) |
Nov
(8) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(8) |
Jul
|
Aug
(11) |
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
| 2011 |
Jan
(14) |
Feb
(20) |
Mar
(3) |
Apr
(1) |
May
(1) |
Jun
(23) |
Jul
(1) |
Aug
(3) |
Sep
(5) |
Oct
(19) |
Nov
(1) |
Dec
(5) |
| 2012 |
Jan
(19) |
Feb
(4) |
Mar
|
Apr
(1) |
May
(2) |
Jun
(7) |
Jul
(33) |
Aug
(3) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(3) |
Apr
(48) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(15) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(9) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: ky582 <ky...@yo...> - 2015-08-10 08:40:45
|
Hi Andrius, Thanks a lot for your update. I might try Java 8 and Eclipse Mars later. Any problem, I will let you know. Regards, Randall > On 8 Aug 2015, at 10:59, Andrius Velykis <and...@ne...> wrote: > > Hi Randall and XING Chang, > > Sorry about the build problems - they are still being solved so please report what you find. Also SourceForge was not working for the last couple weeks so I could not update what is needed. > > I have just updated the update site at http://czt.sourceforge.net/dev/eclipse/updates/ <http://czt.sourceforge.net/dev/eclipse/updates/> - a bit of manual job, but now it should point to the correct m2e connector update sites (they have changed locations since the last CZT updates). > > Also, could you try using Eclipse Mars with Java 8, Maven 3.3.3 and the version of m2e that comes with Mars? I have tried fixing so it works with the recent versions but have not tested with older ones. > > With this configuration (Java 8, Maven 3.3.3, Eclipse Mars), the import of CZT works. There may be a bit of issues with dependency resolution in net.sourceforge.czt.eclipse.ui (known issue) but I have not found a way to resolve it yet or what causes the problem. > > Also, the instructions in http://czt.sourceforge.net/dev/eclipse/ <http://czt.sourceforge.net/dev/eclipse/index.html> are a bit out-of-date, so use the versions indicated in this email. > > > XING Chang, > > Please try running the latest versions as written above. Also, you need to be online to resolve the necessary m2e connectors. > > > Let me know how it goes! And sorry about all the issues.. > Andrius > > > On Sat, 8 Aug 2015 at 10:01 ky582 <ky...@yo... <mailto:ky...@yo...>> wrote: > Hello, > > I am using CZT with Eclipse and Maven 3.2.5 on Mac OS X (I also used Maven 3.0.4 on Ubuntu before). So Maven 3 should not be a problem. The only problem to follow "Setup CZT in Eclipse” (http://czt.sourceforge.net/dev/eclipse/index.html <http://czt.sourceforge.net/dev/eclipse/index.html>) instruction is that the update site (http://czt.sourceforge.net/dev/eclipse/updates/ <http://czt.sourceforge.net/dev/eclipse/updates/>) doesn’t work for me to install two m2e connectors. Because I have another previous setup on Ubuntu as well, my solution is to export these connectors and then install them in new environment. > > I am not sure if it is the case for XINGChang because I can not see his attached screen shot in this mail list. > > Regards, > Randall > >> On 7 Aug 2015, at 13:17, Leo Freitas <leo...@ne... <mailto:leo...@ne...>> wrote: >> >> Hi, >> >> Okay. When I had such issues it usually meant my eclipse installation was missing the plugins, but Eclipse usually managed to find them. The hint about maven 2/3 is good. >> >> @Andrius knows better about these things. Would you have something to suggest? >> >> Best, >> Leo >> >>> On 7 Aug 2015, at 02:59, XINGChang <aub...@ou... <mailto:aub...@ou...>> wrote: >>> >>> Hi, >>> >>> Thanks for you reply. My work would aim to enhance the current type-checker for OZ. My supervisor just said that the type-checker has some problems when processing recursive data structure. >>> >>> Git is not problem and I know how to use it. And I'll look at Maven some more today, Thanks for your suggestion. >>> >>> But I'd like to establish the developing environment as the first step, but when I tried to import the project, follow the tutorial from the sourceforge page, I got an error like this: >>> >>> <Screen Shot 2015-08-07 at 11.21.44 AM.png> >>> >>> Maven failed to download some plug-ins. I tried to search related information in Google but I don't get any solution about this. Someone told that maybe the project uses Maven 2 and I have Maven 3 installed, is it? >>> >>> Thank you! >>> >>> Regards. >>> >>> XING, Chang >>> >>> Zhejiang University >>> >>> >>> From: leo...@ne... <mailto:leo...@ne...> >>> To: aub...@ou... <mailto:aub...@ou...> >>> CC: czt...@li... <mailto:czt...@li...> >>> Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. >>> Date: Thu, 6 Aug 2015 15:17:36 +0000 >>> >>> Hi, >>> >>> Nice to hear about work to do within CZT and OZ. >>> >>> It is possible to use intelij but we have it all setup for Eclipse. You will need the Maven integration within InteliJ, but I don’t know how that goes. >>> >>> CZT is slightly complex but relatively well organised. You will also need to learn Git to be able to commit. I suggest you clone the repository and branch it for your use. >>> You can then have a look at typechecker-oz and parser-oz projects to see what you need to change. Which is what exactly by the way? I mean, are you extending the >>> OZ language or type type system or both? >>> >>> Learning the basics of Maven is important, but that’s not too bad. Asking questions here is also a good way forward. Try using the development environment for a small change, or look at the various examples within different projects and eventually you will get there :-) >>> >>> Good luck! >>> >>> Best, >>> Leo >>> >>> On 5 Aug 2015, at 12:16, 邢畅 <aub...@ou... <mailto:aub...@ou...>> wrote: >>> >>> Hi >>> >>> Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ and doing a project about Object-Z now. My supervisor is professor Graeme Paul Smith, and the thesis aims to enhance the type-checker used by CZT project. So can I join the Mailing list and post questions here? I think it's may be a hard task. >>> >>> I'm not that familiar with CZT and have no idea about the IDEs. I tried to clone the project and import the Maven project into IntelliJ IDEA but failed. I can't make IDEA resolve the complex dependencies so I changed to use Eclipse and follow the instruction from the page(http://czt.sourceforge.net/dev/eclipse/index.html <http://czt.sourceforge.net/dev/eclipse/index.html>). >>> >>> But I encountered a question again, I failed to import the project because it lacks some plugin, as shown in the image attached. >>> >>> Sorry, I'm not familiar with Maven and Eclipse, I only know some language knowledge about Java without any additional knowledge about it's ecosystem...If the question is too obvious or stupid, could you please what kind of things should I learn first? >>> >>> Thank you all. >>> >>> Regards. >>> >>> XING, Chang >>> >>> Zhejiang University >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> CZT-Devel mailing list >>> CZT...@li... <mailto:CZT...@li...> >>> https://lists.sourceforge.net/lists/listinfo/czt-devel <https://lists.sourceforge.net/lists/listinfo/czt-devel> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> CZT-Devel mailing list >> CZT...@li... <mailto:CZT...@li...> >> https://lists.sourceforge.net/lists/listinfo/czt-devel <https://lists.sourceforge.net/lists/listinfo/czt-devel> > |
|
From: Chang X. <aub...@ou...> - 2015-08-10 04:31:47
|
Thank you Andrius, I've already resolved this problem, the project is able to be imported. Regards.XING, ChangZhejiang University From: and...@ne... Date: Sun, 9 Aug 2015 22:44:28 +0000 Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. To: aub...@ou...; bm....@gm... CC: czt...@li... Hi XING Chang, The version of M2E connector for XML Transform plugin you are using is too old. Please add http://czt.sourceforge.net/dev/eclipse/updates/ again as an update site and install version 3.0.0 of M2E connector for XML Transform. It works with Eclipse Mars and newest M2E. I have updated the update site yesterday, as it was pointing to old connector versions previously.. Andrius On Sun, 9 Aug 2015 at 23:38 Chang XING <aub...@ou...> wrote: Hi Mark, Thanks for your suggestion. I tried several times again and seems found the problem. First, I reinstalled the M2Eclipse Plugin to the latest version(1.6), and installed maven-jflex-plugin(1.2). Second, I import the whole czt-code project, and installed all the plug-ins required. Eclipse found those plug-ins successfully this time! But the only xml-maven-plugin cannot be found this time. So after I've imported the project, I tried to install the XML transformer from the eclipse 'install new software' menu, then I got this error: The error message is: Cannot complete the install because of a conflicting dependency. Software being installed: m2e Connector for XML Transform 1.0.0 (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) Software currently installed: m2e - Maven Integration for Eclipse (includes Incubating components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338) Only one of the following can be installed at once: Maven Integration for Eclipse JDT 1.4.0.20130601-0317 (org.eclipse.m2e.jdt 1.4.0.20130601-0317) Maven Integration for Eclipse JDT 1.5.0.20140606-0033 (org.eclipse.m2e.jdt 1.5.0.20140606-0033) Maven Integration for Eclipse JDT 1.5.1.20150109-1820 (org.eclipse.m2e.jdt 1.5.1.20150109-1820) Maven Integration for Eclipse JDT 1.4.1.20140328-1905 (org.eclipse.m2e.jdt 1.4.1.20140328-1905) Maven Integration for Eclipse JDT 1.6.0.20150526-2032 (org.eclipse.m2e.jdt 1.6.0.20150526-2032) Maven Integration for Eclipse JDT 1.5.2.20150413-2215 (org.eclipse.m2e.jdt 1.5.2.20150413-2215) Maven Integration for Eclipse JDT 1.6.1.20150625-2338 (org.eclipse.m2e.jdt 1.6.1.20150625-2338) Cannot satisfy dependency: From: m2e connector for XML Plugin 1.0.0 (nl.mwensveen.m2e.extras.xml.transform 1.0.0) To: bundle org.eclipse.m2e.jdt [1.0.0,1.5.0) Cannot satisfy dependency: From: m2e Connector for XML Transform 1.0.0 (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) To: nl.mwensveen.m2e.extras.xml.transform [1.0.0] Cannot satisfy dependency: From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338) To: org.eclipse.m2e.jdt [1.6.1.20150625-2338] Seems that XML Transformer is conflict with the latest M2E plug-ins and only accept M2E under 1.5.0? But I cannot downgrade M2E because it's built-in by Eclipse Mars(4.5). So I reinstalled Eclipse with built-in M2E(1.6) and try to install the XML Transformer again, it success. If I want to upgrade M2E, the following errors appear: Your original request has been modified. "m2e - slf4j over logback logging (Optional)" is already installed, so an update will be performed instead. "m2e - Maven Integration for Eclipse (includes Incubating components)" is already installed, so an update will be performed instead. Cannot complete the install because of a conflicting dependency. Software being installed: m2e - Maven Integration for Eclipse (includes Incubating components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338) Software currently installed: m2e Connector for XML Transform 1.0.0 (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) Only one of the following can be installed at once: Maven Integration for Eclipse JDT 1.4.0.20130601-0317 (org.eclipse.m2e.jdt 1.4.0.20130601-0317) Maven Integration for Eclipse JDT 1.5.0.20140606-0033 (org.eclipse.m2e.jdt 1.5.0.20140606-0033) Maven Integration for Eclipse JDT 1.5.1.20150109-1820 (org.eclipse.m2e.jdt 1.5.1.20150109-1820) Maven Integration for Eclipse JDT 1.4.1.20140328-1905 (org.eclipse.m2e.jdt 1.4.1.20140328-1905) Maven Integration for Eclipse JDT 1.6.0.20150526-2032 (org.eclipse.m2e.jdt 1.6.0.20150526-2032) Maven Integration for Eclipse JDT 1.5.2.20150413-2215 (org.eclipse.m2e.jdt 1.5.2.20150413-2215) Maven Integration for Eclipse JDT 1.6.1.20150625-2338 (org.eclipse.m2e.jdt 1.6.1.20150625-2338) Cannot satisfy dependency: From: m2e connector for XML Plugin 1.0.0 (nl.mwensveen.m2e.extras.xml.transform 1.0.0) To: bundle org.eclipse.m2e.jdt [1.0.0,1.5.0) Cannot satisfy dependency: From: m2e Connector for XML Transform 1.0.0 (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) To: nl.mwensveen.m2e.extras.xml.transform [1.0.0] Cannot satisfy dependency: From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338) To: org.eclipse.m2e.jdt [1.6.1.20150625-2338] But once I upgraded to the latest version, Eclipse works almost correct: Except the xml-maven-plugin... The the conclusion is, only the latest M2E can install all the plug-ins except the XML Transformer. So, please, does anyone knows how to handle this situation? --- Hi, ky582, Thanks for your reply, I forget the screenshot at the first email, the error looks like this: And I think it's maybe a good option, I use OS X too, with Maven 3.3.3 and Eclipse 4.5, maybe anyone who has the same configuration can export the project and send to me then I can import it without errors. Thank you again~ Regards. XING, Chang Zhejiang University Date: Sat, 8 Aug 2015 15:32:31 +1000 Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. From: bm....@gm... To: leo...@ne... CC: aub...@ou...; czt...@li... Chang, I'm currently using Maven 3.2.2, and had no trouble building CZT yesterday. But it is quite common for Maven to have trouble downloading something - perhaps due to internet timeouts. I find it is sometimes worth trying again a couple of times, and if necessary try at another time of the day. Good luck! Mark On 7 August 2015 at 22:17, Leo Freitas <leo...@ne...> wrote: Hi, Okay. When I had such issues it usually meant my eclipse installation was missing the plugins, but Eclipse usually managed to find them. The hint about maven 2/3 is good. @Andrius knows better about these things. Would you have something to suggest? Best, Leo On 7 Aug 2015, at 02:59, XINGChang <aub...@ou...> wrote: Hi, Thanks for you reply. My work would aim to enhance the current type-checker for OZ. My supervisor just said that the type-checker has some problems when processing recursive data structure. Git is not problem and I know how to use it. And I'll look at Maven some more today, Thanks for your suggestion. But I'd like to establish the developing environment as the first step, but when I tried to import the project, follow the tutorial from the sourceforge page, I got an error like this: <Screen Shot 2015-08-07 at 11.21.44 AM.png> Maven failed to download some plug-ins. I tried to search related information in Google but I don't get any solution about this. Someone told that maybe the project uses Maven 2 and I have Maven 3 installed, is it? Thank you! Regards. XING, Chang Zhejiang University From: leo...@ne... To: aub...@ou... CC: czt...@li... Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. Date: Thu, 6 Aug 2015 15:17:36 +0000 Hi, Nice to hear about work to do within CZT and OZ. It is possible to use intelij but we have it all setup for Eclipse. You will need the Maven integration within InteliJ, but I don’t know how that goes. CZT is slightly complex but relatively well organised. You will also need to learn Git to be able to commit. I suggest you clone the repository and branch it for your use. You can then have a look at typechecker-oz and parser-oz projects to see what you need to change. Which is what exactly by the way? I mean, are you extending the OZ language or type type system or both? Learning the basics of Maven is important, but that’s not too bad. Asking questions here is also a good way forward. Try using the development environment for a small change, or look at the various examples within different projects and eventually you will get there :-) Good luck! Best, Leo On 5 Aug 2015, at 12:16, 邢畅 <aub...@ou...> wrote: Hi Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ and doing a project about Object-Z now. My supervisor is professor Graeme Paul Smith, and the thesis aims to enhance the type-checker used by CZT project. So can I join the Mailing list and post questions here? I think it's may be a hard task. I'm not that familiar with CZT and have no idea about the IDEs. I tried to clone the project and import the Maven project into IntelliJ IDEA but failed. I can't make IDEA resolve the complex dependencies so I changed to use Eclipse and follow the instruction from the page(http://czt.sourceforge.net/dev/eclipse/index.html). But I encountered a question again, I failed to import the project because it lacks some plugin, as shown in the image attached. Sorry, I'm not familiar with Maven and Eclipse, I only know some language knowledge about Java without any additional knowledge about it's ecosystem...If the question is too obvious or stupid, could you please what kind of things should I learn first? Thank you all. Regards. XING, Chang Zhejiang University ------------------------------------------------------------------------------ _______________________________________________ CZT-Devel mailing list CZT...@li... https://lists.sourceforge.net/lists/listinfo/czt-devel ------------------------------------------------------------------------------ _______________________________________________ CZT-Devel mailing list CZT...@li... https://lists.sourceforge.net/lists/listinfo/czt-devel |
|
From: Andrius V. <and...@ne...> - 2015-08-09 22:44:48
|
Hi XING Chang, The version of M2E connector for XML Transform plugin you are using is too old. Please add http://czt.sourceforge.net/dev/eclipse/updates/ again as an update site and install version 3.0.0 of M2E connector for XML Transform. It works with Eclipse Mars and newest M2E. I have updated the update site yesterday, as it was pointing to old connector versions previously.. Andrius On Sun, 9 Aug 2015 at 23:38 Chang XING <aub...@ou...> wrote: > Hi Mark, > > Thanks for your suggestion. > > I tried several times again and seems found the problem. > > First, I reinstalled the M2Eclipse Plugin to the latest version(1.6), and > installed maven-jflex-plugin(1.2). > > Second, I import the whole czt-code project, and installed all the > plug-ins required. Eclipse found those plug-ins successfully this time! But > the only xml-maven-plugin cannot be found this time. > > So after I've imported the project, I tried to install the XML transformer > from the eclipse 'install new software' menu, then I got this error: > > > > > > The error message is: > > > Cannot complete the install because of a conflicting dependency. > Software being installed: m2e Connector for XML Transform 1.0.0 > (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) > Software currently installed: m2e - Maven Integration for Eclipse > (includes Incubating components) 1.6.1.20150625-2338 > (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338) > Only one of the following can be installed at once: > Maven Integration for Eclipse JDT 1.4.0.20130601-0317 > (org.eclipse.m2e.jdt 1.4.0.20130601-0317) > Maven Integration for Eclipse JDT 1.5.0.20140606-0033 > (org.eclipse.m2e.jdt 1.5.0.20140606-0033) > Maven Integration for Eclipse JDT 1.5.1.20150109-1820 > (org.eclipse.m2e.jdt 1.5.1.20150109-1820) > Maven Integration for Eclipse JDT 1.4.1.20140328-1905 > (org.eclipse.m2e.jdt 1.4.1.20140328-1905) > Maven Integration for Eclipse JDT 1.6.0.20150526-2032 > (org.eclipse.m2e.jdt 1.6.0.20150526-2032) > Maven Integration for Eclipse JDT 1.5.2.20150413-2215 > (org.eclipse.m2e.jdt 1.5.2.20150413-2215) > Maven Integration for Eclipse JDT 1.6.1.20150625-2338 > (org.eclipse.m2e.jdt 1.6.1.20150625-2338) > Cannot satisfy dependency: > From: m2e connector for XML Plugin 1.0.0 > (nl.mwensveen.m2e.extras.xml.transform 1.0.0) > To: bundle org.eclipse.m2e.jdt [1.0.0,1.5.0) > Cannot satisfy dependency: > From: m2e Connector for XML Transform 1.0.0 > (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) > To: nl.mwensveen.m2e.extras.xml.transform [1.0.0] > Cannot satisfy dependency: > From: m2e - Maven Integration for Eclipse (includes Incubating > components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group > 1.6.1.20150625-2338) > To: org.eclipse.m2e.jdt [1.6.1.20150625-2338] > > > > Seems that XML Transformer is conflict with the latest M2E plug-ins and > only accept M2E under 1.5.0? > > But I cannot downgrade M2E because it's built-in by Eclipse Mars(4.5). So > I reinstalled Eclipse with built-in M2E(1.6) and try to install the XML > Transformer again, it success. If I want to upgrade M2E, the following > errors appear: > > > Your original request has been modified. > "m2e - slf4j over logback logging (Optional)" is already installed, so > an update will be performed instead. > "m2e - Maven Integration for Eclipse (includes Incubating components)" > is already installed, so an update will be performed instead. > Cannot complete the install because of a conflicting dependency. > Software being installed: m2e - Maven Integration for Eclipse (includes > Incubating components) 1.6.1.20150625-2338 > (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338) > Software currently installed: m2e Connector for XML Transform 1.0.0 > (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) > Only one of the following can be installed at once: > Maven Integration for Eclipse JDT 1.4.0.20130601-0317 > (org.eclipse.m2e.jdt 1.4.0.20130601-0317) > Maven Integration for Eclipse JDT 1.5.0.20140606-0033 > (org.eclipse.m2e.jdt 1.5.0.20140606-0033) > Maven Integration for Eclipse JDT 1.5.1.20150109-1820 > (org.eclipse.m2e.jdt 1.5.1.20150109-1820) > Maven Integration for Eclipse JDT 1.4.1.20140328-1905 > (org.eclipse.m2e.jdt 1.4.1.20140328-1905) > Maven Integration for Eclipse JDT 1.6.0.20150526-2032 > (org.eclipse.m2e.jdt 1.6.0.20150526-2032) > Maven Integration for Eclipse JDT 1.5.2.20150413-2215 > (org.eclipse.m2e.jdt 1.5.2.20150413-2215) > Maven Integration for Eclipse JDT 1.6.1.20150625-2338 > (org.eclipse.m2e.jdt 1.6.1.20150625-2338) > Cannot satisfy dependency: > From: m2e connector for XML Plugin 1.0.0 > (nl.mwensveen.m2e.extras.xml.transform 1.0.0) > To: bundle org.eclipse.m2e.jdt [1.0.0,1.5.0) > Cannot satisfy dependency: > From: m2e Connector for XML Transform 1.0.0 > (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) > To: nl.mwensveen.m2e.extras.xml.transform [1.0.0] > Cannot satisfy dependency: > From: m2e - Maven Integration for Eclipse (includes Incubating > components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group > 1.6.1.20150625-2338) > To: org.eclipse.m2e.jdt [1.6.1.20150625-2338] > > > But once I upgraded to the latest version, Eclipse works almost correct: > > > > > > Except the xml-maven-plugin... > > The the conclusion is, only the latest M2E can install all the plug-ins > except the XML Transformer. > > So, please, does anyone knows how to handle this situation? > > --- > > Hi, ky582, > > Thanks for your reply, I forget the screenshot at the first email, the > error looks like this: > > > > > > And I think it's maybe a good option, I use OS X too, with Maven 3.3.3 and > Eclipse 4.5, maybe anyone who has the same configuration can export the > project and send to me then I can import it without errors. > > Thank you again~ > > Regards. > > XING, Chang > > Zhejiang University > > > ------------------------------ > Date: Sat, 8 Aug 2015 15:32:31 +1000 > > Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. > From: bm....@gm... > To: leo...@ne... > CC: aub...@ou...; czt...@li... > > > Chang, > > I'm currently using Maven 3.2.2, and had no trouble building CZT > yesterday. But it is quite common for Maven to have trouble downloading > something - perhaps due to internet timeouts. I find it is sometimes worth > trying again a couple of times, and if necessary try at another time of the > day. > > Good luck! > Mark > > > On 7 August 2015 at 22:17, Leo Freitas <leo...@ne...> > wrote: > > Hi, > > Okay. When I had such issues it usually meant my eclipse installation was > missing the plugins, but Eclipse usually managed to find them. The hint > about maven 2/3 is good. > > @Andrius knows better about these things. Would you have something to > suggest? > > Best, > Leo > > On 7 Aug 2015, at 02:59, XINGChang <aub...@ou...> wrote: > > Hi, > > Thanks for you reply. My work would aim to enhance the current > type-checker for OZ. My supervisor just said that the type-checker has some > problems when processing recursive data structure. > > Git is not problem and I know how to use it. And I'll look at Maven some > more today, Thanks for your suggestion. > > But I'd like to establish the developing environment as the first step, > but when I tried to import the project, follow the tutorial from the > sourceforge page, I got an error like this: > > > <Screen Shot 2015-08-07 at 11.21.44 AM.png> > > > Maven failed to download some plug-ins. I tried to search related > information in Google but I don't get any solution about this. Someone told > that maybe the project uses Maven 2 and I have Maven 3 installed, is it? > > Thank you! > > Regards. > > XING, Chang > > Zhejiang University > > > ------------------------------ > From: leo...@ne... > To: aub...@ou... > CC: czt...@li... > Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. > Date: Thu, 6 Aug 2015 15:17:36 +0000 > > > Hi, > > Nice to hear about work to do within CZT and OZ. > > It is possible to use intelij but we have it all setup for Eclipse. You > will need the Maven integration within InteliJ, but I don’t know how that > goes. > > CZT is slightly complex but relatively well organised. You will also need > to learn Git to be able to commit. I suggest you clone the repository and > branch it for your use. > You can then have a look at typechecker-oz and parser-oz projects to see > what you need to change. Which is what exactly by the way? I mean, are you > extending the > OZ language or type type system or both? > > Learning the basics of Maven is important, but that’s not too bad. Asking > questions here is also a good way forward. Try using the development > environment for a small change, or look at the various examples within > different projects and eventually you will get there :-) > > Good luck! > > Best, > Leo > > > On 5 Aug 2015, at 12:16, 邢畅 <aub...@ou...> wrote: > > Hi > > Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ > and doing a project about Object-Z now. My supervisor is professor Graeme > Paul Smith, and the thesis aims to enhance the type-checker used by CZT > project. So can I join the Mailing list and post questions here? I think > it's may be a hard task. > > I'm not that familiar with CZT and have no idea about the IDEs. I tried to > clone the project and import the Maven project into IntelliJ IDEA but > failed. I can't make IDEA resolve the complex dependencies so I changed to > use Eclipse and follow the instruction from the page( > http://czt.sourceforge.net/dev/eclipse/index.html). > > But I encountered a question again, I failed to import the project because > it lacks some plugin, as shown in the image attached. > > Sorry, I'm not familiar with Maven and Eclipse, I only know some language > knowledge about Java without any additional knowledge about it's > ecosystem...If the question is too obvious or stupid, could you please what > kind of things should I learn first? > > Thank you all. > > Regards. > > XING, Chang > > Zhejiang University > > ------------------------------------------------------------------------------ > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > > > |
|
From: Andrius V. <and...@ne...> - 2015-08-08 11:35:05
|
Hi - yea, these are the errors I have mentioned. They only appear in Eclipse and I haven't figured out what is causing them yet, sorry. If you are not using UI, feel free to delete all the .eclipse.* projects from your workspace (but don't delete them on disk). Andrius On Sat, 8 Aug 2015 at 12:30 Chang XING <aub...@ou...> wrote: > Hi Andrius, > > Thank you, that really helps, I can import the project without error now. > > But there are still some errors when building in projects 'net.sourceforge.czt.eclipse.ui', > 'net.sourceforge.czt.eclipse.vcg.ui' and 'net.sourceforge.czt.eclipse.zeves.ui'. > The errors says that 'Access restriction' because some functions are not > API. > > All 8 hundred errors' description is attached. > > Sorry I'm not familiar with the Java build system. Is it because the build > path doesn't contain some certain packages? If I don't need UI, can I > simply deleted all the packages related? > > Thanks. > > Regards. > > XING, Chang > > Zhejiang University > > > ------------------------------ > From: and...@ne... > Date: Sat, 8 Aug 2015 09:59:22 +0000 > Subject: CZT build issues in Eclipse > To: ky...@yo...; aub...@ou... > CC: czt...@li...; leo...@ne... > > > Hi Randall and XING Chang, > > Sorry about the build problems - they are still being solved so please > report what you find. Also SourceForge was not working for the last couple > weeks so I could not update what is needed. > > I have just updated the update site at > http://czt.sourceforge.net/dev/eclipse/updates/ - a bit of manual job, > but now it should point to the correct m2e connector update sites (they > have changed locations since the last CZT updates). > > Also, could you try using Eclipse Mars with Java 8, Maven 3.3.3 and the > version of m2e that comes with Mars? I have tried fixing so it works with > the recent versions but have not tested with older ones. > > With this configuration (Java 8, Maven 3.3.3, Eclipse Mars), the import of > CZT works. There may be a bit of issues with dependency resolution in > net.sourceforge.czt.eclipse.ui (known issue) but I have not found a way to > resolve it yet or what causes the problem. > > Also, the instructions in http://czt.sourceforge.net/dev/eclipse/ > <http://czt.sourceforge.net/dev/eclipse/index.html> are a bit > out-of-date, so use the versions indicated in this email. > > > XING Chang, > > Please try running the latest versions as written above. Also, you need to > be online to resolve the necessary m2e connectors. > > > Let me know how it goes! And sorry about all the issues.. > Andrius > > > On Sat, 8 Aug 2015 at 10:01 ky582 <ky...@yo...> wrote: > > Hello, > > I am using CZT with Eclipse and Maven 3.2.5 on Mac OS X (I also used Maven > 3.0.4 on Ubuntu before). So Maven 3 should not be a problem. The only > problem to follow "Setup CZT in Eclipse” ( > http://czt.sourceforge.net/dev/eclipse/index.html) instruction is that > the update site (http://czt.sourceforge.net/dev/eclipse/updates/) doesn’t > work for me to install two m2e connectors. Because I have another previous > setup on Ubuntu as well, my solution is to export these connectors and then > install them in new environment. > > I am not sure if it is the case for XINGChang because I can not see his > attached screen shot in this mail list. > > Regards, > Randall > > On 7 Aug 2015, at 13:17, Leo Freitas <leo...@ne...> wrote: > > Hi, > > Okay. When I had such issues it usually meant my eclipse installation was > missing the plugins, but Eclipse usually managed to find them. The hint > about maven 2/3 is good. > > @Andrius knows better about these things. Would you have something to > suggest? > > Best, > Leo > > On 7 Aug 2015, at 02:59, XINGChang <aub...@ou...> wrote: > > Hi, > > Thanks for you reply. My work would aim to enhance the current > type-checker for OZ. My supervisor just said that the type-checker has some > problems when processing recursive data structure. > > Git is not problem and I know how to use it. And I'll look at Maven some > more today, Thanks for your suggestion. > > But I'd like to establish the developing environment as the first step, > but when I tried to import the project, follow the tutorial from the > sourceforge page, I got an error like this: > > > <Screen Shot 2015-08-07 at 11.21.44 AM.png> > > > Maven failed to download some plug-ins. I tried to search related > information in Google but I don't get any solution about this. Someone told > that maybe the project uses Maven 2 and I have Maven 3 installed, is it? > > Thank you! > > Regards. > > XING, Chang > > Zhejiang University > > > ------------------------------ > From: leo...@ne... > To: aub...@ou... > CC: czt...@li... > Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. > Date: Thu, 6 Aug 2015 15:17:36 +0000 > > Hi, > > Nice to hear about work to do within CZT and OZ. > > It is possible to use intelij but we have it all setup for Eclipse. You > will need the Maven integration within InteliJ, but I don’t know how that > goes. > > CZT is slightly complex but relatively well organised. You will also need > to learn Git to be able to commit. I suggest you clone the repository and > branch it for your use. > You can then have a look at typechecker-oz and parser-oz projects to see > what you need to change. Which is what exactly by the way? I mean, are you > extending the > OZ language or type type system or both? > > Learning the basics of Maven is important, but that’s not too bad. Asking > questions here is also a good way forward. Try using the development > environment for a small change, or look at the various examples within > different projects and eventually you will get there :-) > > Good luck! > > Best, > Leo > > > On 5 Aug 2015, at 12:16, 邢畅 <aub...@ou...> wrote: > > Hi > > Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ > and doing a project about Object-Z now. My supervisor is professor Graeme > Paul Smith, and the thesis aims to enhance the type-checker used by CZT > project. So can I join the Mailing list and post questions here? I think > it's may be a hard task. > > I'm not that familiar with CZT and have no idea about the IDEs. I tried to > clone the project and import the Maven project into IntelliJ IDEA but > failed. I can't make IDEA resolve the complex dependencies so I changed to > use Eclipse and follow the instruction from the page( > http://czt.sourceforge.net/dev/eclipse/index.html). > > But I encountered a question again, I failed to import the project because > it lacks some plugin, as shown in the image attached. > > Sorry, I'm not familiar with Maven and Eclipse, I only know some language > knowledge about Java without any additional knowledge about it's > ecosystem...If the question is too obvious or stupid, could you please what > kind of things should I learn first? > > Thank you all. > > Regards. > > XING, Chang > > Zhejiang University > > ------------------------------------------------------------------------------ > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > > > > ------------------------------------------------------------------------------ > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > > > |
|
From: Chang X. <aub...@ou...> - 2015-08-08 11:30:41
|
Description Resource Path Location Type Access restriction: The constructor 'CztErrorImpl(SectionInfo, String, Object[], LocInfo)' is not API (restriction on required project 'parser-z') ZEditorModel.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/zeditor line 209 Java Problem Access restriction: The constructor 'LocInfoImpl(Dialect, String, int, int)' is not API (restriction on required project 'parser-z') ZEditorModel.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/zeditor line 210 Java Problem Access restriction: The constructor 'PrintVisitor()' is not API (restriction on required project 'corejava-z') NameInfo.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 22 Java Problem Access restriction: The constructor 'PrintVisitor()' is not API (restriction on required project 'corejava-z') NameInfoResolver.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 41 Java Problem Access restriction: The constructor 'PrintVisitor()' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 52 Java Problem Access restriction: The field 'Box.AxBox' is not API (restriction on required project 'corejava-z') NodeChildrenVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 102 Java Problem Access restriction: The field 'Box.AxBox' is not API (restriction on required project 'corejava-z') NodeIconVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 91 Java Problem Access restriction: The field 'Box.OmitBox' is not API (restriction on required project 'corejava-z') NodeIconVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 93 Java Problem Access restriction: The field 'Box.SchBox' is not API (restriction on required project 'corejava-z') NodeIconVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 95 Java Problem Access restriction: The field 'ErrorType.ERROR' is not API (restriction on required project 'parser-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 349 Java Problem Access restriction: The field 'ErrorType.ERROR' is not API (restriction on required project 'parser-z') ZCompilerMessageParser.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 96 Java Problem Access restriction: The field 'ErrorType.ERROR' is not API (restriction on required project 'parser-z') ZEditorUtil.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 82 Java Problem Access restriction: The field 'ErrorType.WARNING' is not API (restriction on required project 'parser-z') ZCompilerMessageParser.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 89 Java Problem Access restriction: The field 'ErrorType.WARNING' is not API (restriction on required project 'parser-z') ZCompilerMessageParser.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 100 Java Problem Access restriction: The field 'ErrorType.WARNING' is not API (restriction on required project 'parser-z') ZCompilerMessageParser.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 144 Java Problem Access restriction: The field 'ParsePropertiesKeys.PROP_IGNORE_UNKNOWN_LATEX_COMMANDS_DEFAULT' is not API (restriction on required project 'parser-z') PreferenceConstants.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/preferences line 96 Java Problem Access restriction: The field 'ParsePropertiesKeys.PROP_IGNORE_UNKNOWN_LATEX_COMMANDS' is not API (restriction on required project 'parser-z') PreferenceConstants.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/preferences line 48 Java Problem Access restriction: The field 'TypecheckPropertiesKeys.PROP_TYPECHECK_RECURSIVE_TYPES_DEFAULT' is not API (restriction on required project 'typechecker-z') PreferenceConstants.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/preferences line 99 Java Problem Access restriction: The field 'TypecheckPropertiesKeys.PROP_TYPECHECK_RECURSIVE_TYPES' is not API (restriction on required project 'typechecker-z') PreferenceConstants.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/preferences line 60 Java Problem Access restriction: The field 'ZString.AX' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 219 Java Problem Access restriction: The field 'ZString.END' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 202 Java Problem Access restriction: The field 'ZString.END' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 226 Java Problem Access restriction: The field 'ZString.END' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 250 Java Problem Access restriction: The field 'ZString.END' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 273 Java Problem Access restriction: The field 'ZString.END' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 296 Java Problem Access restriction: The field 'ZString.END' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 327 Java Problem Access restriction: The field 'ZString.GENAX' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 266 Java Problem Access restriction: The field 'ZString.GENSCH' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 289 Java Problem Access restriction: The field 'ZString.IMP' is not API (restriction on required project 'corejava-z') ZUnicodeCodeScanner.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/unicode line 54 Java Problem Access restriction: The field 'ZString.LAMBDA' is not API (restriction on required project 'corejava-z') ZUnicodeCodeScanner.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/unicode line 42 Java Problem Access restriction: The field 'ZString.LANGLE' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 129 Java Problem Access restriction: The field 'ZString.LBIND' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 99 Java Problem Access restriction: The field 'ZString.LBRACE' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 89 Java Problem Access restriction: The field 'ZString.LDATA' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 109 Java Problem Access restriction: The field 'ZString.LIMG' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 119 Java Problem Access restriction: The field 'ZString.LPAREN' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 69 Java Problem Access restriction: The field 'ZString.LSQUARE' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 79 Java Problem Access restriction: The field 'ZString.PRIME' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 147 Java Problem Access restriction: The field 'ZString.RANGLE' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 134 Java Problem Access restriction: The field 'ZString.RBIND' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 104 Java Problem Access restriction: The field 'ZString.RBRACE' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 94 Java Problem Access restriction: The field 'ZString.RDATA' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 114 Java Problem Access restriction: The field 'ZString.RIMG' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 124 Java Problem Access restriction: The field 'ZString.RPAREN' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 74 Java Problem Access restriction: The field 'ZString.RSQUARE' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 84 Java Problem Access restriction: The field 'ZString.SCH' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 243 Java Problem Access restriction: The field 'ZString.VL' is not API (restriction on required project 'corejava-z') ZSpecDecorationSupport.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 207 Java Problem Access restriction: The field 'ZString.VL' is not API (restriction on required project 'corejava-z') ZSpecDecorationSupport.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 375 Java Problem Access restriction: The field 'ZString.ZED' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 195 Java Problem Access restriction: The method 'AxPara.getBox()' is not API (restriction on required project 'corejava-z') NodeChildrenVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 100 Java Problem Access restriction: The method 'AxPara.getBox()' is not API (restriction on required project 'corejava-z') NodeIconVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 90 Java Problem Access restriction: The method 'AxPara.getZSchText()' is not API (restriction on required project 'corejava-z') CztTreeNodeFactory.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 169 Java Problem Access restriction: The method 'AxPara.getZSchText()' is not API (restriction on required project 'corejava-z') NodeChildrenVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 103 Java Problem Access restriction: The method 'AxPara.getZSchText()' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 140 Java Problem Access restriction: The method 'AxParaVisitor.visitAxPara(AxPara)' is not API (restriction on required project 'corejava-z') NodeIconVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 86 Java Problem Access restriction: The method 'AxParaVisitor.visitAxPara(AxPara)' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 135 Java Problem Access restriction: The method 'ConjPara.getZNameList()' is not API (restriction on required project 'corejava-z') CztTreeNodeFactory.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 217 Java Problem Access restriction: The method 'ConjPara.getZNameList()' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 150 Java Problem Access restriction: The method 'ConjParaVisitor.visitConjPara(ConjPara)' is not API (restriction on required project 'corejava-z') NodeIconVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 101 Java Problem Access restriction: The method 'ConjParaVisitor.visitConjPara(ConjPara)' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 145 Java Problem Access restriction: The method 'ConstDecl.getExpr()' is not API (restriction on required project 'corejava-z') NameInfoResolver.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 229 Java Problem Access restriction: The method 'ConstDecl.getZName()' is not API (restriction on required project 'corejava-z') CztTreeNodeFactory.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 176 Java Problem Access restriction: The method 'ConstDecl.getZName()' is not API (restriction on required project 'corejava-z') CztTreeNodeFactory.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 236 Java Problem Access restriction: The method 'ConstDecl.getZName()' is not API (restriction on required project 'corejava-z') NameInfoResolver.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 233 Java Problem Access restriction: The method 'CztError.getErrorType()' is not API (restriction on required project 'parser-z') ZCompilerMessageParser.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 88 Java Problem Access restriction: The method 'CztError.getErrorType()' is not API (restriction on required project 'parser-z') ZEditorUtil.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 82 Java Problem Access restriction: The method 'CztError.getMessage()' is not API (restriction on required project 'parser-z') ZCompilerMessageParser.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 113 Java Problem Access restriction: The method 'CztErrorImpl.getErrorType()' is not API (restriction on required project 'parser-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 349 Java Problem Access restriction: The method 'CztErrorImpl.getMessageKey()' is not API (restriction on required project 'parser-z') ZEditorModel.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/zeditor line 216 Java Problem Access restriction: The method 'CztErrorList.getErrors()' is not API (restriction on required project 'parser-z') ZCompiler.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 161 Java Problem Access restriction: The method 'CztPrintString.toString()' is not API (restriction on required project 'parser-z') Convert2LatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 50 Java Problem Access restriction: The method 'CztPrintString.toString()' is not API (restriction on required project 'parser-z') Convert2OldLatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 50 Java Problem Access restriction: The method 'CztPrintString.toString()' is not API (restriction on required project 'parser-z') Convert2UnicodeAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 50 Java Problem Access restriction: The method 'CztPrintString.toString()' is not API (restriction on required project 'parser-z') Convert2XMLAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 50 Java Problem Access restriction: The method 'ErrorAnn.getMessage()' is not API (restriction on required project 'typechecker-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 351 Java Problem Access restriction: The method 'ErrorAnn.getMessage()' is not API (restriction on required project 'typechecker-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 355 Java Problem Access restriction: The method 'FreePara.getFreetypeList()' is not API (restriction on required project 'corejava-z') CztTreeNodeFactory.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 193 Java Problem Access restriction: The method 'FreePara.getFreetypeList()' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 161 Java Problem Access restriction: The method 'FreeParaVisitor.visitFreePara(FreePara)' is not API (restriction on required project 'corejava-z') NodeIconVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 109 Java Problem Access restriction: The method 'FreeParaVisitor.visitFreePara(FreePara)' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 156 Java Problem Access restriction: The method 'Freetype.getZName()' is not API (restriction on required project 'corejava-z') CztTreeNodeFactory.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 196 Java Problem Access restriction: The method 'GenericType.getType()' is not API (restriction on required project 'corejava-z') NameInfoResolver.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 180 Java Problem Access restriction: The method 'GenericType.getZNameList()' is not API (restriction on required project 'corejava-z') NameInfoResolver.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 184 Java Problem Access restriction: The method 'GivenPara.getNames()' is not API (restriction on required project 'corejava-z') CztTreeNodeFactory.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 162 Java Problem Access restriction: The method 'GivenPara.getNames()' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 130 Java Problem Access restriction: The method 'GivenParaVisitor.visitGivenPara(GivenPara)' is not API (restriction on required project 'corejava-z') NodeDescriptionVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 133 Java Problem Access restriction: The method 'GivenParaVisitor.visitGivenPara(GivenPara)' is not API (restriction on required project 'corejava-z') NodeIconVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 78 Java Problem Access restriction: The method 'GivenParaVisitor.visitGivenPara(GivenPara)' is not API (restriction on required project 'corejava-z') NodeNameVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/outline line 198 Java Problem Access restriction: The method 'GivenParaVisitor.visitGivenPara(GivenPara)' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 125 Java Problem Access restriction: The method 'LocAnn.getLength()' is not API (restriction on required project 'corejava-z') Selector.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/util line 103 Java Problem Access restriction: The method 'LocAnn.getLength()' is not API (restriction on required project 'corejava-z') ZTextHover.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 138 Java Problem Access restriction: The method 'LocAnn.getStart()' is not API (restriction on required project 'corejava-z') Selector.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/util line 102 Java Problem Access restriction: The method 'LocAnn.getStart()' is not API (restriction on required project 'corejava-z') ZTextHover.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 137 Java Problem Access restriction: The method 'LocInfo.getColumn()' is not API (restriction on required project 'parser-z') ZCompilerMessageParser.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 115 Java Problem Access restriction: The method 'LocInfo.getLength()' is not API (restriction on required project 'parser-z') ZCompilerMessageParser.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 117 Java Problem Access restriction: The method 'LocInfo.getLine()' is not API (restriction on required project 'parser-z') ZCompilerMessageParser.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 114 Java Problem Access restriction: The method 'LocInfo.getStart()' is not API (restriction on required project 'parser-z') ZCompilerMessageParser.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 116 Java Problem Access restriction: The method 'NameSectTypeTriple.getSect()' is not API (restriction on required project 'corejava-z') NameInfoResolver.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 122 Java Problem Access restriction: The method 'NameSectTypeTriple.getSect()' is not API (restriction on required project 'corejava-z') NameInfoResolver.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 125 Java Problem Access restriction: The method 'NameSectTypeTriple.getType()' is not API (restriction on required project 'corejava-z') NameInfoResolver.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/parser line 118 Java Problem Access restriction: The type 'ZUtils' is not API (restriction on required project 'corejava-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 328 Java Problem Access restriction: The type 'ZUtils' is not API (restriction on required project 'corejava-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 27 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 147 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 134 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 129 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 124 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZSpecDecorationSupport.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 207 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 119 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZSpecDecorationSupport.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 375 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 114 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZSpecDecorationSupport.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 20 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 109 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 104 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 99 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 94 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 89 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 84 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 79 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 74 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 69 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') ZCharacter.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 7 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 327 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 296 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 289 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 273 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 266 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 250 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 243 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 226 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 219 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 202 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 195 Java Problem Access restriction: The type 'ZString' is not API (restriction on required project 'corejava-z') IZPartitions.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/editors line 7 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 165 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 165 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 164 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 164 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 163 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 163 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 122 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 121 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 16 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 101 Java Problem Access restriction: The type 'ZNameList' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 16 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 54 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 56 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 56 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 68 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 68 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 80 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 80 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 15 Java Problem Access restriction: The type 'XmlString' is not API (restriction on required project 'parser-z') Convert2XMLAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 49 Java Problem Access restriction: The type 'XmlString' is not API (restriction on required project 'parser-z') Convert2XMLAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'ZNameList' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 88 Java Problem Access restriction: The type 'XmlString' is not API (restriction on required project 'parser-z') Convert2XMLAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'XmlString' is not API (restriction on required project 'parser-z') Convert2XMLAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'XmlString' is not API (restriction on required project 'parser-z') Convert2XMLAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 5 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 90 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 91 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 91 Java Problem Access restriction: The type 'VarDecl' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 88 Java Problem Access restriction: The type 'VarDecl' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 87 Java Problem Access restriction: The type 'VarDecl' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 14 Java Problem Access restriction: The type 'UnicodeString' is not API (restriction on required project 'parser-z') Convert2UnicodeAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 49 Java Problem Access restriction: The type 'UnicodeString' is not API (restriction on required project 'parser-z') Convert2UnicodeAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'UnicodeString' is not API (restriction on required project 'parser-z') Convert2UnicodeAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'UnicodeString' is not API (restriction on required project 'parser-z') Convert2UnicodeAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'UnicodeString' is not API (restriction on required project 'parser-z') Convert2UnicodeAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 5 Java Problem Access restriction: The type 'TypeErrorException' is not API (restriction on required project 'typechecker-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 346 Java Problem Access restriction: The type 'TypeErrorException' is not API (restriction on required project 'typechecker-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 346 Java Problem Access restriction: The type 'TypeErrorException' is not API (restriction on required project 'typechecker-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 344 Java Problem Access restriction: The type 'TypeErrorException' is not API (restriction on required project 'typechecker-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 23 Java Problem Access restriction: The type 'Spec' is not API (restriction on required project 'corejava-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 338 Java Problem Access restriction: The type 'Spec' is not API (restriction on required project 'corejava-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 338 Java Problem Access restriction: The type 'Spec' is not API (restriction on required project 'corejava-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 26 Java Problem Access restriction: The type 'SectTypeEnvAnn' is not API (restriction on required project 'corejava-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 342 Java Problem Access restriction: The type 'SectTypeEnvAnn' is not API (restriction on required project 'corejava-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 341 Java Problem Access restriction: The type 'SectTypeEnvAnn' is not API (restriction on required project 'corejava-z') CztUIPlugin.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui line 25 Java Problem Access restriction: The type 'PrintVisitor' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 52 Java Problem Access restriction: The type 'PrintVisitor' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 52 Java Problem Access restriction: The type 'PrintVisitor' is not API (restriction on required project 'corejava-z') OccurrencesFinderJob.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors line 17 Java Problem Access restriction: The type 'OldLatexString' is not API (restriction on required project 'parser-z') Convert2OldLatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 49 Java Problem Access restriction: The type 'ZFreetypeList' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 161 Java Problem Access restriction: The type 'OldLatexString' is not API (restriction on required project 'parser-z') Convert2OldLatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'OptempParaVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 167 Java Problem Access restriction: The type 'OpTable' is not API (restriction on required project 'parser-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 15 Java Problem Access restriction: The type 'OldLatexString' is not API (restriction on required project 'parser-z') Convert2OldLatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'OldLatexString' is not API (restriction on required project 'parser-z') Convert2OldLatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'OldLatexString' is not API (restriction on required project 'parser-z') Convert2OldLatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 5 Java Problem Access restriction: The type 'Name' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 89 Java Problem Access restriction: The type 'Name' is not API (restriction on required project 'corejava-z') GoToDeclarationAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 13 Java Problem Access restriction: The type 'LatexString' is not API (restriction on required project 'parser-z') Convert2LatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 49 Java Problem Access restriction: The type 'LatexString' is not API (restriction on required project 'parser-z') Convert2LatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'LatexString' is not API (restriction on required project 'parser-z') Convert2LatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'NarrPara' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 24 Java Problem Access restriction: The type 'NarrSect' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 25 Java Problem Access restriction: The type 'Oper' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 26 Java Problem Access restriction: The type 'Operand' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 27 Java Problem Access restriction: The type 'Operator' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 28 Java Problem Access restriction: The type 'OptempPara' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 29 Java Problem Access restriction: The type 'TypeAnn' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 30 Java Problem Access restriction: The type 'UnparsedPara' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 31 Java Problem Access restriction: The type 'VarDecl' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 32 Java Problem Access restriction: The type 'ZDeclList' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 33 Java Problem Access restriction: The type 'ZFreetypeList' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 34 Java Problem Access restriction: The type 'ZName' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 35 Java Problem Access restriction: The type 'ZNameList' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 36 Java Problem Access restriction: The type 'ZSect' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 37 Java Problem Access restriction: The type 'PrintVisitor' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 38 Java Problem Access restriction: The type 'LatexString' is not API (restriction on required project 'parser-z') Convert2LatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 48 Java Problem Access restriction: The type 'LatexString' is not API (restriction on required project 'parser-z') Convert2LatexAction.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/actions line 5 Java Problem Access restriction: The type 'GivenType' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 23 Java Problem Access restriction: The type 'GivenPara' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 127 Java Problem Access restriction: The type 'GivenPara' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 125 Java Problem Access restriction: The type 'GivenPara' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 125 Java Problem Access restriction: The type 'GivenParaVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 45 Java Problem Access restriction: The type 'GivenTypeVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 46 Java Problem Access restriction: The type 'NarrParaVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 47 Java Problem Access restriction: The type 'NarrSectVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 48 Java Problem Access restriction: The type 'OperVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 49 Java Problem Access restriction: The type 'OptempParaVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 50 Java Problem Access restriction: The type 'UnparsedParaVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 51 Java Problem Access restriction: The type 'VarDeclVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 52 Java Problem Access restriction: The type 'ZDeclListVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 53 Java Problem Access restriction: The type 'ZFreetypeListVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 54 Java Problem Access restriction: The type 'ZNameListVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 55 Java Problem Access restriction: The type 'ZNameVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 56 Java Problem Access restriction: The type 'ZSectVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 57 Java Problem Access restriction: The type 'ZSectVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 67 Java Problem Access restriction: The type 'NarrSectVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 68 Java Problem Access restriction: The type 'GivenParaVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 69 Java Problem Access restriction: The type 'GivenPara' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 22 Java Problem Access restriction: The type 'FreetypeVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 44 Java Problem Access restriction: The type 'Freetype' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 21 Java Problem Access restriction: The type 'OptempParaVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 73 Java Problem Access restriction: The type 'NarrParaVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 74 Java Problem Access restriction: The type 'UnparsedParaVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 75 Java Problem Access restriction: The type 'FreeParaVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 72 Java Problem Access restriction: The type 'VarDeclVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 77 Java Problem Access restriction: The type 'ZDeclListVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 78 Java Problem Access restriction: The type 'ZNameVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 79 Java Problem Access restriction: The type 'ZNameListVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 80 Java Problem Access restriction: The type 'FreeParaVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 155 Java Problem Access restriction: The type 'OperVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 82 Java Problem Access restriction: The type 'GivenTypeVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 83 Java Problem Access restriction: The type 'ZFreetypeListVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 84 Java Problem Access restriction: The type 'FreetypeVisitor<String>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 85 Java Problem Access restriction: The type 'ZSectVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 105 Java Problem Access restriction: The type 'FreeParaVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 43 Java Problem Access restriction: The type 'ZSect' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 106 Java Problem Access restriction: The type 'ZSect' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 106 Java Problem Access restriction: The type 'ZSect' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 108 Java Problem Access restriction: The type 'FreePara' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 158 Java Problem Access restriction: The type 'NarrSectVisitor<R>' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 115 Java Problem Access restriction: The type 'FreePara' is not API (restriction on required project 'corejava-z') TermHighlightInfoVisitor.java /net.sourceforge.czt.eclipse.ui/src/net/sourceforge/czt/eclipse/ui/internal/editors/hover line 156 Java Problem Access restriction: The type 'NarrSect' is not API (restriction on required pr... [truncated message content] |
|
From: Andrius V. <and...@ne...> - 2015-08-08 09:59:43
|
Hi Randall and XING Chang, Sorry about the build problems - they are still being solved so please report what you find. Also SourceForge was not working for the last couple weeks so I could not update what is needed. I have just updated the update site at http://czt.sourceforge.net/dev/eclipse/updates/ - a bit of manual job, but now it should point to the correct m2e connector update sites (they have changed locations since the last CZT updates). Also, could you try using Eclipse Mars with Java 8, Maven 3.3.3 and the version of m2e that comes with Mars? I have tried fixing so it works with the recent versions but have not tested with older ones. With this configuration (Java 8, Maven 3.3.3, Eclipse Mars), the import of CZT works. There may be a bit of issues with dependency resolution in net.sourceforge.czt.eclipse.ui (known issue) but I have not found a way to resolve it yet or what causes the problem. Also, the instructions in http://czt.sourceforge.net/dev/eclipse/ <http://czt.sourceforge.net/dev/eclipse/index.html> are a bit out-of-date, so use the versions indicated in this email. XING Chang, Please try running the latest versions as written above. Also, you need to be online to resolve the necessary m2e connectors. Let me know how it goes! And sorry about all the issues.. Andrius On Sat, 8 Aug 2015 at 10:01 ky582 <ky...@yo...> wrote: > Hello, > > I am using CZT with Eclipse and Maven 3.2.5 on Mac OS X (I also used Maven > 3.0.4 on Ubuntu before). So Maven 3 should not be a problem. The only > problem to follow "Setup CZT in Eclipse” ( > http://czt.sourceforge.net/dev/eclipse/index.html) instruction is that > the update site (http://czt.sourceforge.net/dev/eclipse/updates/) doesn’t > work for me to install two m2e connectors. Because I have another previous > setup on Ubuntu as well, my solution is to export these connectors and then > install them in new environment. > > I am not sure if it is the case for XINGChang because I can not see his > attached screen shot in this mail list. > > Regards, > Randall > > On 7 Aug 2015, at 13:17, Leo Freitas <leo...@ne...> wrote: > > Hi, > > Okay. When I had such issues it usually meant my eclipse installation was > missing the plugins, but Eclipse usually managed to find them. The hint > about maven 2/3 is good. > > @Andrius knows better about these things. Would you have something to > suggest? > > Best, > Leo > > On 7 Aug 2015, at 02:59, XINGChang <aub...@ou...> wrote: > > Hi, > > Thanks for you reply. My work would aim to enhance the current > type-checker for OZ. My supervisor just said that the type-checker has some > problems when processing recursive data structure. > > Git is not problem and I know how to use it. And I'll look at Maven some > more today, Thanks for your suggestion. > > But I'd like to establish the developing environment as the first step, > but when I tried to import the project, follow the tutorial from the > sourceforge page, I got an error like this: > > > <Screen Shot 2015-08-07 at 11.21.44 AM.png> > > > Maven failed to download some plug-ins. I tried to search related > information in Google but I don't get any solution about this. Someone told > that maybe the project uses Maven 2 and I have Maven 3 installed, is it? > > Thank you! > > Regards. > > XING, Chang > > Zhejiang University > > > ------------------------------ > From: leo...@ne... > To: aub...@ou... > CC: czt...@li... > Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. > Date: Thu, 6 Aug 2015 15:17:36 +0000 > > Hi, > > Nice to hear about work to do within CZT and OZ. > > It is possible to use intelij but we have it all setup for Eclipse. You > will need the Maven integration within InteliJ, but I don’t know how that > goes. > > CZT is slightly complex but relatively well organised. You will also need > to learn Git to be able to commit. I suggest you clone the repository and > branch it for your use. > You can then have a look at typechecker-oz and parser-oz projects to see > what you need to change. Which is what exactly by the way? I mean, are you > extending the > OZ language or type type system or both? > > Learning the basics of Maven is important, but that’s not too bad. Asking > questions here is also a good way forward. Try using the development > environment for a small change, or look at the various examples within > different projects and eventually you will get there :-) > > Good luck! > > Best, > Leo > > > On 5 Aug 2015, at 12:16, 邢畅 <aub...@ou...> wrote: > > Hi > > Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ > and doing a project about Object-Z now. My supervisor is professor Graeme > Paul Smith, and the thesis aims to enhance the type-checker used by CZT > project. So can I join the Mailing list and post questions here? I think > it's may be a hard task. > > I'm not that familiar with CZT and have no idea about the IDEs. I tried to > clone the project and import the Maven project into IntelliJ IDEA but > failed. I can't make IDEA resolve the complex dependencies so I changed to > use Eclipse and follow the instruction from the page( > http://czt.sourceforge.net/dev/eclipse/index.html). > > But I encountered a question again, I failed to import the project because > it lacks some plugin, as shown in the image attached. > > Sorry, I'm not familiar with Maven and Eclipse, I only know some language > knowledge about Java without any additional knowledge about it's > ecosystem...If the question is too obvious or stupid, could you please what > kind of things should I learn first? > > Thank you all. > > Regards. > > XING, Chang > > Zhejiang University > > ------------------------------------------------------------------------------ > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > > > > ------------------------------------------------------------------------------ > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > > > |
|
From: Chang X. <aub...@ou...> - 2015-08-08 09:04:36
|
Hi Mark,
Thanks for your suggestion.
I tried several times again and seems found the problem.
First, I reinstalled the M2Eclipse Plugin to the latest version(1.6), and installed maven-jflex-plugin(1.2).
Second, I import the whole czt-code project, and installed all the plug-ins required. Eclipse found those plug-ins successfully this time! But the only xml-maven-plugin cannot be found this time.
So after I've imported the project, I tried to install the XML transformer from the eclipse 'install new software' menu, then I got this error:
The error message is:
Cannot complete the install because of a conflicting dependency. Software being installed: m2e Connector for XML Transform 1.0.0 (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) Software currently installed: m2e - Maven Integration for Eclipse (includes Incubating components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338) Only one of the following can be installed at once: Maven Integration for Eclipse JDT 1.4.0.20130601-0317 (org.eclipse.m2e.jdt 1.4.0.20130601-0317) Maven Integration for Eclipse JDT 1.5.0.20140606-0033 (org.eclipse.m2e.jdt 1.5.0.20140606-0033) Maven Integration for Eclipse JDT 1.5.1.20150109-1820 (org.eclipse.m2e.jdt 1.5.1.20150109-1820) Maven Integration for Eclipse JDT 1.4.1.20140328-1905 (org.eclipse.m2e.jdt 1.4.1.20140328-1905) Maven Integration for Eclipse JDT 1.6.0.20150526-2032 (org.eclipse.m2e.jdt 1.6.0.20150526-2032) Maven Integration for Eclipse JDT 1.5.2.20150413-2215 (org.eclipse.m2e.jdt 1.5.2.20150413-2215) Maven Integration for Eclipse JDT 1.6.1.20150625-2338 (org.eclipse.m2e.jdt 1.6.1.20150625-2338) Cannot satisfy dependency: From: m2e connector for XML Plugin 1.0.0 (nl.mwensveen.m2e.extras.xml.transform 1.0.0) To: bundle org.eclipse.m2e.jdt [1.0.0,1.5.0) Cannot satisfy dependency: From: m2e Connector for XML Transform 1.0.0 (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) To: nl.mwensveen.m2e.extras.xml.transform [1.0.0] Cannot satisfy dependency: From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338) To: org.eclipse.m2e.jdt [1.6.1.20150625-2338]
Seems that XML Transformer is conflict with the latest M2E plug-ins and only accept M2E under 1.5.0?
But I cannot downgrade M2E because it's built-in by Eclipse Mars(4.5). So I reinstalled Eclipse with built-in M2E(1.6) and try to install the XML Transformer again, it success. If I want to upgrade M2E, the following errors appear:
Your original request has been modified. "m2e - slf4j over logback logging (Optional)" is already installed, so an update will be performed instead. "m2e - Maven Integration for Eclipse (includes Incubating components)" is already installed, so an update will be performed instead.Cannot complete the install because of a conflicting dependency. Software being installed: m2e - Maven Integration for Eclipse (includes Incubating components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338) Software currently installed: m2e Connector for XML Transform 1.0.0 (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) Only one of the following can be installed at once: Maven Integration for Eclipse JDT 1.4.0.20130601-0317 (org.eclipse.m2e.jdt 1.4.0.20130601-0317) Maven Integration for Eclipse JDT 1.5.0.20140606-0033 (org.eclipse.m2e.jdt 1.5.0.20140606-0033) Maven Integration for Eclipse JDT 1.5.1.20150109-1820 (org.eclipse.m2e.jdt 1.5.1.20150109-1820) Maven Integration for Eclipse JDT 1.4.1.20140328-1905 (org.eclipse.m2e.jdt 1.4.1.20140328-1905) Maven Integration for Eclipse JDT 1.6.0.20150526-2032 (org.eclipse.m2e.jdt 1.6.0.20150526-2032) Maven Integration for Eclipse JDT 1.5.2.20150413-2215 (org.eclipse.m2e.jdt 1.5.2.20150413-2215) Maven Integration for Eclipse JDT 1.6.1.20150625-2338 (org.eclipse.m2e.jdt 1.6.1.20150625-2338) Cannot satisfy dependency: From: m2e connector for XML Plugin 1.0.0 (nl.mwensveen.m2e.extras.xml.transform 1.0.0) To: bundle org.eclipse.m2e.jdt [1.0.0,1.5.0) Cannot satisfy dependency: From: m2e Connector for XML Transform 1.0.0 (nl.mwensveen.m2e.extras.xml.transform.feature.feature.group 1.0.0) To: nl.mwensveen.m2e.extras.xml.transform [1.0.0] Cannot satisfy dependency: From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338) To: org.eclipse.m2e.jdt [1.6.1.20150625-2338]
But once I upgraded to the latest version, Eclipse works almost correct:
Except the xml-maven-plugin...
The the conclusion is, only the latest M2E can install all the plug-ins except the XML Transformer.
So, please, does anyone knows how to handle this situation?
---
Hi, ky582,
Thanks for your reply, I forget the screenshot at the first email, the error looks like this:
And I think it's maybe a good option, I use OS X too, with Maven 3.3.3 and Eclipse 4.5, maybe anyone who has the same configuration can export the project and send to me then I can import it without errors.
Thank you again~
Regards.XING, ChangZhejiang University
Date: Sat, 8 Aug 2015 15:32:31 +1000
Subject: Re: [CZT-Devel] [czt-devel] New Member and Question.
From: bm....@gm...
To: leo...@ne...
CC: aub...@ou...; czt...@li...
Chang,
I'm currently using Maven 3.2.2, and had no trouble building CZT yesterday. But it is quite common for Maven to have trouble downloading something - perhaps due to internet timeouts. I find it is sometimes worth trying again a couple of times, and if necessary try at another time of the day.
Good luck!Mark
On 7 August 2015 at 22:17, Leo Freitas <leo...@ne...> wrote:
Hi,
Okay. When I had such issues it usually meant my eclipse installation was missing the plugins, but Eclipse usually managed to find them. The hint about maven 2/3 is good.
@Andrius knows better about these things. Would you have something to suggest?
Best,Leo
On 7 Aug 2015, at 02:59, XINGChang <aub...@ou...> wrote:
Hi,
Thanks for you reply. My work would aim to enhance the current type-checker for OZ. My supervisor just said that the type-checker has some problems when processing recursive data structure.
Git is not problem and I know how to use it. And I'll look at Maven some more today, Thanks for your suggestion.
But I'd like to establish the developing environment as the first step, but when I tried to import the project, follow the tutorial from the sourceforge page, I got an error like this:
<Screen Shot 2015-08-07 at 11.21.44 AM.png>
Maven failed to download some plug-ins. I tried to search related information in Google but I don't get any solution about this. Someone told that maybe the project uses Maven 2 and I have Maven 3 installed, is it?
Thank you!
Regards.XING, ChangZhejiang University
From: leo...@ne...
To: aub...@ou...
CC: czt...@li...
Subject: Re: [CZT-Devel] [czt-devel] New Member and Question.
Date: Thu, 6 Aug 2015 15:17:36 +0000
Hi,
Nice to hear about work to do within CZT and OZ.
It is possible to use intelij but we have it all setup for Eclipse. You will need the Maven integration within InteliJ, but I don’t know how that goes.
CZT is slightly complex but relatively well organised. You will also need to learn Git to be able to commit. I suggest you clone the repository and branch it for your use.You can then have a look at typechecker-oz and parser-oz projects to see what you need to change. Which is what exactly by the way? I mean, are you extending theOZ language or type type system or both?
Learning the basics of Maven is important, but that’s not too bad. Asking questions here is also a good way forward. Try using the development environment for a small change, or look at the various examples within different projects and eventually you will get there :-)
Good luck!
Best,Leo
On 5 Aug 2015, at 12:16, 邢畅 <aub...@ou...> wrote:
Hi
Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ and doing a project about Object-Z now. My supervisor is professor Graeme Paul Smith, and the thesis aims to enhance the type-checker used by CZT project. So can I join the Mailing list and post questions here? I think it's may be a hard task.
I'm not that familiar with CZT and have no idea about the IDEs. I tried to clone the project and import the Maven project into IntelliJ IDEA but failed. I can't make IDEA resolve the complex dependencies so I changed to use Eclipse and follow the instruction from the page(http://czt.sourceforge.net/dev/eclipse/index.html).
But I encountered a question again, I failed to import the project because it lacks some plugin, as shown in the image attached.
Sorry, I'm not familiar with Maven and Eclipse, I only know some language knowledge about Java without any additional knowledge about it's ecosystem...If the question is too obvious or stupid, could you please what kind of things should I learn first?
Thank you all.
Regards.XING, ChangZhejiang University------------------------------------------------------------------------------_______________________________________________CZT-Devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/czt-devel
------------------------------------------------------------------------------
_______________________________________________
CZT-Devel mailing list
CZT...@li...
https://lists.sourceforge.net/lists/listinfo/czt-devel
|
|
From: ky582 <ky...@yo...> - 2015-08-08 09:00:43
|
Hello, I am using CZT with Eclipse and Maven 3.2.5 on Mac OS X (I also used Maven 3.0.4 on Ubuntu before). So Maven 3 should not be a problem. The only problem to follow "Setup CZT in Eclipse” (http://czt.sourceforge.net/dev/eclipse/index.html <http://czt.sourceforge.net/dev/eclipse/index.html>) instruction is that the update site (http://czt.sourceforge.net/dev/eclipse/updates/ <http://czt.sourceforge.net/dev/eclipse/updates/>) doesn’t work for me to install two m2e connectors. Because I have another previous setup on Ubuntu as well, my solution is to export these connectors and then install them in new environment. I am not sure if it is the case for XINGChang because I can not see his attached screen shot in this mail list. Regards, Randall > On 7 Aug 2015, at 13:17, Leo Freitas <leo...@ne...> wrote: > > Hi, > > Okay. When I had such issues it usually meant my eclipse installation was missing the plugins, but Eclipse usually managed to find them. The hint about maven 2/3 is good. > > @Andrius knows better about these things. Would you have something to suggest? > > Best, > Leo > >> On 7 Aug 2015, at 02:59, XINGChang <aub...@ou... <mailto:aub...@ou...>> wrote: >> >> Hi, >> >> Thanks for you reply. My work would aim to enhance the current type-checker for OZ. My supervisor just said that the type-checker has some problems when processing recursive data structure. >> >> Git is not problem and I know how to use it. And I'll look at Maven some more today, Thanks for your suggestion. >> >> But I'd like to establish the developing environment as the first step, but when I tried to import the project, follow the tutorial from the sourceforge page, I got an error like this: >> >> <Screen Shot 2015-08-07 at 11.21.44 AM.png> >> >> Maven failed to download some plug-ins. I tried to search related information in Google but I don't get any solution about this. Someone told that maybe the project uses Maven 2 and I have Maven 3 installed, is it? >> >> Thank you! >> >> Regards. >> >> XING, Chang >> >> Zhejiang University >> >> >> From: leo...@ne... <mailto:leo...@ne...> >> To: aub...@ou... <mailto:aub...@ou...> >> CC: czt...@li... <mailto:czt...@li...> >> Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. >> Date: Thu, 6 Aug 2015 15:17:36 +0000 >> >> Hi, >> >> Nice to hear about work to do within CZT and OZ. >> >> It is possible to use intelij but we have it all setup for Eclipse. You will need the Maven integration within InteliJ, but I don’t know how that goes. >> >> CZT is slightly complex but relatively well organised. You will also need to learn Git to be able to commit. I suggest you clone the repository and branch it for your use. >> You can then have a look at typechecker-oz and parser-oz projects to see what you need to change. Which is what exactly by the way? I mean, are you extending the >> OZ language or type type system or both? >> >> Learning the basics of Maven is important, but that’s not too bad. Asking questions here is also a good way forward. Try using the development environment for a small change, or look at the various examples within different projects and eventually you will get there :-) >> >> Good luck! >> >> Best, >> Leo >> >> On 5 Aug 2015, at 12:16, 邢畅 <aub...@ou... <mailto:aub...@ou...>> wrote: >> >> Hi >> >> Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ and doing a project about Object-Z now. My supervisor is professor Graeme Paul Smith, and the thesis aims to enhance the type-checker used by CZT project. So can I join the Mailing list and post questions here? I think it's may be a hard task. >> >> I'm not that familiar with CZT and have no idea about the IDEs. I tried to clone the project and import the Maven project into IntelliJ IDEA but failed. I can't make IDEA resolve the complex dependencies so I changed to use Eclipse and follow the instruction from the page(http://czt.sourceforge.net/dev/eclipse/index.html <http://czt.sourceforge.net/dev/eclipse/index.html>). >> >> But I encountered a question again, I failed to import the project because it lacks some plugin, as shown in the image attached. >> >> Sorry, I'm not familiar with Maven and Eclipse, I only know some language knowledge about Java without any additional knowledge about it's ecosystem...If the question is too obvious or stupid, could you please what kind of things should I learn first? >> >> Thank you all. >> >> Regards. >> >> XING, Chang >> >> Zhejiang University >> ------------------------------------------------------------------------------ >> _______________________________________________ >> CZT-Devel mailing list >> CZT...@li... <mailto:CZT...@li...> >> https://lists.sourceforge.net/lists/listinfo/czt-devel <https://lists.sourceforge.net/lists/listinfo/czt-devel> > ------------------------------------------------------------------------------ > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel |
|
From: Mark U. <bm....@gm...> - 2015-08-08 05:32:39
|
Chang, I'm currently using Maven 3.2.2, and had no trouble building CZT yesterday. But it is quite common for Maven to have trouble downloading something - perhaps due to internet timeouts. I find it is sometimes worth trying again a couple of times, and if necessary try at another time of the day. Good luck! Mark On 7 August 2015 at 22:17, Leo Freitas <leo...@ne...> wrote: > Hi, > > Okay. When I had such issues it usually meant my eclipse installation was > missing the plugins, but Eclipse usually managed to find them. The hint > about maven 2/3 is good. > > @Andrius knows better about these things. Would you have something to > suggest? > > Best, > Leo > > On 7 Aug 2015, at 02:59, XINGChang <aub...@ou...> wrote: > > Hi, > > Thanks for you reply. My work would aim to enhance the current > type-checker for OZ. My supervisor just said that the type-checker has some > problems when processing recursive data structure. > > Git is not problem and I know how to use it. And I'll look at Maven some > more today, Thanks for your suggestion. > > But I'd like to establish the developing environment as the first step, > but when I tried to import the project, follow the tutorial from the > sourceforge page, I got an error like this: > > > <Screen Shot 2015-08-07 at 11.21.44 AM.png> > > > Maven failed to download some plug-ins. I tried to search related > information in Google but I don't get any solution about this. Someone told > that maybe the project uses Maven 2 and I have Maven 3 installed, is it? > > Thank you! > > Regards. > > XING, Chang > > Zhejiang University > > > ------------------------------ > From: leo...@ne... > To: aub...@ou... > CC: czt...@li... > Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. > Date: Thu, 6 Aug 2015 15:17:36 +0000 > > > Hi, > > Nice to hear about work to do within CZT and OZ. > > It is possible to use intelij but we have it all setup for Eclipse. You > will need the Maven integration within InteliJ, but I don’t know how that > goes. > > CZT is slightly complex but relatively well organised. You will also need > to learn Git to be able to commit. I suggest you clone the repository and > branch it for your use. > You can then have a look at typechecker-oz and parser-oz projects to see > what you need to change. Which is what exactly by the way? I mean, are you > extending the > OZ language or type type system or both? > > Learning the basics of Maven is important, but that’s not too bad. Asking > questions here is also a good way forward. Try using the development > environment for a small change, or look at the various examples within > different projects and eventually you will get there :-) > > Good luck! > > Best, > Leo > > > On 5 Aug 2015, at 12:16, 邢畅 <aub...@ou...> wrote: > > Hi > > Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ > and doing a project about Object-Z now. My supervisor is professor Graeme > Paul Smith, and the thesis aims to enhance the type-checker used by CZT > project. So can I join the Mailing list and post questions here? I think > it's may be a hard task. > > I'm not that familiar with CZT and have no idea about the IDEs. I tried to > clone the project and import the Maven project into IntelliJ IDEA but > failed. I can't make IDEA resolve the complex dependencies so I changed to > use Eclipse and follow the instruction from the page( > http://czt.sourceforge.net/dev/eclipse/index.html). > > But I encountered a question again, I failed to import the project because > it lacks some plugin, as shown in the image attached. > > Sorry, I'm not familiar with Maven and Eclipse, I only know some language > knowledge about Java without any additional knowledge about it's > ecosystem...If the question is too obvious or stupid, could you please what > kind of things should I learn first? > > Thank you all. > > Regards. > > XING, Chang > > Zhejiang University > > ------------------------------------------------------------------------------ > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > > |
|
From: Leo F. <leo...@ne...> - 2015-08-07 12:17:18
|
Hi, Okay. When I had such issues it usually meant my eclipse installation was missing the plugins, but Eclipse usually managed to find them. The hint about maven 2/3 is good. @Andrius knows better about these things. Would you have something to suggest? Best, Leo > On 7 Aug 2015, at 02:59, XINGChang <aub...@ou...> wrote: > > Hi, > > Thanks for you reply. My work would aim to enhance the current type-checker for OZ. My supervisor just said that the type-checker has some problems when processing recursive data structure. > > Git is not problem and I know how to use it. And I'll look at Maven some more today, Thanks for your suggestion. > > But I'd like to establish the developing environment as the first step, but when I tried to import the project, follow the tutorial from the sourceforge page, I got an error like this: > > <Screen Shot 2015-08-07 at 11.21.44 AM.png> > > Maven failed to download some plug-ins. I tried to search related information in Google but I don't get any solution about this. Someone told that maybe the project uses Maven 2 and I have Maven 3 installed, is it? > > Thank you! > > Regards. > > XING, Chang > > Zhejiang University > > > From: leo...@ne... <mailto:leo...@ne...> > To: aub...@ou... <mailto:aub...@ou...> > CC: czt...@li... <mailto:czt...@li...> > Subject: Re: [CZT-Devel] [czt-devel] New Member and Question. > Date: Thu, 6 Aug 2015 15:17:36 +0000 > > Hi, > > Nice to hear about work to do within CZT and OZ. > > It is possible to use intelij but we have it all setup for Eclipse. You will need the Maven integration within InteliJ, but I don’t know how that goes. > > CZT is slightly complex but relatively well organised. You will also need to learn Git to be able to commit. I suggest you clone the repository and branch it for your use. > You can then have a look at typechecker-oz and parser-oz projects to see what you need to change. Which is what exactly by the way? I mean, are you extending the > OZ language or type type system or both? > > Learning the basics of Maven is important, but that’s not too bad. Asking questions here is also a good way forward. Try using the development environment for a small change, or look at the various examples within different projects and eventually you will get there :-) > > Good luck! > > Best, > Leo > > On 5 Aug 2015, at 12:16, 邢畅 <aub...@ou... <mailto:aub...@ou...>> wrote: > > Hi > > Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ and doing a project about Object-Z now. My supervisor is professor Graeme Paul Smith, and the thesis aims to enhance the type-checker used by CZT project. So can I join the Mailing list and post questions here? I think it's may be a hard task. > > I'm not that familiar with CZT and have no idea about the IDEs. I tried to clone the project and import the Maven project into IntelliJ IDEA but failed. I can't make IDEA resolve the complex dependencies so I changed to use Eclipse and follow the instruction from the page(http://czt.sourceforge.net/dev/eclipse/index.html <http://czt.sourceforge.net/dev/eclipse/index.html>). > > But I encountered a question again, I failed to import the project because it lacks some plugin, as shown in the image attached. > > Sorry, I'm not familiar with Maven and Eclipse, I only know some language knowledge about Java without any additional knowledge about it's ecosystem...If the question is too obvious or stupid, could you please what kind of things should I learn first? > > Thank you all. > > Regards. > > XING, Chang > > Zhejiang University > ------------------------------------------------------------------------------ > _______________________________________________ > CZT-Devel mailing list > CZT...@li... <mailto:CZT...@li...> > https://lists.sourceforge.net/lists/listinfo/czt-devel <https://lists.sourceforge.net/lists/listinfo/czt-devel> |
|
From: Leo F. <leo...@ne...> - 2015-08-06 15:17:48
|
Hi, Nice to hear about work to do within CZT and OZ. It is possible to use intelij but we have it all setup for Eclipse. You will need the Maven integration within InteliJ, but I don’t know how that goes. CZT is slightly complex but relatively well organised. You will also need to learn Git to be able to commit. I suggest you clone the repository and branch it for your use. You can then have a look at typechecker-oz and parser-oz projects to see what you need to change. Which is what exactly by the way? I mean, are you extending the OZ language or type type system or both? Learning the basics of Maven is important, but that’s not too bad. Asking questions here is also a good way forward. Try using the development environment for a small change, or look at the various examples within different projects and eventually you will get there :-) Good luck! Best, Leo > On 5 Aug 2015, at 12:16, 邢畅 <aub...@ou...> wrote: > > Hi > > Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ and doing a project about Object-Z now. My supervisor is professor Graeme Paul Smith, and the thesis aims to enhance the type-checker used by CZT project. So can I join the Mailing list and post questions here? I think it's may be a hard task. > > I'm not that familiar with CZT and have no idea about the IDEs. I tried to clone the project and import the Maven project into IntelliJ IDEA but failed. I can't make IDEA resolve the complex dependencies so I changed to use Eclipse and follow the instruction from the page(http://czt.sourceforge.net/dev/eclipse/index.html <http://czt.sourceforge.net/dev/eclipse/index.html>). > > But I encountered a question again, I failed to import the project because it lacks some plugin, as shown in the image attached. > > Sorry, I'm not familiar with Maven and Eclipse, I only know some language knowledge about Java without any additional knowledge about it's ecosystem...If the question is too obvious or stupid, could you please what kind of things should I learn first? > > Thank you all. > > Regards. > > XING, Chang > > Zhejiang University > ------------------------------------------------------------------------------ > _______________________________________________ > CZT-Devel mailing list > CZT...@li... <mailto:CZT...@li...> > https://lists.sourceforge.net/lists/listinfo/czt-devel <https://lists.sourceforge.net/lists/listinfo/czt-devel> |
|
From: 邢畅 <aub...@ou...> - 2015-08-05 11:16:07
|
Hi Sorry for bothering, I'm new here. My name is Chang. I'm a student of UQ and doing a project about Object-Z now. My supervisor is professor Graeme Paul Smith, and the thesis aims to enhance the type-checker used by CZT project. So can I join the Mailing list and post questions here? I think it's may be a hard task. I'm not that familiar with CZT and have no idea about the IDEs. I tried to clone the project and import the Maven project into IntelliJ IDEA but failed. I can't make IDEA resolve the complex dependencies so I changed to use Eclipse and follow the instruction from the page(http://czt.sourceforge.net/dev/eclipse/index.html). But I encountered a question again, I failed to import the project because it lacks some plugin, as shown in the image attached. Sorry, I'm not familiar with Maven and Eclipse, I only know some language knowledge about Java without any additional knowledge about it's ecosystem...If the question is too obvious or stupid, could you please what kind of things should I learn first? Thank you all. Regards.XING, ChangZhejiang University |
|
From: Matheus G. T. <mtr...@in...> - 2015-01-26 17:10:21
|
Dear All, I am a Brazilian student and I am interested in developing a code generator for a dialect of Circus. To do so, I need to manipulate a AST instance, and I am not sure exactly how to do that. I would appreciate to get some information on how to run the parsers so I can get the AST. Thanks in advance -- Matheus Garay Trindade |
|
From: Andrius V. <and...@ne...> - 2013-05-30 15:18:10
|
Hi everyone, Just quick notification - I would encourage CZT developers to subscribe to CZT discussion forums. This way you will be notified about questions asked through the forums. To subscribe via e-mail, click the "email" icon on the top-right of each forum windows: - Help forum: https://sourceforge.net/p/czt/discussion/295268/ - Open forum: https://sourceforge.net/p/czt/discussion/295267/ This should allow us to answer forum questions as quickly as we do with czt-users and czt-devel. Thanks! Andrius |
|
From: <an...@an...> - 2013-04-16 08:42:40
|
Dear Tim Thanks for this. I don't think we should let the memory management issue force us into a position where we violate Z semantics, or have a special mode. I'm not sure whether the improvement Andrius found, and others like it, actually require that ids be the same in different schemas. I don't know whether the copying he was referring to was one that changed the ids or not. If not, maybe we can still improve memory usage without a semantic change. But if so, then perhaps there are other possible solutions? First, maybe it would be OK to copy the ZName, as long as in doing so we didn't copy any of its components? I suspect (but don't know) that the copy currently gets a new ZWord, LcAnn etc? If that wouldn't solve the problem, then perhaps we can keep some sort of id but interpret it in a way consistent with the semantics. Suppose I have x defined in schema A and then included in B. Given that its occurrence in B is, by definition of the semantics, unique, we don't actually need to assign a different id to tell us that. All we need to know is that it is a schema variable not a global one. So if the id were changed in some way to indicate the scope of the variable (global, schema, or expression-local) plus a pointer back to a declaration instance, then we could have exactly the same ZName in every schema without violating the semantics., This seems consistent with your point that ids need to be unique but actually the tools don't care - they don't care because the uniqueness to the schema is part of the language and doesn't need a separate indication. Would this reconcile the two issues, of correctness vs efficiency, do you think? (I'm writing this just before going on holiday, so please forgive the fact that I won't respond to any further discussion for a couple of weeks) All the best Anthony > On 16 April 2013 at 01:55 Tim Miller <tm...@un...> wrote: > > > Hi Anthony, > > You wrote: > > Can I ask a question about ids? I had understood that the id was necessary > > for distinguishing truly different instances of a name - for example x > > declared globally and x within a schema. > > Yep, that's correct. > > > If that's true we can't presumably > > drop ids altogether? Certainly I use them in my cross reference (as you may > > remember, we had extensive discussions about this) and I've just been > > looking at the "Go To Declaration" tool in the Eclipse IDE, which I think > > uses the word + id as the unique identifier of a name. > > > > So I wonder whether we do need to keep the id, but not to create a new id > > for every schema inclusion? If I declare x in S and then include S in T, I > > don't think we should need a new id for the x in T, for example. > > It creates a new ID because it is a new variable. I did it like this > because it is consistent with the semantics of Z. If x is declared in S > and then S included in T, the variable x is indeed a new variable, > because the semantics are that the definition of T is identical to the > case that the declarations and predicate from S are "cut and paste" into > T. So, the following: > > S == [x : X]; > T == [S; y : Y] > > is semantically equivalent to: > > S == [x : X]; > T == [x : X; y : Y] > > If we were to not declare a new ID for the x in the first example, then > the two declarations of x the first example would have the same ID, > while in the second, they would be different. I'm not comfortable with > that inconsistency. > > I'm not arguing that this is really important (I can't see that any of > our tools would care), but this is the motivation. I would prefer to > preserve the semantics as is currently, and just have a mode where the > IDs are not renamed. In fact, this second mode would be nice for tracing > variable declarations in Z state machines, as we can link included state > variables back to their definition in a state schema quite easily. To do > this now, we would have to pass the definitions in more detail. > > > Also, there the special id deltaxi, which presumably needs to be kept or > > replaced with a different mechanism? > > > The id deltaxi was added by someone other than me (Leo I guess?) and I > don't know what the motivation for that was, instead of e.g. just > allocating a fresh ID. > > > At the moment it also seems to be true that there are many instances of a > > ZName with the same id - that too could presumably be avoided? > > > I can't comment on that without looking further. I would assume that you > are right because I appear to have created a method in the typechecker > factory for copying names. One shortcut would be to just return the same > instance for that method, but I'm not really sure. I can certainly look > into this further once we have a consensus on how we should handle this. > > Cheers, > Tim > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel |
|
From: Leo F. <leo...@ne...> - 2013-04-16 08:15:42
|
Hi all, As promised, prior to the upcoming release we tried to collect the "activity" within CZT in the past few years with the major udpates/developments divided by categories of functionality, improvement, IDE, and admin. The list is not exhaustive and we will add it to the website as "features" and try to keep them up-to date as much as possible. Thanks to Andrius efforts on nightly builds and the website this should be straightforward to do now :-). Best, Leo & Andrius === New functionality === * Z Verification Condition Generator = Z VC infrastructure: + DefinitionTable extension to infer declared types, and schema calculus usage within specs + Predicate transformers for VC automatic simplification + file-based and programmable integration = Domain Checking VCs for consistency of function application, definite description (\mu), and unique existential quantification = Feasibility VCs for precondition calculation over a given state and operations + user-defined configuration as a special schema determines what VCs to generate + VCs generated according to a prescribed pattern, including state initialisation + Added signature schemas for modular generation of VCs + Added VCs for axiomatic definitions consistency and given type non-emptyness + File-based VC generation (i.e. result is a new section with VCs) + Eclipse integration to ensure all VCs generated are accounted for in Spec = Refinement VCs for forward/backward simulation + support for interface refinement rules + takes initialisation and finalisation into account + user-defined configuration as a special schema determining VCs to generate + VCs for correctness, applicability, init/final, and I/O * New language extensions (i.e. AST, parser, printer, type checker, IDE integration) = ZEves proof language integration = Circus Jokers / Wildcards for Rules (Under development) = Circus time = Object Oriented Circus (Oh Circus) = Oh Circus extended with pointers and Time * ZEves integration = Iso-Z (CZT) to Fuzz-like-Z (ZEves) translator = CZT-XML to EVES-XML input = EVES-XML output to CZT (Unicode and LaTeX) = interpretation of ZEves results (i.e. lemmas used, new prover goals, etc) = ZEves session useful for extending tools to interact/inspect/interfere with the proof session = Socket-based connection to the EVES server (i.e. completely subsumes ZEves front-end interfaces) = extended parser/printer to copy with new proof commands and proof environment = session snapshots to enable integration with proof inspection tools for replay / learning from proof attempts (see www.ai4fm.org) = programmable encoding of new proof tactics = extensive test set from Grand Challenge repository of experiments (i.e. Tokeneer, Mondex, POSIX file stores, Flash Memory, etc). * experimental = z2b translation = z2alloy translation = ZEves jEdit plugin === Improvements === * improved memory management of names = memory profiling to detected/fixed leaks in parser I/O, Factory classes, and AST default list sizes (now zeroed) (55% memory footprint decrease) = traceability of AST instances for aiding debugging of dangling references and future memory leaks = traceability of ZName usage/creation as it became the key AST class for memory improvement/usage = TODO: recent discovery of Signature copying in type checker leading to possible memory improvement (under investigation) * section management = transaction-based section management for improved performance on large specifications (i.e. avoid reparsing/typechecking) + avoids reloading of sections + takes transitive dependencies into account (up/downwards and diamond dependencies) + widened scope of transaction in case of low-level parsers like LaTeXMarkupScanner, which bootstraps high-level parsing = normalised access to standard/known Sections = normalised access to SectionManager through explicit use of extension/dialect of interest = SectionManager performance and documentation improvements * code warnings and generics = CZT had about 10000 warnings across various projects, now it has 6! (this was partially historic --- Java Generics ---, partly dependant on external tools --- CUP/GnAST code generated with warnings, partially coding practices to avoid now easily captured by IDEs). Overall the exercise normalised code, improved clarity and rooted out some tricky real bugs from these warnings. = remainder warnings are now to be taken as features being or yet to being implemented. * low-level tools update: GnAST = GNAsT update as a maven plugin with extra controlling parameters = Corejava build per extension to avoid slow rebuilds = warning-free code generation + generics aware code = added debugging information for Velocity generation = proper handling of Enum types from ZML declarations = fixed bugs on list handling and JAXB property elements for XML integration * low-level tools update: java-CUP = can cope with large grammars as external files (i.e. Circus onwards generated Java file beyond allowed size). = better debugging information for grammar-code generation to allow for fine-tuning and warning elimination * low-level tools update: others = update use of logging to be more consistent across various tools = added warning manager across developments = basic CZTManagedTestCase class for consistent test case coding standard === IDE === * Extended Eclipse integration = CZT-ide product as a standalone Eclipse application = basic for Circus and Object-Z (i.e. use of type checker + extended char map) = thorough for Z and ZEves (i.e. syntax highlight, auto-completion, various squiggles, outline, etc). = VCG integration with theorems proved / to-prove view = ZEves link/integration via Z-XML Api = various markup conversions and type checking information as tooltips * Website update = modern look-and-feel = markdown-based website for easy extension = wiki-like document ion based on text files === Adeministrative === * Move to Git = easy of branch/merge for parallel (independent) developments = fine-grained control of commits and histories * Improved documentation = added java doc at key (mostly requested) parts (i.e. section manager, parsing, lang-extension etc) = installation, update, build documentation and instructions (including for Eclipse builds) * Project separation / rearrangement = parent maven project for: vcg, corejava, type checker, parser, etc = this enables uniform maven integration and dependency checking = also helps IDE integration for development with Eclipse and Netbeans = easier for new language extensions * Nightly builds via Jenkins server = automatic nightly builds of czt.jar, IDEs (jEdit + Eclipse) = automatic javadoc and website builds |
|
From: Leo F. <leo...@ne...> - 2013-04-16 06:57:47
|
Hi Tim, Andrius and I have been discussing possible solutions yesterday for memory improvements. It revolves around rearranging how the checkForDuplicates method, called at key points for ID merging in the schema calculus (and a few other places), rely on signatures being copied. If copying is to be relaxed (i.e. the culprit for 60% memory shoot up), adjustments elsewhere are needed to ensure the semantics intended by the IDs is preserved. Incidentally, the del taxi id was something I added to ensure the intended postcondition for the ID database was kept (i.e. all ZNames associated with the same id in the ID database have the same "word" naming). Without setDeltaXi, the DeltaXI case would break the invariant, so it's just a "marker" really to declare that isn't a name where IDs matters much in so far as the invariant is concerned. See net.sourceforge.czt.typecheck.z.util.AbstractTypeEnv.getDeltaXiType(ZName zName, Type type) [l163] net.sourceforge.czt.typecheck.z.impl.Factory.checkNameIDDBInvariant(ZName zName, List<ZName> list) [l558] Our worry for a solution that change the semantics of IDs is that we don't understand it well enough to ensure all cases will be catered for. This will require some time…. Best, Leo On 16 Apr 2013, at 01:55, Tim Miller <tm...@un...<mailto:tm...@un...>> wrote: Hi Anthony, You wrote: Can I ask a question about ids? I had understood that the id was necessary for distinguishing truly different instances of a name - for example x declared globally and x within a schema. Yep, that's correct. If that's true we can't presumably drop ids altogether? Certainly I use them in my cross reference (as you may remember, we had extensive discussions about this) and I've just been looking at the "Go To Declaration" tool in the Eclipse IDE, which I think uses the word + id as the unique identifier of a name. So I wonder whether we do need to keep the id, but not to create a new id for every schema inclusion? If I declare x in S and then include S in T, I don't think we should need a new id for the x in T, for example. It creates a new ID because it is a new variable. I did it like this because it is consistent with the semantics of Z. If x is declared in S and then S included in T, the variable x is indeed a new variable, because the semantics are that the definition of T is identical to the case that the declarations and predicate from S are "cut and paste" into T. So, the following: S == [x : X]; T == [S; y : Y] is semantically equivalent to: S == [x : X]; T == [x : X; y : Y] If we were to not declare a new ID for the x in the first example, then the two declarations of x the first example would have the same ID, while in the second, they would be different. I'm not comfortable with that inconsistency. I'm not arguing that this is really important (I can't see that any of our tools would care), but this is the motivation. I would prefer to preserve the semantics as is currently, and just have a mode where the IDs are not renamed. In fact, this second mode would be nice for tracing variable declarations in Z state machines, as we can link included state variables back to their definition in a state schema quite easily. To do this now, we would have to pass the definitions in more detail. Also, there the special id deltaxi, which presumably needs to be kept or replaced with a different mechanism? The id deltaxi was added by someone other than me (Leo I guess?) and I don't know what the motivation for that was, instead of e.g. just allocating a fresh ID. At the moment it also seems to be true that there are many instances of a ZName with the same id - that too could presumably be avoided? I can't comment on that without looking further. I would assume that you are right because I appear to have created a method in the typechecker factory for copying names. One shortcut would be to just return the same instance for that method, but I'm not really sure. I can certainly look into this further once we have a consensus on how we should handle this. Cheers, Tim ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ CZT-Devel mailing list CZT...@li... https://lists.sourceforge.net/lists/listinfo/czt-devel |
|
From: Tim M. <tm...@un...> - 2013-04-16 00:55:51
|
Hi Anthony, You wrote: > Can I ask a question about ids? I had understood that the id was necessary > for distinguishing truly different instances of a name - for example x > declared globally and x within a schema. Yep, that's correct. > If that's true we can't presumably > drop ids altogether? Certainly I use them in my cross reference (as you may > remember, we had extensive discussions about this) and I've just been > looking at the "Go To Declaration" tool in the Eclipse IDE, which I think > uses the word + id as the unique identifier of a name. > > So I wonder whether we do need to keep the id, but not to create a new id > for every schema inclusion? If I declare x in S and then include S in T, I > don't think we should need a new id for the x in T, for example. It creates a new ID because it is a new variable. I did it like this because it is consistent with the semantics of Z. If x is declared in S and then S included in T, the variable x is indeed a new variable, because the semantics are that the definition of T is identical to the case that the declarations and predicate from S are "cut and paste" into T. So, the following: S == [x : X]; T == [S; y : Y] is semantically equivalent to: S == [x : X]; T == [x : X; y : Y] If we were to not declare a new ID for the x in the first example, then the two declarations of x the first example would have the same ID, while in the second, they would be different. I'm not comfortable with that inconsistency. I'm not arguing that this is really important (I can't see that any of our tools would care), but this is the motivation. I would prefer to preserve the semantics as is currently, and just have a mode where the IDs are not renamed. In fact, this second mode would be nice for tracing variable declarations in Z state machines, as we can link included state variables back to their definition in a state schema quite easily. To do this now, we would have to pass the definitions in more detail. > Also, there the special id deltaxi, which presumably needs to be kept or > replaced with a different mechanism? > The id deltaxi was added by someone other than me (Leo I guess?) and I don't know what the motivation for that was, instead of e.g. just allocating a fresh ID. > At the moment it also seems to be true that there are many instances of a > ZName with the same id - that too could presumably be avoided? > I can't comment on that without looking further. I would assume that you are right because I appear to have created a method in the typechecker factory for copying names. One shortcut would be to just return the same instance for that method, but I'm not really sure. I can certainly look into this further once we have a consensus on how we should handle this. Cheers, Tim |
|
From: Anthony H. <an...@an...> - 2013-04-15 12:57:54
|
Dear Leo > @Anthony one case that is tricky is when you have name collusion as in S == [ x: \nat ]; T == [x : \num]; R == S \land T, where declared/unified types are different, here the two references ought to get / have the same ID. Other weird cases appear when you have schema quantification i.e. \forall T @ S, in which case the first is the declaring name? I understand that these are all examples of why the problem of deciding what a name refers to isn't straightforward. But that's a problem that has been solved before, because the typechecker has already worked out what to do in these cases. Here we are really only talking about how to record the relevant information, not the much more difficult problem of how to work it out. Since the type of a variable is its base type like \arithmos, not its declared type like \nat, there is no problem in using the same id for both cases afa the typechecker is concerned. And yes, in \forall T @ S the declarations are all in T (or an enclosing scope) - S must be consistent with them. > > Andrius and I have been discussing potential solutions that take memory and functionality preservation into account, if with some need to change practices / code in various projects. Will look at this as soon as I free myself from an Isabelle proof that is taking longer than I wanted it to :-(. It will be great if you can fix this! I expect I'll have to change my cross referencer, too, but that's OK if the new scheme is better. > PS: > Another interesting possibility is to look at what ProofPowerZ does, given it's efficient and solves similar problem? I don't know anything about it I'm afraid but I dare say Rob would help if asked. It's completely different, of course, being written in HOL/ML All the best Anthony > > Best, > Leo > > On 15 Apr 2013, at 11:22, Anthony Hall <an...@an...> wrote: > > > Tim > > > > Can I ask a question about ids? I had understood that the id was > > necessary for distinguishing truly different instances of a name - for > > example x declared globally and x within a schema. If that's true we > > can't presumably drop ids altogether? Certainly I use them in my cross > > reference (as you may remember, we had extensive discussions about > > this) and I've just been looking at the "Go To Declaration" tool in > > the Eclipse IDE, which I think uses the word + id as the unique identifier of a name. > > > > So I wonder whether we do need to keep the id, but not to create a new > > id for every schema inclusion? If I declare x in S and then include S > > in T, I don't think we should need a new id for the x in T, for > > example. Of course if I declare x in S1 and S2 and then include both > > in T, there would have to be an arbitrary choice of which id to use > > for references in T, but that's really no different from the arbitrary > > choice of location that has to be made at present if I ask where x in T is defined. > > > > Also, there the special id deltaxi, which presumably needs to be kept > > or replaced with a different mechanism? > > > > At the moment it also seems to be true that there are many instances > > of a ZName with the same id - that too could presumably be avoided? > > > > Please do say if I've misunderstood this! > > > > Thanks > > > > Anthony > > > > -----Original Message----- > > From: Tim Miller [mailto:tm...@un...] > > Sent: 15 April 2013 00:49 > > To: CZT-Devel > > Subject: Re: [CZT-Devel] Reducing memory usage: Signatures are the > > biggest culprit? > > > > Hi everyone, > > > > You wrote: > >> This lead me to thinking - do signatures really need to be duplicated > >> everywhere? I imagine that the signature of schema A would be the > >> same everywhere? Can we reuse the signature, or is it important to > >> duplicate and assign new IDs to the name? > >> > > It was, at some point, very important to create new signatures, > > because referenced schema names declare new variables into the name > > space of a specification, and we can't have 2 variables with the same > > IDs if they refer to different declarations. The IDs were a CZT-specific thing (i.e. > > not part of the standard), and were used by other tools (the > > typechecker does not require them because it keeps track of references > > in the type environments itself). > > > > Now, I'm not sure whether they are still important in CZT. Other tools > > may still rely on them. I'm pretty sure the rules package used them at > > some point. > > > > Andrius, have you tried running all CZT tests to see what happens when > > you don't create new signatures? If some of the rules tests fail, then > > the dependency there means that we can't just switch these off in the > > typechecker. If not, then there is a chance these aren't used any more. > > > > If I do a grep -r for "getId" and "setId" in the rules package, there > > are a number of references, but most look to be just ensuring that > > they are passed around. > > > > If it was decided that IDs are no longer necessary (I know at one > > point there was talk of dropping them), then they should be removed > > from the ZName class all together, along with any reference to them in > > all of the other packages. Anything else would be too confusing. If > > they don't play an important role, then the memory saving may be worth > > removing them, but I'd wager the change would be tedious. > > > >> The massive space saving becomes quite obvious when you think about it. > >> If we have schema references, every RefExpr would duplicate the whole > >> schema definition when typechecked, hence creating a lot of new ZName > >> instances and consuming all this memory. > >> > > It wouldn't duplicate the whole schema definition -- it would only > > create a new Signature instance, and new ZName instances for all names > > inside the signature. The existing type instances are used. > > > > This alone will certainly account for a large chunk of memory in a > > state-machine, because every schema inclusion (including Xi/Delta) > > will create a new ZName for every name in that inclusion (two for > > Delta inclusions). > > > > Cheers, > > Tim > > > > ---------------------------------------------------------------------- > > ------ > > -- > > Precog is a next-generation analytics platform capable of advanced > > analytics on semi-structured data. The platform includes APIs for > > building apps and a phenomenal toolset for data science. Developers > > can use our toolset for easy data analysis & visualization. Get a free account! > > http://www2.precog.com/precogplatform/slashdotnewsletter > > _______________________________________________ > > CZT-Devel mailing list > > CZT...@li... > > https://lists.sourceforge.net/lists/listinfo/czt-devel > > > > > > ---------------------------------------------------------------------- > > -------- Precog is a next-generation analytics platform capable of > > advanced analytics on semi-structured data. The platform includes APIs > > for building apps and a phenomenal toolset for data science. > > Developers can use our toolset for easy data analysis & visualization. > > Get a free account! > > http://www2.precog.com/precogplatform/slashdotnewsletter > > _______________________________________________ > > CZT-Devel mailing list > > CZT...@li... > > https://lists.sourceforge.net/lists/listinfo/czt-devel > |
|
From: Leo F. <leo...@ne...> - 2013-04-15 12:24:52
|
Hi Tim / Anthony, @Tim do you remember the discussions when we moved from ZDEclName/RefName to ZName? When was it? There could lie some important clues for what to (not) do. @Anthony one case that is tricky is when you have name collusion as in S == [ x: \nat ]; T == [x : \num]; R == S \land T, where declared/unified types are different, here the two references ought to get / have the same ID. Other weird cases appear when you have schema quantification i.e. \forall T @ S, in which case the first is the declaring name? Andrius and I have been discussing potential solutions that take memory and functionality preservation into account, if with some need to change practices / code in various projects. Will look at this as soon as I free myself from an Isabelle proof that is taking longer than I wanted it to :-(… PS: Another interesting possibility is to look at what ProofPowerZ does, given it's efficient and solves similar problem? Best, Leo On 15 Apr 2013, at 11:22, Anthony Hall <an...@an...> wrote: > Tim > > Can I ask a question about ids? I had understood that the id was necessary > for distinguishing truly different instances of a name - for example x > declared globally and x within a schema. If that's true we can't presumably > drop ids altogether? Certainly I use them in my cross reference (as you may > remember, we had extensive discussions about this) and I've just been > looking at the "Go To Declaration" tool in the Eclipse IDE, which I think > uses the word + id as the unique identifier of a name. > > So I wonder whether we do need to keep the id, but not to create a new id > for every schema inclusion? If I declare x in S and then include S in T, I > don't think we should need a new id for the x in T, for example. Of course > if I declare x in S1 and S2 and then include both in T, there would have to > be an arbitrary choice of which id to use for references in T, but that's > really no different from the arbitrary choice of location that has to be > made at present if I ask where x in T is defined. > > Also, there the special id deltaxi, which presumably needs to be kept or > replaced with a different mechanism? > > At the moment it also seems to be true that there are many instances of a > ZName with the same id - that too could presumably be avoided? > > Please do say if I've misunderstood this! > > Thanks > > Anthony > > -----Original Message----- > From: Tim Miller [mailto:tm...@un...] > Sent: 15 April 2013 00:49 > To: CZT-Devel > Subject: Re: [CZT-Devel] Reducing memory usage: Signatures are the biggest > culprit? > > Hi everyone, > > You wrote: >> This lead me to thinking - do signatures really need to be duplicated >> everywhere? I imagine that the signature of schema A would be the same >> everywhere? Can we reuse the signature, or is it important to >> duplicate and assign new IDs to the name? >> > It was, at some point, very important to create new signatures, because > referenced schema names declare new variables into the name space of a > specification, and we can't have 2 variables with the same IDs if they refer > to different declarations. The IDs were a CZT-specific thing (i.e. > not part of the standard), and were used by other tools (the typechecker > does not require them because it keeps track of references in the type > environments itself). > > Now, I'm not sure whether they are still important in CZT. Other tools may > still rely on them. I'm pretty sure the rules package used them at some > point. > > Andrius, have you tried running all CZT tests to see what happens when you > don't create new signatures? If some of the rules tests fail, then the > dependency there means that we can't just switch these off in the > typechecker. If not, then there is a chance these aren't used any more. > > If I do a grep -r for "getId" and "setId" in the rules package, there are a > number of references, but most look to be just ensuring that they are passed > around. > > If it was decided that IDs are no longer necessary (I know at one point > there was talk of dropping them), then they should be removed from the ZName > class all together, along with any reference to them in all of the other > packages. Anything else would be too confusing. If they don't play an > important role, then the memory saving may be worth removing them, but I'd > wager the change would be tedious. > >> The massive space saving becomes quite obvious when you think about it. >> If we have schema references, every RefExpr would duplicate the whole >> schema definition when typechecked, hence creating a lot of new ZName >> instances and consuming all this memory. >> > It wouldn't duplicate the whole schema definition -- it would only create a > new Signature instance, and new ZName instances for all names inside the > signature. The existing type instances are used. > > This alone will certainly account for a large chunk of memory in a > state-machine, because every schema inclusion (including Xi/Delta) will > create a new ZName for every name in that inclusion (two for Delta > inclusions). > > Cheers, > Tim > > ---------------------------------------------------------------------------- > -- > Precog is a next-generation analytics platform capable of advanced analytics > on semi-structured data. The platform includes APIs for building apps and a > phenomenal toolset for data science. Developers can use our toolset for easy > data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel |
|
From: Anthony H. <an...@an...> - 2013-04-15 10:22:45
|
Tim Can I ask a question about ids? I had understood that the id was necessary for distinguishing truly different instances of a name - for example x declared globally and x within a schema. If that's true we can't presumably drop ids altogether? Certainly I use them in my cross reference (as you may remember, we had extensive discussions about this) and I've just been looking at the "Go To Declaration" tool in the Eclipse IDE, which I think uses the word + id as the unique identifier of a name. So I wonder whether we do need to keep the id, but not to create a new id for every schema inclusion? If I declare x in S and then include S in T, I don't think we should need a new id for the x in T, for example. Of course if I declare x in S1 and S2 and then include both in T, there would have to be an arbitrary choice of which id to use for references in T, but that's really no different from the arbitrary choice of location that has to be made at present if I ask where x in T is defined. Also, there the special id deltaxi, which presumably needs to be kept or replaced with a different mechanism? At the moment it also seems to be true that there are many instances of a ZName with the same id - that too could presumably be avoided? Please do say if I've misunderstood this! Thanks Anthony -----Original Message----- From: Tim Miller [mailto:tm...@un...] Sent: 15 April 2013 00:49 To: CZT-Devel Subject: Re: [CZT-Devel] Reducing memory usage: Signatures are the biggest culprit? Hi everyone, You wrote: > This lead me to thinking - do signatures really need to be duplicated > everywhere? I imagine that the signature of schema A would be the same > everywhere? Can we reuse the signature, or is it important to > duplicate and assign new IDs to the name? > It was, at some point, very important to create new signatures, because referenced schema names declare new variables into the name space of a specification, and we can't have 2 variables with the same IDs if they refer to different declarations. The IDs were a CZT-specific thing (i.e. not part of the standard), and were used by other tools (the typechecker does not require them because it keeps track of references in the type environments itself). Now, I'm not sure whether they are still important in CZT. Other tools may still rely on them. I'm pretty sure the rules package used them at some point. Andrius, have you tried running all CZT tests to see what happens when you don't create new signatures? If some of the rules tests fail, then the dependency there means that we can't just switch these off in the typechecker. If not, then there is a chance these aren't used any more. If I do a grep -r for "getId" and "setId" in the rules package, there are a number of references, but most look to be just ensuring that they are passed around. If it was decided that IDs are no longer necessary (I know at one point there was talk of dropping them), then they should be removed from the ZName class all together, along with any reference to them in all of the other packages. Anything else would be too confusing. If they don't play an important role, then the memory saving may be worth removing them, but I'd wager the change would be tedious. > The massive space saving becomes quite obvious when you think about it. > If we have schema references, every RefExpr would duplicate the whole > schema definition when typechecked, hence creating a lot of new ZName > instances and consuming all this memory. > It wouldn't duplicate the whole schema definition -- it would only create a new Signature instance, and new ZName instances for all names inside the signature. The existing type instances are used. This alone will certainly account for a large chunk of memory in a state-machine, because every schema inclusion (including Xi/Delta) will create a new ZName for every name in that inclusion (two for Delta inclusions). Cheers, Tim ---------------------------------------------------------------------------- -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ CZT-Devel mailing list CZT...@li... https://lists.sourceforge.net/lists/listinfo/czt-devel |
|
From: Tim M. <tm...@un...> - 2013-04-14 23:54:51
|
Oh, and another thought: the typechecker has an option "use name IDs". I don't remember what this did, but presumably there was some notation that name IDs were important for name equality for some packages (I think Petra added it for the Z rules package). We could change the typechecker such that if this was turned off, we simply didn't record name IDs, which would mean new signatures would not need to be created. Tim On 13/04/13 00:00, Andrius Velykis wrote: > Hi, > > Since I had a profiler on CZT running for catching some leftover > debugging code, I thought I would give a quick look into the CZT memory > usage as well. > > I have discovered that most of the large amount of ZNames that are > created are referenced from typechecker Signatures (via NameTypePairs). > This is the case because when creating type signatures during > typechecking, the Signatures are duplicated in a lot of places. > > A prominent example of this is in > net.sourceforge.czt.typechecker.z.ExprChecker:94 (method visitRefExpr). > This bit of code calculates the type of a RefExpr. If a reference is to > a Schema, it duplicates the Schema signature (assigns new IDs to all its > names) and then uses the new signature within the power type. > > As a quick test, I tried removing this duplication and instead reuse the > original schema signature (with original ZName ids): `Signature sig = > signature;` > > This single change reduced the memory consumption of typechecked > `spec.tex` by about 60%! > > This lead me to thinking - do signatures really need to be duplicated > everywhere? I imagine that the signature of schema A would be the same > everywhere? Can we reuse the signature, or is it important to duplicate > and assign new IDs to the name? > > The massive space saving becomes quite obvious when you think about it. > If we have schema references, every RefExpr would duplicate the whole > schema definition when typechecked, hence creating a lot of new ZName > instances and consuming all this memory. > > Leo advised that Tim would be the person to ask about the Signature > duplication in typechecker? Is it really necessary, or can we reuse the > objects? > > Best regards, > Andrius > > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > > > > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > |
|
From: Tim M. <tm...@un...> - 2013-04-14 23:49:44
|
Hi everyone, You wrote: > This lead me to thinking - do signatures really need to be duplicated > everywhere? I imagine that the signature of schema A would be the same > everywhere? Can we reuse the signature, or is it important to duplicate > and assign new IDs to the name? > It was, at some point, very important to create new signatures, because referenced schema names declare new variables into the name space of a specification, and we can't have 2 variables with the same IDs if they refer to different declarations. The IDs were a CZT-specific thing (i.e. not part of the standard), and were used by other tools (the typechecker does not require them because it keeps track of references in the type environments itself). Now, I'm not sure whether they are still important in CZT. Other tools may still rely on them. I'm pretty sure the rules package used them at some point. Andrius, have you tried running all CZT tests to see what happens when you don't create new signatures? If some of the rules tests fail, then the dependency there means that we can't just switch these off in the typechecker. If not, then there is a chance these aren't used any more. If I do a grep -r for "getId" and "setId" in the rules package, there are a number of references, but most look to be just ensuring that they are passed around. If it was decided that IDs are no longer necessary (I know at one point there was talk of dropping them), then they should be removed from the ZName class all together, along with any reference to them in all of the other packages. Anything else would be too confusing. If they don't play an important role, then the memory saving may be worth removing them, but I'd wager the change would be tedious. > The massive space saving becomes quite obvious when you think about it. > If we have schema references, every RefExpr would duplicate the whole > schema definition when typechecked, hence creating a lot of new ZName > instances and consuming all this memory. > It wouldn't duplicate the whole schema definition -- it would only create a new Signature instance, and new ZName instances for all names inside the signature. The existing type instances are used. This alone will certainly account for a large chunk of memory in a state-machine, because every schema inclusion (including Xi/Delta) will create a new ZName for every name in that inclusion (two for Delta inclusions). Cheers, Tim |
|
From: Andrius V. <and...@ne...> - 2013-04-14 12:03:38
|
Dear Anthony, On Sat, Apr 13, 2013 at 9:46 AM, Anthony Hall <an...@an...>wrote: > > I have a selfish follow up question. Assuming Tim can confirm that this, > or something like it, is acceptable then would you be able to do a bit of > work on this? It’s true that I had very diffidently volunteered to look at > this area, but it would be clearly much more effective and efficient for > you, who obviously know what you are doing, to look at it than for me to > spend a lot of time groping around and wasting your time asking dumb > questions. Of course I’d be extremely happy to help with any testing, > especially if you get to the point where typechecking large specifications > becomes feasible (at the moment it simply isn’t possible to typecheck the > whole of the iFACTS spec in CZT on any machine I’ve been able to try.) > Unfortunately, I cannot promise too much. In my current stage of PhD, I have quite a lot of pressing things to do there. I will check with Leo how we can approach this - but sometimes coding is the thing I do to relax, so.. :) First though, it would be good to know about mutability/ID uniqueness of Signatures and other typechecker artifacts. > **** > > ** ** > > Anyway, I’m really encouraged by this result and thank you so much for > doing this – I’m delighted (and impressed!)**** > > ** ** > > Anthony > Thanks, I appreciate your comments! :) Andrius > ** > |
|
From: Leo F. <leo...@ne...> - 2013-04-13 09:02:43
|
Hi Andrius, Brilliant! Another point of memory improvement. Anthony, the first round of memory reclaim (a few months / years ago) improve about 50-70% and they had to do with dangling references by the CUP parser as well as empty Ann lists (with 10 elements in memory) being created for every AST. The many names being around are now possible to trace (i.e. the extra code in ZNameImpl + debugging info to output that). --- i.e. in case you want to see how names proliferate. A long time ago Petra and I started a flyweight factory at Corejava but didn't go very far. It seems like this would be the way forward. @all another point of interest is the use of mutable references returned by various AST methods, which leads to potential memory leaks (i.e. references that would never be GCed). For instance, AST methods have "getXXX()" which returns a List<??> that can be modified and referenced from outside. If that reference persists, the AST will never be GCed. @Mark thanks for the pointer on Guava. I will try and have a look at this next week. Also, it's incredible to think CZT is 10 years old! I am remembering my first encounters with it through Jaza during my PhD :-) Best, Leo On 13 Apr 2013, at 09:46, Anthony Hall <an...@an...<mailto:an...@an...>> wrote: Dear Andrius This is brilliant! Since I had a profiler on CZT running for catching some leftover debugging code, I thought I would give a quick look into the CZT memory usage as well. I have discovered that most of the large amount of ZNames that are created are referenced from typechecker Signatures (via NameTypePairs). This is the case because when creating type signatures during typechecking, the Signatures are duplicated in a lot of places. A prominent example of this is in net.sourceforge.czt.typechecker.z.ExprChecker:94 (method visitRefExpr). This bit of code calculates the type of a RefExpr. If a reference is to a Schema, it duplicates the Schema signature (assigns new IDs to all its names) and then uses the new signature within the power type. As a quick test, I tried removing this duplication and instead reuse the original schema signature (with original ZName ids): `Signature sig = signature;` This single change reduced the memory consumption of typechecked `spec.tex` by about 60%! Excellent! This lead me to thinking - do signatures really need to be duplicated everywhere? I imagine that the signature of schema A would be the same everywhere? Can we reuse the signature, or is it important to duplicate and assign new IDs to the name? The massive space saving becomes quite obvious when you think about it. If we have schema references, every RefExpr would duplicate the whole schema definition when typechecked, hence creating a lot of new ZName instances and consuming all this memory. Leo advised that Tim would be the person to ask about the Signature duplication in typechecker? Is it really necessary, or can we reuse the objects? Andrius, this is exactly the sort of thing I hoped might be possible. I don’t know how much of the previous discussion you’re aware of, but at first sight it does look as if objects are being copied many, many times and the total number of objects created seems to be bigger than should be needed, not by a few percent, but by orders of magnitude. If Tim can confirm that these objects and others like them are indeed immutable, then it seems not only more efficient but also the Right Thing simply to copy the object reference. If there are a few more places you can find savings of this sort of percentage then the problem would be fixed. (Two more 60% and you’d have an order of magnitude already!) I have a selfish follow up question. Assuming Tim can confirm that this, or something like it, is acceptable then would you be able to do a bit of work on this? It’s true that I had very diffidently volunteered to look at this area, but it would be clearly much more effective and efficient for you, who obviously know what you are doing, to look at it than for me to spend a lot of time groping around and wasting your time asking dumb questions. Of course I’d be extremely happy to help with any testing, especially if you get to the point where typechecking large specifications becomes feasible (at the moment it simply isn’t possible to typecheck the whole of the iFACTS spec in CZT on any machine I’ve been able to try.) Anyway, I’m really encouraged by this result and thank you so much for doing this – I’m delighted (and impressed!) Anthony ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter_______________________________________________ CZT-Devel mailing list CZT...@li...<mailto:CZT...@li...> https://lists.sourceforge.net/lists/listinfo/czt-devel |
18 messages has been excluded from this view by a project administrator.
