From: Ed L Cashin <ecashin@coe.uga.edu>
Cc: Mailing List <ntg-context@ntg.nl>
Subject: Re: MetaFun
Date: 12 Dec 2000 10:35:51 -0500 [thread overview]
Message-ID: <m3elzdmz3c.fsf@coe.uga.edu> (raw)
In-Reply-To: <20001211135633.R1834@cs.ucc.ie>
Marc van Dongen <dongen@cs.ucc.ie> writes:
> Hello,
>
>
> This time no questions.
> I hope some people will enjoy the metafun appended
> below. I'm sure it could have done a bit more
> elegantly, but this does the trick as well. (See
> also: htpp://www.cs.ucc.ie/~dongen/xmas.pdf (55020 bytes).
Great! Thanks.
> In case some people are wondering; I did part of
> the picture in xfig first and then used the
> coordinates to write the metapost code. If people
> know of better (more clever) ways of doing this
> then I would be delighted to find out.
I don't know if this is your style or if it fits your application, but
instead of writing out a long list of points, I sometimes find it
easier to use a for loop.
I can declare a metapost array for holding points or paths, and then
initialize it using a for loop and some simple math. It makes the
code much easier to read, understand, and maintain.
--
--Ed Cashin PGP public key:
ecashin@coe.uga.edu http://www.coe.uga.edu/~ecashin/pgp/
next prev parent reply other threads:[~2000-12-12 15:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 13:56 MetaFun Marc van Dongen
2000-12-12 15:35 ` Ed L Cashin [this message]
2000-12-12 15:48 ` MetaFun Marc van Dongen
2000-12-12 16:18 ` MetaFun Ed L Cashin
-- strict thread matches above, loose matches on Subject: below --
2021-02-20 16:27 metafun Hans Hagen
2021-02-20 17:43 ` metafun Otared Kavian
2021-02-20 21:19 ` metafun Hans Hagen
2010-10-23 19:34 metafun Herbert Voss
2010-10-23 22:14 ` metafun Aditya Mahajan
2016-03-24 17:23 ` metafun Piotr Kopszak
2016-03-24 17:24 ` metafun Piotr Kopszak
2016-03-24 18:14 ` metafun luigi scarso
2016-03-24 18:22 ` metafun Hans Hagen
2010-10-20 12:03 metafun Hans Hagen
2010-10-20 12:11 ` metafun Mojca Miklavec
2010-10-20 12:23 ` metafun Martin Schröder
2010-10-20 12:49 ` metafun Vedran Miletić
2010-10-20 12:17 ` metafun Taco Hoekwater
2010-10-20 22:42 ` metafun Kevin D. Robbins
2010-10-21 7:10 ` metafun Hans Hagen
2010-10-22 14:06 ` metafun Taco Hoekwater
2010-10-22 14:20 ` metafun Hans Hagen
2010-10-22 14:22 ` metafun Taco Hoekwater
2010-10-22 15:29 ` metafun Otared Kavian
2010-10-22 16:09 ` metafun Kevin D. Robbins
2010-10-22 15:12 ` metafun Wolfgang Schuster
2010-10-22 15:28 ` metafun Hans Hagen
2010-10-23 10:49 ` metafun Alan BRASLAU
2004-06-23 15:03 metafun jimarin
[not found] ` <m2eko6gvg m.fsf@levana.de>
2004-06-23 15:11 ` metafun Patrick Gundlach
2004-06-23 15:26 ` metafun jimarin
2004-06-23 15:45 ` metafun Patrick Gundlach
2004-06-23 15:55 ` metafun jimarin
2004-06-23 16:03 ` metafun Patrick Gundlach
2004-06-24 8:13 ` metafun Hans Hagen
2001-09-16 9:13 metafun Hervé Rouault
2001-03-21 14:23 metafun guravage m.a.
2001-03-21 15:30 ` metafun Hans Hagen
2000-09-12 10:26 metafun Hans Hagen
2000-09-12 13:41 ` metafun Robert F. Beeger
[not found] ` <4.3.2.7.0.20000912152319.00b2ae30@rzdspc1.informatik.uni-h amburg.de>
2000-09-12 15:06 ` metafun Hans Hagen
2000-09-13 7:39 ` metafun Michal Kvasnicka
2000-07-17 0:45 (no) hyphenation Hans Hagen
2000-07-19 7:13 ` Hans Hagen
2000-07-24 20:20 ` metafun Hraban
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=m3elzdmz3c.fsf@coe.uga.edu \
--to=ecashin@coe.uga.edu \
--cc=ntg-context@ntg.nl \
/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).