Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Saturday, 28 December 2013 at 03:13:10 UTC, Casper Færgemand wrote: On Saturday, 28 December 2013 at 02:02:44 UTC, Alexander Bothe wrote: May I have some code samples? Writing 'SysTime' may happen everywhere - as well as 'a similar null-pointer' .. I have no magic glass bowl to look in, you know. ;-) I can't reproduce it in a new file. I can, however, go to any line in my existing project, press a key on the keyboard, and the code completion window crashes with a null pointer. Not sure what you want aside from that. I don't see why it would have anything to do with what code I've written. My only import outside Phobos is Pegged. D_Parser.Dom.DefaultDepthFirstVisitor.Visit(ArrayLiteralExpression x) Just another hint: I have the same issue, on 4.2.2 under OSX with 0.5.5.6/0.5.5.5. Reverted to 0.5.5.4 and the issue is still present, BUT only in the log (--no-redirect) and without the modal error dialog. I agree with Casper, it happens practically in every module you wrote, when you write incomplete code. I think you already know this, Alex, but I agree with ilya and Casper: MonoD is by far the best environment to code with under OSX/linux, but we definitely need more stability. Right now, I'm scouting for my colleague every new combination of Xamarin and Mono-D updates (ok, update to 4.2.2, it works, hold on with 0.5.5.6, it's broken!, and so on..) /Paolo
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Saturday, 28 December 2013 at 03:13:10 UTC, Casper Færgemand wrote: On Saturday, 28 December 2013 at 02:02:44 UTC, Alexander Bothe wrote: May I have some code samples? Writing 'SysTime' may happen everywhere - as well as 'a similar null-pointer' .. I have no magic glass bowl to look in, you know. ;-) I can't reproduce it in a new file. I can, however, go to any line in my existing project, press a key on the keyboard, and the code completion window crashes with a null pointer. Not sure what you want aside from that. I don't see why it would have anything to do with what code I've written. My only import outside Phobos is Pegged. D_Parser.Dom.DefaultDepthFirstVisitor.Visit(ArrayLiteralExpression x) Okay, I think that I've fixed it now although I still can't reproduce this exception in any wise - neither in my trivial test programs nor in std.datetime (just noticed that halfway fluid editing with all code completion and stuff is possible there either - despite 35k LOC) How am I supposed to test things I've never seen before?
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Saturday, 28 December 2013 at 06:55:21 UTC, ilya-stromberg wrote: When I used `ppa:keks9n/monodevelop-latest` repro, the MonoDevelop updated every day. So, it was alpha version. BTW, I had a lot of problems with it, new `ppa:ermshiperete/monodevelop` looks much better. Although I'm rather interested in providing a good platform for everyone I can't keep an eye for everything. As I've also left Ubuntu I honestly don't care about this apt-get magic anymore. I'm providing my own MD distro which is working with most setups and that's it. If someone's willed to use other versions, I can't care about each platform's specific release strategies. I repeat, please write supported MonoDevelop version at the download page. You have too many opportunities for Ubuntu: we have 3 different repros and nobody knows the correct one. BTW, `ppa:ermshiperete/monodevelop` contains pre-installed Mono-D, so it looks like the maintainer wants to support correct MonoDevelop version for Mono-D. If I write 4.2.2 somewhere at the bottom, it can be the case that there are different releases called 4.2.2 - featuring broken API and other things. I've been following that 'development' over the last couple of years - and it was deadly annoying to have broken API and nonsense exceptions after each rebuild. Yes, this might be the issue with Mono-D as well, but as soon as I'm introducing new features it's very often the case that internals change - and therewith new regressions/throw-cases rise. I'm also no test engineer who is willed to build GUI test infrastructures - perhaps I just could code more carefully, but well, even then unexpected situations will(!, I've had these situations often enough now) occur. Additional request: please use more intuitive version number, see http://semver.org/ because current version scheme doesn't provide any additional information. Please use: 1) 1-st digit if you need to upgrade the MonoDevelop version with incompatible API changes 2) 2-nd digit if you have new features, code refactoring or any other big code change 3) 3-d digit if you have only bug fixes It can help a lot. For example, 2 last Mono-D versions should have 0.5.6.0 and 0.5.6.1 numbers. Same stuff here: I'm using these numbers just to indicate an update for MD's update manager. If I could, I wouldn't even use those - as with all the continous integration there can be API changes everytime - either via Refactoring or via new feature introduction or even via bug fixing. I probably would have released Mono-D v456 now if I followed these strict rules. Or you have a second setup which is just dedicated for some final user verification. Or you just come back in a year and check it out again - if Mono-D still exists then, who knows.
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Saturday, 28 December 2013 at 06:55:21 UTC, ilya-stromberg wrote: Additional request: please use more intuitive version number, see http://semver.org/ because current version scheme doesn't provide any additional information. Please use: 1) 1-st digit if you need to upgrade the MonoDevelop version with incompatible API changes 2) 2-nd digit if you have new features, code refactoring or any other big code change 3) 3-d digit if you have only bug fixes It can help a lot. For example, 2 last Mono-D versions should have 0.5.6.0 and 0.5.6.1 numbers. Anyway, thank you for the hint. I think I'll push a new major version as soon as there's a new MD version that features breaking API - although it must feel strange to have so ridiculously high version numbers (see Chrome/FF and others). Numbers greater than 9 should be okay as well - so I'll have versions like 22.30.4 then :-) Cheers, Alex
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
I updated the language bindings from 0.5.5.6 to 0.5.5.7. While past experience tells me anything I say will only serve to make a fool of myself, I shall accept my fate and say that so far I have not been able to reproduce the null pointer exception. And by that I mean I am able to hit the keyboard more than once without having to hit the escape key to close the informative popup.
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Saturday, 28 December 2013 at 17:16:29 UTC, Casper Færgemand wrote: I updated the language bindings from 0.5.5.6 to 0.5.5.7. While past experience tells me anything I say will only serve to make a fool of myself, I shall accept my fate and say that so far I have not been able to reproduce the null pointer exception. And by that I mean I am able to hit the keyboard more than once without having to hit the escape key to close the informative popup. Great. Well then, time for refactoring tooltips and probably get some code highlighting into them + try to examine DDoc info! :-)
Re: Mobile App STACK4 with a D backend
On Friday, 27 December 2013 at 16:38:16 UTC, Martin Krejcirik wrote: On 27.12.2013 12:33, extrawurst wrote: Does this maybe look like the problem you are having ? http://forum.xda-developers.com/showthread.php?t=2580084 Yes, just blank screen and nothing happens. Well yeah that was alreday clear... i meant the answer someone posted there: Just go to settings-apps and transfer the game from internal onto your phone memory. It's a common issue Does this solve the problem ?
