Re: [Vala] State of the Vala union

2017-04-15 Thread Matthias Berndt
Hi Michael, There are bugs about these, https://bugzilla.gnome.org/show_bug.cgi?id=772209 and https://bugzilla.gnome.org/show_bug.cgi?id=694895 (I'm not sure about the delegate bug, it may or may not be in bugzilla – but I won't waste my time reporting bugs that nobody is going to fix anyway. Feel

Re: [Vala] State of the Vala union

2017-04-13 Thread Dr. Michael Lauer
Hi Matthias, > Well, apparently storing objects in a List is esoteric, > because the compiler will let obvious type errors pass: > > var l1 = new ArrayList(); > ArrayList l2 = l1; > l2.add(new Object()); > Foo f = l1[0]; // f has type Foo but points to an Object, no cast is needed. > > And a

Re: [Vala] State of the Vala union

2017-04-06 Thread Matthias Berndt
> Don't you have anything better to be doing with your time than to be > trolling the mailing list of a programming language that you don't want to > use? It's quite telling that you accuse me of trolling rather than addressing any of the actual issues I've raised. I've fixed several bugs in the

Re: [Vala] State of the Vala union

2017-04-06 Thread Michael Gratton
On 7 April 2017 8:16:32 AM "Matthias Berndt" wrote: Obviously all these examples are completely contrived, academic and serve no purpose other than showing off my 31337 comp!l0r h4xx0ring 5k!11z. Thanks for finally showing me the light about the One True Programming Language: Vala! Don't you

Re: [Vala] State of the Vala union

2017-04-06 Thread Matthias Berndt
> > Well, I suppose I have higher requirements than they have. From a > > production-ready > > compiler I would expect > > – no (or at best very obscure) type errors to get through > > – no compiler crashes > > – no broken code generated > > I don't think these are unreasonable criteria, yet valac

Re: [Vala] State of the Vala union

2017-04-05 Thread Ulink
>> they have been part of a 200K lines of code project. They must have thought >> it was >> production ready. We are SURE that it was and it IS production ready. We started the project approx. 2-3 years ago (vala 0.22 on Ubuntu 14.04 I think) and it is constantly growing while implementing new fe

Re: [Vala] State of the Vala union

2017-04-05 Thread Nor Jaidi Tuah
> Well, I suppose I have higher requirements than they have. From a > production-ready > compiler I would expect > – no (or at best very obscure) type errors to get through > – no compiler crashes > – no broken code generated Possibly you have eliminated every compiler :-) Nice day Nor Jaidi Tua

Re: [Vala] State of the Vala union

2017-04-05 Thread Matthias Berndt
Hi Al, thanks for responding! > I guess it depends on what you are producing. Some one has just stated on > this list > they have been part of a 200K lines of code project. They must have thought > it was > production ready. Well, I suppose I have higher requirements than they have. From a pro

Re: [Vala] State of the Vala union (was: Starting with Vala)

2017-04-04 Thread Al Thomas via vala-list
> From: Matthias Berndt > Sent: Tuesday, 4 April 2017, 23:43 > Subject: [Vala] State of the Vala union (was: Starting with Vala) > Vala suffers from a number of problems: > – the compiler is basically not production ready. I dug into the source code> >just a bit and

[Vala] State of the Vala union (was: Starting with Vala)

2017-04-04 Thread Matthias Berndt
TL;DR – The design of the language is outdated – The implementation is buggy and not production ready – There's generally little momentum (tools, mindshare etc.) – It won't be fixed because there are almost no maintainers and none will join at this point Frankly I would recommend you to use so