Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.forth > #48769

Re: RfD: Unsigned Double Words Naming Convention

From "HAA" <someone@microsoft.com>
Newsgroups comp.lang.forth
Subject Re: RfD: Unsigned Double Words Naming Convention
Date 2016-07-05 00:19 +1000
Organization Aioe.org NNTP Server
Message-ID <nldr5j$hd2$1@gioia.aioe.org> (permalink)
References <0bfcdb36-eaf0-4634-8820-049911494e85@googlegroups.com><c1ddd988-4b71-4d7e-9776-69ce1c495e77@googlegroups.com> <nlcmq2$nmd$1@gioia.aioe.org> <37c74d57-5eac-44c5-b5db-8ff916abdd14@googlegroups.com>

Show all headers | View raw


krishna.myneni@ccreweb.org wrote:
> HAA writes:
> ...
> > Agreed.  All the 'D' words in ANS begin with .... D.  UD. would break that convention.
>
>
> Consider the following words from the floating point wordset:
>
>   DF@  DF!  SF@  SF!
>
> By your argument, these words should be named
>
>   FD@  FD!  FS@  FS!
>
> The current naming of these words in the standard means that D and S are modifiers for
> the type float. Putting the operations, @ and ! , next to F seems the most sensible
> thing to do.
>
> Similarly, U is a modifier for the type double in UD< .
>
> I wonder if our difference in preferences are not linguistic in origin, i.e. preferring
> UD<x> to DU<x> is due to the normal order of expressions in the English language. In
> other languages, modifiers follow the noun. Actually, one could argue that the latter
> is more Forth-like, but I think it presents problems as in the hypothetical case of
> renaming DF@ to FD@ (purely for the sake of argument here).

I use both DU< and UD.  Academically they may be inconsistent but so
is human language and its users don't even notice.  Learnt when children,
language inconsistencies vanish as memory and instant recall kick in.
It's the same with DU< and UD.  Both have been around so long that
Forth users only need to see the words and their respective actions
automatically pop into mind.  We don't change human language simply
to satisfy an academic principle.  IMO neither should we do it for Forth.


Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

RfD: Unsigned Double Words Naming Convention krishna.myneni@ccreweb.org - 2016-07-02 07:25 -0700
  Re: RfD: Unsigned Double Words Naming Convention Cecil Bayona <cbayona@cbayona.com> - 2016-07-02 10:01 -0500
  Re: RfD: Unsigned Double Words Naming Convention ruvim.pinka@gmail.com - 2016-07-02 12:43 -0700
    Re: RfD: Unsigned Double Words Naming Convention rickman <gnuarm@gmail.com> - 2016-07-03 01:05 -0400
      Re: RfD: Unsigned Double Words Naming Convention ruvim.pinka@gmail.com - 2016-07-03 00:31 -0700
        Re: RfD: Unsigned Double Words Naming Convention rickman <gnuarm@gmail.com> - 2016-07-03 11:54 -0400
    Re: RfD: Unsigned Double Words Naming Convention "HAA" <someone@microsoft.com> - 2016-07-05 00:19 +1000
      Re: RfD: Unsigned Double Words Naming Convention krishna.myneni@ccreweb.org - 2016-07-04 07:37 -0700
        Re: RfD: Unsigned Double Words Naming Convention "HAA" <someone@microsoft.com> - 2016-07-07 13:01 +1000
          Re: RfD: Unsigned Double Words Naming Convention krishna.myneni@ccreweb.org - 2016-07-09 08:40 -0700
            Re: RfD: Unsigned Double Words Naming Convention "HAA" <someone@microsoft.com> - 2016-07-10 18:23 +1000
              Re: RfD: Unsigned Double Words Naming Convention krishna.myneni@ccreweb.org - 2016-07-10 08:27 -0700
    Re: RfD: Unsigned Double Words Naming Convention "HAA" <someone@microsoft.com> - 2016-07-04 13:59 +1000
      Re: RfD: Unsigned Double Words Naming Convention krishna.myneni@ccreweb.org - 2016-07-03 22:42 -0700
    Re: RfD: Unsigned Double Words Naming Convention krishna.myneni@ccreweb.org - 2016-07-03 21:09 -0700
      Re: RfD: Unsigned Double Words Naming Convention ruvim.pinka@gmail.com - 2016-07-10 20:37 -0700
      Re: RfD: Unsigned Double Words Naming Convention ruvim.pinka@gmail.com - 2016-07-10 21:07 -0700

csiph-web