From: Marko Rauhamaa <marko@pacujo.net>
To: Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com>
Cc: Carlos Pita <carlosjosepita@gmail.com>,
David Thompson <dthompson2@worcester.edu>,
"guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: A couple of questions about goops method parameters
Date: Sat, 06 Sep 2014 01:26:27 +0300 [thread overview]
Message-ID: <874mwliu0c.fsf@elektro.pacujo.net> (raw)
In-Reply-To: <87ha0lg2ep.fsf@taylan.uni.cx> (Taylan Ulrich Bayirli's message of "Fri, 05 Sep 2014 23:53:18 +0200")
Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com>:
> Though after pondering a bit I realized that it indeed seems impossible
> to compile "(.bar foo)" (could result from "foo[.bar]" via SRFI-105)
> into the correct memory offset, if there are multiple record types each
> with a '.bar' field, because it's not statically known which record type
> 'foo' has. Maybe that's exactly what you meant.
Yes.
It is amusing, though, that C originally suffered from the same issue:
the struct field offsets were global linker objects. That's why to this
day, unix/linux C structs have ugly field prefixes:
struct timeval {
time_t tv_sec;
suseconds_t tv_usec;
};
struct timezone {
int tz_minuteswest;
int tz_dsttime;
};
struct linger {
int l_onoff;
int l_linger;
};
struct sockaddr_in {
sa_family_t sin_family;
in_port_t sin_port;
struct in_addr sin_addr;
};
struct in_addr {
uint32_t s_addr;
};
struct iovec {
void *iov_base;
size_t iov_len;
};
and so on...
Marko
next prev parent reply other threads:[~2014-09-05 22:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 2:05 A couple of questions about goops method parameters Carlos Pita
2014-09-03 15:49 ` Carlos Pita
2014-09-03 16:47 ` Marko Rauhamaa
2014-09-03 18:05 ` Carlos Pita
2014-09-03 16:20 ` Panicz Maciej Godek
2014-09-05 8:32 ` Nala Ginrut
2014-09-05 12:47 ` Carlos Pita
2014-09-05 19:03 ` Panicz Maciej Godek
2014-09-05 19:12 ` David Thompson
2014-09-05 19:35 ` Panicz Maciej Godek
2014-09-05 19:55 ` David Thompson
2014-09-05 20:10 ` Taylan Ulrich Bayirli/Kammer
2014-09-05 20:50 ` David Thompson
2014-09-07 10:33 ` Neil Jerram
2014-09-07 15:27 ` Taylan Ulrich Bayirli/Kammer
2014-09-05 20:10 ` Panicz Maciej Godek
2014-09-05 20:18 ` Taylan Ulrich Bayirli/Kammer
2014-09-05 20:37 ` Panicz Maciej Godek
2014-09-05 20:51 ` Marko Rauhamaa
2014-09-05 21:53 ` Taylan Ulrich Bayirli/Kammer
2014-09-05 22:26 ` Marko Rauhamaa [this message]
2014-09-05 20:44 ` Marko Rauhamaa
2014-09-05 21:08 ` Panicz Maciej Godek
2014-09-05 22:14 ` Marko Rauhamaa
2014-09-06 8:53 ` Panicz Maciej Godek
2014-09-06 10:44 ` Taylan Ulrich Bayirli/Kammer
2014-09-06 11:27 ` Marko Rauhamaa
2014-09-06 11:54 ` Taylan Ulrich Bayirli/Kammer
2014-09-06 23:46 ` Panicz Maciej Godek
2014-09-07 0:20 ` Marko Rauhamaa
2014-09-07 12:57 ` Taylan Ulrich Bayirli/Kammer
2014-09-07 13:58 ` Marko Rauhamaa
2014-09-07 16:46 ` Taylan Ulrich Bayirli/Kammer
2014-09-07 19:49 ` Marko Rauhamaa
2014-09-07 23:13 ` Taylan Ulrich Bayirli/Kammer
[not found] ` <CAPjoZoc7X7s+keog6avP62yvgJyQ3Ma_jomhw6xQq_rK9jnhVw@mail.gmail.com>
2014-09-06 16:57 ` Nala Ginrut
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mwliu0c.fsf@elektro.pacujo.net \
--to=marko@pacujo.net \
--cc=carlosjosepita@gmail.com \
--cc=dthompson2@worcester.edu \
--cc=guile-user@gnu.org \
--cc=taylanbayirli@gmail.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).