More. Extensible records makes a syntactic difference between field
access and function call. So if one wants to export a type abstractly
or simply to provide functions operating on it without fixing the
fact that they are physically fields, he ends in writing functions like
size:: MyRecord -> Int
size x = x.MyRecord.size
which are unnecessary now, even if size is simply a field.
It reminds me of C++ which wants us to provide methods for accessing
data fields (for allowing them to be later redefined as methods,
and for allowing everything to be uniformly used with "()" after the
feature name). Ugh.
--
__("< Marcin Kowalczyk * [EMAIL PROTECTED] http://qrczak.ids.net.pl/
\__/ GCS/M d- s+:-- a22 C+++$ UL++>++++$ P+++ L++>++++$ E-
^^ W++ N+++ o? K? w(---) O? M- V? PS-- PE++ Y? PGP+ t
QRCZAK 5? X- R tv-- b+>++ DI D- G+ e>++++ h! r--%>++ y-
