This sentence:

"Some people require a second explanation of the simpler version of
sublist (“$”), even though “$” is currently very simple."

Could probably be better expressed as:

"Some people require a second explanation of SUBLIST, which is
essentially the explanation of the *current* version of SUBLIST
described in this SRFI."

--

The sentence:

"Adding this capability to “$” makes it much more complicated to describe."

seems redundant, since we already said:

"It complicates explanation of “$”"

earlier.

On 3/2/13, Alan Manuel Gloria <almkg...@gmail.com> wrote:
> On 3/1/13, David A. Wheeler <dwhee...@dwheeler.com> wrote:
>> Alan Manuel Gloria:
>>
>>> Err I already wrote a draft section on Beni's proposal and pushed it
>>> *very* early this morning.
>>
>> Got it.  I took our versions and tried to merge them together.
>>
>> Please do take a look and fix any problems you see.
>>
>
> Seems okay, although:
>
> "There’s already a body of material on how to handle indentation-based
> languages, which tend to follow Python approaches and specifically do
> NOT differentiate between “indent 3 spaces” and “indent 1 space”, just
> INDENT."
>
> ...seems to come out of left field, given that the formal description
> above it mentions just "INDENT" and "DEDENT".  It may be better to
> reword it to something nearer to:
>
> "...which tend to follow Python or Haskell approaches and specifically
> consider the actual source stream to have matching indentations and
> dedentations"
>
> ...or, er, something clearer, anyway.  Erk.
>
> --
>
> Otherwise seems fine, we need more links to archive mailinglist messages.
>
> Sincerely,
> AmkG
>

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Readable-discuss mailing list
Readable-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/readable-discuss

Reply via email to