Additionally, how does one duplicate your development system ? An experienced developer will probably be able to figure this out even if they had no prior experience with Ada's toolset. But an inexperienced developer is going to run into hurdle, after hurdle, until they become frustrated, and just not bother with it all. An experienced developer like me however who knows how to avoid most of these hurdles, will eventually run into the language barrier I spoke of above ( if no prior Ada experience ), and they're very likely to attempt to learn how to duplicate something similar to what you've done in code, from scratch. My own reasoning here is that if I have to learn the language already anyhow, why bother attempting to understand someone elses code, when I can write my own . . .
On Tue, Apr 5, 2016 at 12:34 PM, William Hermans <[email protected]> wrote: > So here is a suggestion / comment. Perhaps write a short blog, or > additional readme.md that comments on which files are for what purpose( a > few are hard to tell ). Then a blog perhaps for walking through one of the > source files from a beginners point of view. > > Here is why. Myself, I'm a very experienced programmer in several > languages, but I've never picked up Ada, and have been meaning to. A very > thorough explanation on one of the source files, would answer a lot of > questions for me personally. > > Anyway, I realize it is not your "job" to necessarily teach Aa from a > beginners standpoint. But I do think this would go a long ways to help some > experienced developers understand why using Ada in an embedded context > could be beneficial. Me, I understand the "selling points" of Ada. At least > a few, but what has been holding me back is reading / understanding a > language that is very different from C. Ada is actually one of those > languages, at least for me personally, where I can not necessarily just > start reading through the code, and understand what's going on. > > For instance, it seems like you're wrapping the sysfs object for each > separate peripheral object, but I can not tell exactly how. discussing the > finer points of the code, such as that would help me( and hopefully others > ) understand the code better. But again, is this your "job" ? No it's not, > but I'd appreciate it, and I'm sure others would as well. > > > > On Tue, Apr 5, 2016 at 11:03 AM, <[email protected]> wrote: > >> I have been doing some Ada programming on the BeagleBone Black using gnat >> and gnat-gps from the Debian repository. One of the things that I've been >> doing is developing a library of routines to access various bits of the >> board's I/O. The source is available at >> https://github.com/BrentSeidel/BBS-BBB-Ada.git and currently covers the >> LEDs, GPIO, I2C, PWM, and Analog Inputs. I don't claim that this is >> anywhere near production ready, but it might provide some useful examples >> or information, even if you're not using Ada. >> >> Comments, questions, suggestions are welcome. >> >> Brent >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
