public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Joost van der Sluis <joost@cnoc.nl>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: Patch for pascal-dynamic arrays
Date: Sat, 15 May 2010 20:24:00 -0000	[thread overview]
Message-ID: <1273955042.32006.31.camel@wsjoost.cnoc.lan> (raw)
In-Reply-To: <20100514224613.GA3338@host0.dyn.jankratochvil.net>

On Sat, 2010-05-15 at 00:46 +0200, Jan Kratochvil wrote:
> On Fri, 14 May 2010 23:57:30 +0200, Joost van der Sluis wrote:
> > I can't apply it.
> 
> OK, sorry for the inconvenience.

No problem, I've got it to work!

In principle I did the same as you suggested. Eventually I've applied
the patch 'manually' by copy-pasting the right bits. I think there were
some eol-differences, or something.

But it works great. I don't understand the cleanup-bit entirely, but
you've found another solution for this problem I didn't think of. Thanks
for the help.

A few details, though.

Take a look a this bug-report
(http://sourceware.org/bugzilla/show_bug.cgi?id=11492) about the
identification of arrays. It has a better fix for that, and it avoids
problems when merging this later.

And when you do a 'print s' when the breakpoint is before line 80. (In
arrays.pas) you get 'Object is not allocated'. In theory this is true,
but unallocated strings in pascal are handled as empty strings (''). But
that's a minor issue that's fixable in p-valprint only.

The next challenge is to print individual items from the array. (print
DynArrStr[3]). But that didn't work with my patch either. And I think
that with your solution it's easier to implement this.

Again, thanks for the help, this patch works perfectly.

Joost.

  reply	other threads:[~2010-05-15 20:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 14:45 Joost van der Sluis
2009-09-16 15:45 ` Jan Kratochvil
2009-09-16 18:18   ` Joost van der Sluis
2009-09-16 18:41     ` Jan Kratochvil
2009-09-16 19:09       ` Joost van der Sluis
2009-09-30 16:00   ` Joost van der Sluis
2009-10-04 14:17     ` Jan Kratochvil
2009-10-05 10:08       ` Joost van der Sluis
     [not found]       ` <1254737231.3257.20.camel@wsjoost.cnoc.lan>
2009-10-05 14:43         ` Jan Kratochvil
2009-10-28 17:35       ` Joost van der Sluis
2009-10-30  9:47         ` Jan Kratochvil
2009-11-07 21:49           ` Joost van der Sluis
2010-04-12 11:25             ` Joost van der Sluis
2010-04-12 19:51               ` Jan Kratochvil
2010-04-14 10:35                 ` Joost van der Sluis
2010-05-06 23:05                   ` Jan Kratochvil
2010-05-14 21:58                     ` Joost van der Sluis
2010-05-14 22:46                       ` Jan Kratochvil
2010-05-15 20:24                         ` Joost van der Sluis [this message]
2010-05-15 21:44                           ` Jan Kratochvil
2010-05-16 12:04                             ` Jonas Maebe
2010-05-16 17:06                               ` Joost van der Sluis
2010-05-16 17:31                                 ` Jan Kratochvil
2010-05-16 21:49                                   ` Jonas Maebe
2010-05-16 21:55                                     ` Jonas Maebe
2010-05-16 18:31                               ` Jan Kratochvil

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=1273955042.32006.31.camel@wsjoost.cnoc.lan \
    --to=joost@cnoc.nl \
    --cc=archer@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).