Minor last-minute issues John Cowan (18 Sep 2012 17:45 UTC)
Re: Minor last-minute issues Per Bothner (18 Sep 2012 18:40 UTC)
Re: Minor last-minute issues John Cowan (18 Sep 2012 18:59 UTC)
Re: Minor last-minute issues David A. Wheeler (18 Sep 2012 21:32 UTC)
Re: Minor last-minute issues Per Bothner (18 Sep 2012 21:54 UTC)
Re: Minor last-minute issues David A. Wheeler (19 Sep 2012 00:03 UTC)
Re: Minor last-minute issues Per Bothner (19 Sep 2012 00:46 UTC)
Re: Minor last-minute issues Alan Manuel Gloria (19 Sep 2012 01:16 UTC)
Re: Minor last-minute issues John Cowan (19 Sep 2012 02:22 UTC)
Re: Minor last-minute issues Alan Manuel Gloria (19 Sep 2012 12:27 UTC)
Re: Minor last-minute issues David A. Wheeler (19 Sep 2012 13:44 UTC)

Re: Minor last-minute issues Per Bothner 18 Sep 2012 18:38 UTC

On 09/18/2012 10:45 AM, John Cowan wrote:
> I mentioned this before but it seems to have gotten lost: I recommend
> that [foo bar] in c-expressions be treated as ($bracket-list$ foo bar)
> rather than (bracketaccess foo bar).  This is compatible with Kawa,
> which is the only Scheme in my test suite to treat square brackets in
> this way.  In FemtoLisp and Rep, they are used for vector datums; in
> all other Schemes, they are synonyms for parentheses per R6RS, regular
> identifier characters, or lexical syntax errors.

Some context: The default binding of $bracket-list$ is like vector,
except that it returns an immutable vector.

There is also some target-typing: In a context that requires a
generic sequence (i.e. a type that implements java.util.List),
a $bracket-list$ is automatically (at compile-time) treated as
a constructor for that sequence type.

The syntax F0[F1 ... Fn] with no space between the F0 and the '['
is read as ($bracket-apply$ F0 F1 ... Fn).  This is used for
parameterized types, as in vector[string].  It is also used for "legacy"
array types: string[].
--
	--Per Bothner
xxxxxx@bothner.com   http://per.bothner.com/