[Libre-soc-bugs] [Bug 1125] split instructions' pseudo-code into separate files so they can be [[!inline]]-ed into the wiki

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=1125

Luke Kenneth Casson Leighton <lkcl at lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=1013

--- Comment #9 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(reminder again: please take extra care to trim context, it is
 easy to see replies above and wastes time and resources when reading
 duplicate copies of already-read comments)

(In reply to Jacob Lifshay from comment #7)

> ok, how about this:
> 
> we have the entire RFC instruction entry in e.g.
> openpower/isa/bitmanip/sadduw.mdwn and have the pseudo-code separated out
> into openpower/isa/bitmanip/sadduw_code.mdwn.

that works really well, the pandoc plugin already does the job.
if "code" is in a fixed location very little modification to
the machine-reading parser is needed.

freeform text is not appropriate to support.

4-space indentation can be supported by the pandoc plugin
(easily added because the plugin knows for a fact anything
 ending "_code.mdwn" gets indented 4 spaces).

pick a bugreport, this is a relatively small task...
bug #1013 would do well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.