Re:GNU ed 1.15
by mbrock on Friday January 04, 2019 @09:52AM
(#18824369)
Pretty interesting that there are to this day updates in the POSIX standard for ed...
[ Parent
| on HN ]
Yes... That also caught my eye... I guess it is helpful to have a sensible implementation-neutral standard to prevent implementations from drifting too much. This could be something like the C updates that fix undefined behavior.
Re:GNU ed 1.15
by merlincorey on Friday January 04, 2019 @01:45PM
(#18826532)
> This could be something like the C updates that fix undefined behavior.
Undefined behavior isn't necessarily something that should be fixed, in all cases. In some cases, it explicitly cannot be fixed, as it is undefined explicitly due to known differences in machines.
Re:GNU ed 1.15
by Skunkleton on Friday January 04, 2019 @03:27PM
(#18827319)
Undefined != implementation defined. The more stuff that gets moved to implementation defined the better.
If everything is implementation defined, why bother with a standard?
Re:GNU ed 1.15
by Skunkleton on Saturday January 05, 2019 @04:51PM
(#18834502)
https://stackoverflow.com/a/4105123
Why would you want undefined behavior?
Re:GNU ed 1.15
by merlincorey on Sunday January 06, 2019 @12:23AM
(#18836712)
To allow implementations slack to do things in the way that works best for them, in some cases of undefined behavior -- but not all of them.
If you have not read it before, you might find "The Value of Undefined Behavior" informative: https://nullprogram.com/blog/2018/07/20/
Re:GNU ed 1.15
by Skunkleton on Sunday January 06, 2019 @02:00PM
(#18839902)
The whole point of implementation defined behavior is to allow the individual implementations slack. I'm not saying C should be 100% UB free, just that implementation defined is preferable to undefined.