Re: newbie, Spark 2014 or Ada 2012

[Paul Rubin <no.email@nospam.invalid>]

Björn Lundin <b.f.lundin@gmail.com> writes:
> But - I often fall into the IndentationException trap...
> or find that I did not declare a variable...
> I know how to resolve the errors,
> but it does not come as natural as Ada compile errors do.
> I find it more fragile. Or I am to bad at testing.

Yeah, it's a different style, you have to write just a small bit of
code, then test it, then write the next bit, etc.  But you can bang out
working code very fast that way, especially with an interactive
interpreter shell.  Python is more fragile in that refactoring breaks
stuff and the way around that is with comprehensive test automation that
takes considerable determination to maintain.  It's IMHO best for small
to medium sized tasks that aren't complex enough to need Ada's
organizational machinery, like up to a few thousand LOC.  And 200 LOC of
Python can often do as much stuff as 1 KLOC of Ada (Python is a lot
slower though, since it's interpreted).  For really big programs, you
need as much maintenance infrastructure that you might as well use a
typed language.  I've been using Haskell some, and have been wanting to
try the ML family.

This article is really good:

https://cdsmith.wordpress.com/2011/01/09/an-old-article-i-wrote/

it's mostly about the typed-vs-untyped debate, but gives a useful
picture of debugging and untyped languages.  

>>> http://sourceforge.net/p/avr-ada/wiki/Home/
>> How has that been going for you? 
> I guess it depends on your standard.  For me, it was my first try into
> embedded, so I got blinky going, ...

Nice, I will give it a try sometime.