From: Gaius Mulley <gaius@glam.ac.uk>
To: Jim Blandy <jimb@codesourcery.com>
Cc: "Pierre Muller" <muller@ics.u-strasbg.fr>,
<gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] Unbounded array support implemented (for Modula-2)
Date: Mon, 30 Jul 2007 06:29:00 -0000 [thread overview]
Message-ID: <87abtgscnc.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <m34pjpo72d.fsf@codesourcery.com> (Jim Blandy's message of "Fri, 27 Jul 2007 14:44:26 -0700")
Jim Blandy <jimb@codesourcery.com> writes:
> "Pierre Muller" <muller@ics.u-strasbg.fr> writes:
>> Modula-2 is not the only language supporting unbounded
>> arrays, I would be interested in using the same kind of code for
>> pascal language support.
>
> In C, there are ABI documents that specify how each type is
> represented in memory for a given processor, the goal being to specify
> things enough that one can link code from different vendor's compilers
> together when they implement the same ABI. It sounds like the 'PIM'
> documents are the equivalent for Modula-2; is that right?
Hi Jim,
ah alas, the PIM (Programming in Modula-2 books by N. Wirth) ed2, ed3
and ed4 don't say how unbounded arrays should be implemented or
anything about parameter ordering etc - they really concentrate on the
semantics of the language itself and to a lesser extent the libraries.
The ISO standard doesn't say much about unbounded array implementation
either - although it does tidy up many other loose ends.
> Are there equivalent documents for Pascal?
>
> I'm not sure it actually would be a good idea to unify Pascal and
> Modula-2 code if they are meant to follow different specifications.
> Bugs in that common code might have the same fix for both languages,
> or they might not. People would hesitate to fix things, for fear of
> breaking the other language they're not familiar with.
>
> I don't think we should require Gaius's patch to unify the
> Pascal/Modula-2 support.
I agree :-) the amount of shared code would be fairly small anyhow and
many blocks would have to be predicated by testing whether we were in
Modula-2 language mode or Pascal language mode. At which point it
begs the question whether these sections of code would be better
separately placed into m2-valprint.c, p-valprint.c, m2-typeprint.c and
p-typeprint.c etc.
regards,
Gaius
prev parent reply other threads:[~2007-07-28 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 7:07 Gaius Mulley
2007-07-26 7:36 ` Markus Deuling
2007-07-27 12:26 ` Gaius Mulley
2007-07-27 20:22 ` Eli Zaretskii
2007-07-30 8:29 ` Gaius Mulley
2007-07-30 23:34 ` Jim Blandy
2007-07-31 3:01 ` Jim Blandy
2007-07-31 16:47 ` Gaius Mulley
2007-07-31 16:48 ` Jim Blandy
2007-08-01 14:01 ` Gaius Mulley
2007-07-31 19:18 ` Jim Blandy
2007-10-16 16:59 ` Gaius Mulley
2007-10-16 22:04 ` Jim Blandy
2007-07-26 22:58 ` Pierre Muller
2007-07-27 13:17 ` Gaius Mulley
2007-07-27 13:28 ` Pierre Muller
2007-07-28 0:59 ` Jim Blandy
2007-07-30 6:29 ` Gaius Mulley [this message]
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=87abtgscnc.fsf@j228-gm.comp.glam.ac.uk \
--to=gaius@glam.ac.uk \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@codesourcery.com \
--cc=muller@ics.u-strasbg.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