New build is posted and online docs updated.
A couple of really nice enhancements to make Fantom constructors more flexible:
Notes for these changes related to existing code bases:
For more detailed discussed see ticket #1776.
There have been significant enhancements to the Java FFI subsystem:
For more detailed discussed see ticket #1780.
Quite a bit of work was done back in December to compilerDoc. Most all the data structures were refactored to be immutable. This allows this code to be more easily used with actors and caching engines. On http://skyfoundry.com/ we are now running online documentation and the search engine straight from a fanr repository. That work was the final pieces we need to upgrade this site to the new sidewalk stack. So hopefully we'll be doing that in the next month or two.
Per discussion topic #1743, I have changed the "d" suffix on decimals to be required. This was actually a much needed change and I was surprised how many places in my own code I had stuff screwed up. So now all float/decimal literals will be explicitly readable in code.
The fant tester can now accept a script file in addition to pods, types, and slots. This is a useful little feature if you want to try out stuff quickly or want to post test scripts on the forum.
I noticed the compiler wasn't checking type visibility in is, isnot, as, and casting expressions. If you had expressions using an internal type in another pod they will now be compiler errors.
There is a bit of prototype code in this build to setup a PathEnv from your directory structure instead of using environment variables. The runtime will look in your current directory upwards to see if it finds a directory with a "fan.props" file. If it does that is considered your working directory. The "fan.props" file can define intermediate paths using "path" key. The thinking is that this model would make Fantom paths work more like Mercurial where your current "project setup" is based solely on your current working directory.
This is just a prototype and in no way official. We are going to work with it for a few months and see what we think. Its one baby step on the need to rethink launchers, configuration options, and complex multi-project Fantom development environments. But you are welcome to start using it and provide your feedback.
Build 1.0.62 (24 Feb 2012)
Login or Signup to reply.