On date Sunday 2024-01-21 18:43:36 +0100, Anton Khirnov wrote: > Quoting Stefano Sabatini (2024-01-20 12:32:42) [...] > > When you present an example you usually start with an explanation > > (what it does) and then present the command, not the other way around. > > I don't, neither does most literature I can recall. Typically you first > present a thing, then explain its structure. Explaning the structure of > something the reader has not seen yet is backwards, unnatural, and hard > to understand.
I still don't understand what "literature" you are referring to. If you see most examples in the FFmpeg docs they are in the form: @item This does this and that...: @example ... @end example An explanation is presented *before* introducing the example itself, in other words plain English before the actual command/code. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
