Anonymous user
Talk:Range extraction: Difference between revisions
→TUSCRIPT example: So close ...
m (→Comment in Ada solution on notstion: Spelling.) |
(→TUSCRIPT example: So close ...) |
||
Line 56:
:''"For real-life applications it is better to use the notation -9..-4"''
True. if I were doing this for real then I would have liked to use a different range indication character, but, as in so many things, I modified/simplified an [http://www-cecpv.u-strasbg.fr/Documentations/lsf/html/lsf6.1_admin/G_jobarrays.html#32777 existing format that used dashes], to allow negative numbers - hence the compromise. (On seeing how easy it was to parse I left it in).
==TUSCRIPT example==
It would be good to both keep the current TUSCRIPT example - noting where it fails to follow the task description; as well as create a fully compliant version. It was pleasantly surprising to see that the language had a built-in routine that could so nearly produce the right answer! --[[User:Paddy3118|Paddy3118]] 21:31, 28 January 2011 (UTC)
| |||