Poly/ML

polyml@lists.polyml.org

2 participants
711 discussions

InternalError: Equality for function raised
by rda＠lemma-one.com 14 Sep '09

14 Sep '09

David, David, Using recent sources, the following caused an internal error as described in the comment. The problem persists when I update to the very latest (rev. 866). fun present (eq : ('a * 'a) -> bool) (x: 'a) : 'a list -> bool = ( let fun test (h :: t) = eq(x,h) orelse test t | test [] = false in test end ); fun insert (eq:'a * 'a -> bool) (lst : 'a list) (what : 'a) = ( if present eq what lst then lst else (what :: lst) ); (* following cut down extract from a test script fails with: Exception- InternalError: Equality for function raised while compiling *) [ (insert (op =) []), (insert (op =) [1]) ]; Regards, Rob.

2 1

Re: [Building Poly/ML on MacOS X 10.6]
by rda＠lemma-one.com 09 Sep '09

09 Sep '09

David, Yes, it works with --build=i386-apple-darwin. Regards, Rob. On Wednesday 09 Sep 2009 5:55 pm, you wrote: > Rob, > Try with > ./configure --build=i386-apple-darwin CFLAGS='-arch i386 -O3' \ > CXXFLAGS='-arch i386 -O3' CCASFLAGS='-arch i386' > > With the change to config.guess the configure script is now picking up > the default architecture as x86_64 rather than i386 which was what it > was reporting before. Previously you had to override it in 64-bit mode; > now you have to override it in 32-bit mode. > > It would be good to have just a single option to select whether to build > 32-bit or 64-bit on machines that support that. I can't see a good way > to do it at the moment. > > Regards, > David > > Rob Arthan wrote: > > David, > > > > I have update to revision 864 and don't seem to be able to force a 32-bit > > build using the following command any more: > > > > ./configure CFLAGS='-arch i386 -O3' CXXFLAGS='-arch i386 -O3' > > CCASFLAGS='-arch i386' > > > > I have attached the config.log and make output. > > > > Regards, > > > > Rob. > > > > On Wednesday 09 Sep 2009 2:58 pm, David Matthews wrote: > >> Rob, > >> Can I take it that the current SVN builds on Mac OS 10.6 without any > >> extra options, although your Makefiles will have to add the -segprot > >> option? I may need to ask you test it again if the official > >> config.guess is updated to include support for 10.6. > >> > >> Eventually I'd like to remove the need for -segprot but that will > >> require making the code segment at least completely read-only. That in > >> turn requires changes to profiling, data sharing and exporting all of > >> which write to code objects. > >> > >> Regards, > >> David > >> > >> rda(a)lemma-one.com wrote: > >>>> Rob Arthan wrote: > >>>>> I wrote: > >>>>>> I am completely baffled. I thought I hada solved all my problems on > >>>>>> MacOS X > >>>>>> 10.6 and was just tidying up, > >> > >> _______________________________________________ > >> polyml mailing list > >> polyml(a)inf.ed.ac.uk > >> http://lists.inf.ed.ac.uk/mailman/listinfo/polyml

1 0

[Fwd: Re: [polyml] Building Poly/ML on MacOS X 10.6]
by rda＠lemma-one.com 08 Sep '09

08 Sep '09

David, On 7 Sep 2009, at 15:15, David Matthews wrote: Rob, ... >> It may be possible to force 32-bit mode with >> ./configure CFLAGS='-arch i386 -O3' CXXFLAGS='-arch i386 -O3' \ >> CCASFLAGS='-arch i386' > Did you try with the CXXFLAGS option as well? From what I can tell CFLAGS is only used in C > programs not in the C++ parts such as x86_dep.cpp. It does work when I do set all three of CFLAGS CXXFLAGS and CCASFLAGS. Yet again I need to specify -arch i386 in my make files when I link Poly/ML programs. Is there any reason for or against compiling Poly/ML for the 32 bit architecture? [Aside: if I had known about these compiler options 3 days ago, the ProofPower GUI program xpp would probably still be full of code that only works on 32 bit implementations of X/Motif!] One thing that won't hurt me at the moment, but may affect other users is that the configure script is not finding the X Windows installation that comes with MacOS X. As far as I can see this is just because the test it uses needs to specify -L/usr/X11R6/lib. Regards, Rob.

3 3

Building Poly/ML on MacOS X 10.6
by rda＠lemma-one.com 07 Sep '09

07 Sep '09

My first attempt to compile Poly/ML 5.2.1 on Snow Leopard (= MacOS X 10.6) resulted in an error due to a cast of a pointer to an int in libpolyml/x86_dep.cpp. There is a fix for this in the latest source, but the build then falls over as follows: ... g++ -DHAVE_CONFIG_H -I. -I.. -DMACOSX -Wall -O3 -MT x86_dep.lo -MD -MP -MF .deps/x86_dep.Tpo -c x86_dep.cpp -fno-common -DPIC -o .libs/x86_dep.o /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:1063:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:1774:Incorrect register `%rsi' used with `l' suffix /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:1968:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:1973:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:2097:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:2129:Incorrect register `%rsi' used with `l' suffix /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:2416:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4660:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4666:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4672:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4696:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4702:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4738:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4759:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4777:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4780:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4783:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4789:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4792:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4795:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4798:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4801:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4804:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4807:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4819:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4822:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4891:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4894:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4897:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4900:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4903:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4906:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4909:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4912:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4915:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4924:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4927:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4936:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4939:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4978:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4981:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4984:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4987:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4990:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4992:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4994:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4996:suffix or operands invalid for `pop' /var/folders/Ih/IhQgyfokGpO8Wx1qsxaKZ++++TI/-Tmp-//ccWgMIs0.s:4998:suffix or operands invalid for `pop' make[2]: *** [x86_dep.lo] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Any suggestions gratefully received. Regards, Rob.

3 5

Re: Poly/ML does not build under Snow Leopard
by David.Matthews＠prolingua.co.uk 07 Sep '09

07 Sep '09

Peter, Are you subscribed to the Poly/ML mailing list? Rob Arthan has also been asking about this and it makes sense that everyone is aware of the various issues. I'm copying this to the list as well. Rob also found that ./configure --build=x86_64-darwin LDFLAGS='-segprot POLY rwx rwx' worked. I'm surprised that "make cvs" didn't appear to do anything but actually you don't need it in this case. Did you do a "make distclean" before the configure? It would appear that the Mac OS X linker will require the LDFLAGS="-segprot POLY rwx rwx' option whenever an executable file is built using an exported Poly object file. I don't know how to do this with HOL; perhaps someone on the list will be able to help. I'll add it to the link step of Poly/ML but that won't help with Isabelle. Regards, David Peter Vincent Homeier wrote: > Dear David, > > I tried the same thing on the developer (svn) version. I downloaded a > clean new copy, and tried > > ./configure --build=x86_64-darwin LDFLAGS='-segprot POLY rwx rwx' > make > make cvs > make > sudo make install > > and this all seemed to work. (Note that the "make cvs" seemed to have > no effect.) However, when I then tried to build HOL4 (a theorem > prover that built before with Poly/ML) I found that although I could > build HOL4's lexer, when I tried to run this lexer to build the parser > I got > > Bus error > > I could go back and try for the 32-bit versions as you suggested > earlier, although I really would like to build the 64-bit version, > given that much of the point of Snow Leopard is to be natively 64-bit > as much as possible. > > What would you suggest? > > Cheers, > Peter

1 0

Poly/ML on Windows (MinGW/MSYS port)
by gdr＠integrable-solutions.net 06 Sep '09

06 Sep '09

Hi David, I tried to build Poly/ML on Windows using the MSYS/MinGW toolchains, but was unsuccessful The build failed with: g++ -DHAVE_CONFIG_H -I. -I.. -I../../../polyml.svn/polyml/libpolyml -DWINDOWS_P C -Wall -O3 -mthreads -MT mpoly.lo -MD -MP -MF .deps/mpoly.Tpo -c ../../../polym l.svn/polyml/libpolyml/mpoly.cpp -DDLL_EXPORT -DPIC -o .libs/mpoly.o ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:24:23: error: winconfig.h: No suc h file or directory In file included from ../../../polyml.svn/polyml/libpolyml/mpoly.h:26, from ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:60: ../../../polyml.svn/polyml/libpolyml/../polyexports.h:78: warning: 'PolyWinMain' initialized and declared 'extern' ../../../polyml.svn/polyml/libpolyml/../polyexports.h:78: error: 'HINSTANCE' was not declared in this scope ../../../polyml.svn/polyml/libpolyml/../polyexports.h:78: error: 'HINSTANCE' was not declared in this scope ../../../polyml.svn/polyml/libpolyml/../polyexports.h:79: error: 'LPTSTR' was no t declared in this scope ../../../polyml.svn/polyml/libpolyml/../polyexports.h:79: error: expected primar y-expression before 'int' ../../../polyml.svn/polyml/libpolyml/../polyexports.h:79: error: expected primar y-expression before '*' token ../../../polyml.svn/polyml/libpolyml/../polyexports.h:79: error: 'exports' was n ot declared in this scope ../../../polyml.svn/polyml/libpolyml/../polyexports.h:79: error: initializer exp ression list treated as compound expression In file included from ../../../polyml.svn/polyml/libpolyml/pexport.h:27, from ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:65: ../../../polyml.svn/polyml/libpolyml/exporter.h:58: error: ISO C++ forbids decla ration of 'FILE' with no type ../../../polyml.svn/polyml/libpolyml/exporter.h:58: error: expected ';' before ' *' token ../../../polyml.svn/polyml/libpolyml/mpoly.cpp: In function 'int polymain(int, c har**, exportDescription*)': ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:143: error: 'printf' was not decl ared in this scope ../../../polyml.svn/polyml/libpolyml/mpoly.cpp: In function 'void Usage(const ch ar*)': ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:233: error: 'printf' was not decl ared in this scope ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:236: error: 'printf' was not decl ared in this scope ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:238: error: 'stdout' was not decl ared in this scope ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:238: error: 'fflush' was not decl ared in this scope ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:243: error: '_T' was not declared in this scope ../../../polyml.svn/polyml/libpolyml/mpoly.cpp: In function 'char* RTSArgHelp()' : ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:258: error: 'sprintf' was not dec lared in this scope ../../../polyml.svn/polyml/libpolyml/mpoly.cpp:261: warning: statement has no ef fect make[2]: *** [mpoly.lo] Error 1 make[2]: Leaving directory `/home/gdr/Desktop/sandbox/build/polyml/libpolyml' This is an out-of-source build, meaning that I keep the build directory separate from the vanilla Poly/ML source tree. I had a quick look for winconfig.h and was under the impression that it was supposed to replace config.h (which is generated anyway at configure time). For some reason, it is not being seen by the preprocessor. Why keep winconfig.h when config.h (that truly reflects the host/build machine characteristics) is generated at configure time? I also noticed that pthread is being check for even on Windows. I believe that is not good. On Windows, one should just check for Windows thread support. The reason is that configure may report that pthread.h exists without the full semantics support needed by Poly/ML (which is the case on my machine, Windows XP SP3). A second point is that in such circumstances, checking for HAVE_PTHREAD_H, then for WIN32 is not good. The test should be reversed. One should first check for WIN32, then HAVE_PTHREAD_H. Another observation: __darwin_mcontext32 should be checked only on darwin platforms. Best, -- Gaby

2 6

Detecting unreferenced identifiers
by rda＠lemma-one.com 01 Sep '09

01 Sep '09

David, On 31 Aug 2009, at 18:26, you wrote: >> Rob Arthan wrote: >> > I have a problem building ProofPower with the latest Poly/ML. The >> build >> > goes into a loop at a point where it opens a certain structure. >> This >> > will be the first time Poly/ML has had to pretty-print a value of >> the >> > type THM that represents theorems. This type has a circularity >> passing >> > through a ref and a certain dictionary data type. I have attached >> a very >> > cutdown version of the failing code. The cutdown version behaves >> > slightly differently in that I see some never-ending output, >> while the >> > ProofPower build just goes into a silent busy hang. >> > >> > The dictionary type OE_DICT that causes the problem is an amalgam >> of two >> > simpler dictionary data types S_DICT (simple dictionaries using an >> > association list) and E_DICT (efficient dictionaries using a hash >> key >> > and a binary tree). Somewhat oddly the problem doesn't happen if I >> > replace OE_DICT with either S_DICT or E_DICT even though the >> > representation type for OE_DICT is just S_DICT * E_DICT. >> >> I'm not sure what's happening in detail in your example but there has >> been a significant change in the way printing works in the latest >> version. A printing function (and an equality function, if >> appropriate) >> is now compiled for each type as it is created. This means that >> printing and type-specific equality functions are available in a >> wider >> range of cases than they used to be, particularly in functors. >> >> Previously, the code checked whether there was circularity and just >> printed "..." when it detected it. That's not really possible with >> the >> current code so it relies on the print depth (PolyML.print_depth) to >> stop infinite looping. Setting print_depth to 10 in your example >> produces much more sensible output. >> That works. Even better for me, if I change the order of compilation so that my user-defined pretty-printer for the circular type is installed first, that works too. >> The only simple solution I can suggest is to set the default for the >> printer depth to something much smaller, perhaps 10. There's >> probably >> no reason for the current, essentially unconstrained, print depth. >> >> > I also noted in passing that types declared as abstypes are now >> equality >> > types. Was this a conscious attempt to implement one of the >> Successor ML >> > proposals? >> >> No, it was something I noticed while working on the printing and >> equality code. An early draft of Standard ML explicitly said that >> abstypes were not equality types outside the "with...end" block and >> that's what Poly/ML implemented. When I looked again recently I >> couldn't actually see that anywhere in either the ML90 or ML97 >> definitions and it seems to conflict with the way equality is >> handled in >> the semantics. For that reason I took out the code which switched >> off >> equality. >> Section 4.9 of the ML97 definitions describes something called Abs(TE, VE) that I think is changing the types declared between "abstype" and "with" into non-equality types and getting rid of their constructors. I think the conflict you mention is why there is a Successor ML proposal to do what you have done. Regards, Rob.

3 2

Pretty-printer seems to loop
by rda＠lemma-one.com 31 Aug '09

31 Aug '09

David, I have a problem building ProofPower with the latest Poly/ML. The build goes into a loop at a point where it opens a certain structure. This will be the first time Poly/ML has had to pretty-print a value of the type THM that represents theorems. This type has a circularity passing through a ref and a certain dictionary data type. I have attached a very cutdown version of the failing code. The cutdown version behaves slightly differently in that I see some never-ending output, while the ProofPower build just goes into a silent busy hang. The dictionary type OE_DICT that causes the problem is an amalgam of two simpler dictionary data types S_DICT (simple dictionaries using an association list) and E_DICT (efficient dictionaries using a hash key and a binary tree). Somewhat oddly the problem doesn't happen if I replace OE_DICT with either S_DICT or E_DICT even though the representation type for OE_DICT is just S_DICT * E_DICT. If it is just that the latest source in SVN is just not in a stable state, let me know and I will give up until further notice. I also noted in passing that types declared as abstypes are now equality types. Was this a conscious attempt to implement one of the Successor ML proposals? Regards, Rob.

2 1

Detecting unreferenced identifiers
by David.Matthews＠prolingua.co.uk 31 Aug '09

31 Aug '09

I fixed a bug recently [831] where I'd reorganised some code and the wrong identifier was being picked up. It would have been immediately apparent if the compiler had detected that an identifier was unreferenced so I've now added that check. In the current SVN version identifier checking is off by default but can be turned on with PolyML.Compiler.reportUnreferencedIds := true; The compiler will then report identifiers that are unreferenced as a warning. Currently, this applies only to value identifiers, excluding value constructors. An identifier is referenced if it used anywhere, which includes a recursive use, exported as a top-level value or used in the result of a structure or functor. When used in a structure or functor an identifier must be mentioned in the signature to be considered as referenced. Reference information isn't currently available through the IDE protocol but that can be added. Enabling unreferenced identifier checking on the compiler itself showed up a minor bug so it's already proved useful. David

2 3

Re: PolyML application news
by ldixon＠inf.ed.ac.uk 27 Aug '09

27 Aug '09

Hello, Unfortunately, as some people suspected, the PolyML application was deemed to be out of scope and so it was not taken forward for funding. However, I did get positive feedback and we were recommended to resubmit the application to another funding stream. So I am now thinking about adapting the previous proposal, adding a bit more of a research angle. I had a few discussions already, e.g. adapting the idea of equality type to a more general notion of type classes (from Larry, I think). Do email me your ML-grumbles and thoughts: I'll be bouncing various ideas around at the ML-workshop in the forthcoming ICFP conference. The old (so far unfunded) application can be found here: http://dream.inf.ed.ac.uk/projects/polyml/appl.pdf best, lucas Lucas Dixon wrote: > Hi, > > Quickly following the second draft, I've done a good deal more polishing > up of the proposal, and this is probably close to the final version. > > Thanks very much for all the feedback! > > Many thanks, > lucas

1 0

← Newer
1
...
49
50
51
52
53
54
55
...
72
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Poly/ML