I posted a couple of blog posts last week that did not get syndicated well via rss. Mostly due to not modifing the publishing date when i posted them, so if you missed them and they sound interesting heres the links
PHP Grammer added to leds, and how to build leds Note: dsource.org is currently down (14nov2006 -server upgrade in progress.), so the compd patches have not been commited Note: I've recently added quite a bit more php autocomletion, variable type guesing and inline help (displaying method docblock info when you autocomplete a method call) - again, this is waiting for dsource.org to comeback
D does not have nice mailing lists like PHP, they have a news server, and web based forums. Since I like my Inbox overflowing with news, here's a little hack to retrieve the news, and post it to yourself... - great reading if you are interested in compiler design or just want to pick up D by listening. http://www.akbkhome.com/svn/akpear/NNTPtoMail/NNTPtoMail.php
Interestingly there was a post this week by someone deciding to use D rather than PHP for a project. This is something that I have been tending towards, although as the example above shows, PHP still has many advantages, with projects like PEAR making tasks very simple as the libraries are easy to use, readily available. But as time goes by, that situation for D is obviously improving. Oddly enough I can see a day (although not within 6-9 months) when writing a website in D would be preferable to PHP. (ohh the blasphamy)
davfs2
Yesterday I continued looking at davfs2 , as this old postsubversion and davfs described. i depend on my subversion servers being mounted using davfs2. and since reinstalling debian on my new desktop, i noticed that davfs2 was packaged and available.
The new maintained davfs2, has a number of significant improvements, like fusefs support (allowing more than 5 davfs2 mounts), secret file (for password storage ) and caching. Unfortunately the last of these makes the new davfs2 unusable for svn mounted writable repos.
There are two dealbreaker bugs, which may be related. The first is caused by the fact that when you save a file, it writes the file locally first, then sends the file to the server in the background. This leads to a problem, that the true file mtime can not be correctly determined. (as the file has not actually been written to the subversion server when you saved it.) Leading to text editors thinking that the file has been modified on the server shortly after saving.
The second problem, intermittent write failue, appears to be fixed by the patch i posted to the davfs2 bug tracker, but does it by breaking the davfs internal logic .
So after spending far too long trying to fix it, i gave up and reverted back to v0.2, which works reliaby ,albeit slower.
Previous Topic
