> After taking a closer look at how the parsing needs to work, I see that
> fixing this (by issuing a warning) may be easier said than done. Maybe that's
> why no one has fixed it yet :-(

But is it really a problem ? It arises only because one abuses syntatic 
sugar and can be fixed by writing

{
25rFFs2.
26rFFs2.
27rFFs2.
28rFFs2.
29rFFs2.
30rFFs2.
31rFFs2.
32rFFs2
}

instead.

Stef