From: Bakul Shah <bakul@iitbombay.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: CDL & UCDS
Date: Fri, 10 Feb 2023 11:31:36 -0800 [thread overview]
Message-ID: <35DBD3F6-12C1-4EDD-A546-AC3343329F7B@iitbombay.org> (raw)
In-Reply-To: <6af20c95-7b9f-8a06-b930-e1d8e74101d4@unixsh.com>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
On Feb 10, 2023, at 8:44 AM, Steve <srb@unixsh.com> wrote:
>
> I took it over the code base at some point and among other things added macros so that repeated wire to chip connection patterns and names could be generated without the labor intensive one wire at a time e.g. wire[0-7] connects to pin[0-7]. The macro would be expanded so that wire0 connected to pin0 etc.
For specifying wirewrap lists compactly, at Fortune Systems we used some syntax Rob Warnock had picked up elsewhere. Basically lists in all angle brackets would expand in parallel and then lists in all square brackets. So for example
U[0:1].P<3:0> = U[2:3].P<1,2,4:5>
would expand as
U0.P3 = U2.P1
U0.P2 = U2.P2
U0.P1 = U2.P4
...
U1.P0 = U3.P5
This turns out to be an interesting programming exercise. Its grammar is clearly not context-free because the number of items in all bracketed lists of give type and at a given level had to match.
[Program for this also happened to be the first C program I wrote for pay -- and spent a week debugging because coming from Pascal I used "=" when I should've used "=="]
[-- Attachment #2: Type: text/html, Size: 1958 bytes --]
next prev parent reply other threads:[~2023-02-10 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 16:44 [TUHS] " Steve
2023-02-10 19:31 ` Bakul Shah [this message]
2023-02-12 7:20 ` [TUHS] " arnold
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=35DBD3F6-12C1-4EDD-A546-AC3343329F7B@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=tuhs@tuhs.org \
/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).