From: Alexandre Pilkiewicz <alexandre.pilkiewicz@polytechnique.org>
To: caml-list@inria.fr
Subject: [MLPost] Curly brances
Date: Fri, 5 Mar 2010 17:51:48 +0100 [thread overview]
Message-ID: <9020d4c51003050851xe9f2a7ftf9fd2cc9deae40d6@mail.gmail.com> (raw)
Dear list
I'm sorry if that's the wrong list, but mlpost doesn't seem to have
it's own list.
I'm starting to use (quite happily!) MLPost for some drawing, and it
works perfectly. But now I'm trying some more advance things, and I'm
stuck:
I would like to draw variable size curly braces, pretty much like
\underbrace would do in LaTeX. More specifically, I want to draw 16
boxes horizontally alligned (representing 16 bits of a VM
instruction), and "select" (by a curly brace) say the 4 first and say
it's the opcode, and then the 12 next and say it's the argument.
How could I do that?
Thanks in advance.
Alexandre Pilkiewicz
next reply other threads:[~2010-03-05 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 16:51 Alexandre Pilkiewicz [this message]
2010-03-06 9:06 ` [Caml-list] " Johannes Kanig
2010-03-06 11:45 ` Alexandre Pilkiewicz
2010-03-06 15:22 ` Johannes Kanig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9020d4c51003050851xe9f2a7ftf9fd2cc9deae40d6@mail.gmail.com \
--to=alexandre.pilkiewicz@polytechnique.org \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).