----------------------------------------------------------------------------------
@MSGID: 1@dont-email.me> 9dc0972d
@REPLY: 1@dont-email.me> b3132719
@REPLYADDR Kevin Chadwick
<kc-usenet@chadwicks.me.uk>
@REPLYTO 2:5075/128 Kevin Chadwick
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@RFC-References: 1@dont-email.me>
1@dont-email.me>
@TZUTC: -0000
@PID: PhoNews/3.12.0 (Android/13)
@TID: FIDOGATE-5.12-ge4e8b94
>Bounded Text_Buffer instead. So the language addresses this particular
>concern.
>
>I don`t know if GNAT implements all of those ways (in particular, the
>restriction Max_Image_Length), but that is hardly the fault of the language!
I see. I guess the error message could suggest those options, too. Perhaps
after the 2022 Gnat support work is completed.
That buffer support is pretty neat but my main concern which Gnat may (it
may not) address more than the current language by providing a cortex
runtime. Is that such demanding runtimes are brilliant but I am not sure if
even Ravenscar is scalable to so many microchips such as Rust is trying to
support. That isn`t a huge issue but barriers to entry like having to work
out your own exception replacement might be turning users away. Which is
unfortunate when Ada is the best language out there by a significant margin
for embedded development or frankly any protocol or hardware register use.
Of course others will rightly argue Ada is the best due to many of the more
complex runtime features but that doesn`t help with the issue of ease of
adoption on an unsupported microchip that I have raised above.
>
>For anyone else interested in this particular discussion, I recommend
>reading and following up on the ARG Githib issue rather than here
>(
https://github.com/Ada-Rapporteur-Group/User-Community-Input/issues/67).
>
--- PhoNews/3.12.0 (Android/13)
* Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441