From: JP M. <jpm...@gm...> - 2011-10-09 17:46:35
|
As announced on my blog, there is a branch of eclipseFP called "buildwrapper" that doesn't use scion anymore. If people want to test before it's merged into the main branch, you need to install the buildwrapper Haskell executable, then configure EclipseFP to use the installed executable. The pluses of the new versions: - supports component references inside a project (so you can have an executable referencing the library directly) - uses Cabal executable to build the project so you get the same errors and warnings than building through the command line - no resident server, so no huge memory usage and easier synchronization of calls The minuses: - since the calls to the GHC API start a new session each time, "thingAtPoint" is slower than before Please let me know what you think. -- JP Moresmau http://jpmoresmau.blogspot.com/ |
From: Alejandro S. M. <tr...@gm...> - 2011-10-09 19:11:56
|
It sound great to me. Everything that makes EclipseFP better (and performance is clearly a plus) is good. There is one thing that would have to change if buildwrapper is used: now, for Alex, Happy and UUAGC files, EclipseFP is the one responsible for preprocessing them to .hs files. However, if using Cabal to build, those files are preprocessed automatically, so we would get warnings and error through that path. Also, it would be nice to have some way to get an outline of the entire project + project dependencies (I mean, those not coming from installed packages, but from other projects in the workspace). That would allow to greatly enhace autocompletion. 2011/10/9 JP Moresmau <jpm...@gm...> > As announced on my blog, there is a branch of eclipseFP called > "buildwrapper" that doesn't use scion anymore. If people want to test > before it's merged into the main branch, you need to install the > buildwrapper Haskell executable, then configure EclipseFP to use the > installed executable. > The pluses of the new versions: > - supports component references inside a project (so you can have an > executable referencing the library directly) > - uses Cabal executable to build the project so you get the same > errors and warnings than building through the command line > - no resident server, so no huge memory usage and easier > synchronization of calls > The minuses: > - since the calls to the GHC API start a new session each time, > "thingAtPoint" is slower than before > > Please let me know what you think. > > -- > JP Moresmau > http://jpmoresmau.blogspot.com/ > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > _______________________________________________ > eclipsefp-develop mailing list > ecl...@li... > https://lists.sourceforge.net/lists/listinfo/eclipsefp-develop > |