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

Groups > comp.lang.forth > #39470

Re: COMPILE, and :NONAME

Show all headers | View raw

on 30/05/2015 12:56:00,  wrote:
> "Alex McDonald" <blog@rivadpm.com> writes:
>>on 29/05/2015 21:47:39, Bernd Paysan wrote:
>>> https://www.complang.tuwien.ac.at/forth/header-ideas.html
>>
>>Now I'm thoroughly confused. I've implemented, with a few minor
>>modifications, the ideas in that post. Is it smart or intelligent?
> 
> If COMPILE, appends the behaviour to the current definition that
> EXECUTE performs (i.e., COMPILE, does what the standard specifies),
> it's intelligent.  If not, it's "smart"; one could also say "buggy",
> but I guess fans of this behaviour would not use this term.
> 
>> (An
>>aside; can we pick names that aren't synonyms please?)
> 
> I did not pick "smart", and nobody was writing about "smart COMPILE,",
> when I wrote about "intelligent COMPILE," (first in 1997); "smart
> COMPILE," was first used synonymous to "intelligent COMPILE, starting
> in 2000 in my records <86a74g$ntm$1@newsg1.svr.pol.co.uk>
> <cgph3o$cir$1@hercules.btinternet.com> ...
> 
> Then Bernd Paysan started to use "smart COMPILE," it for a COMPILE,
> that does not behave as specified in the standard.  I thought that's
> quite appropriate, because it reminds me immediately of "state-smart
> words" (which also work in the common case, and act up in uncommon
> cases, and then their defenders try to blame the uncommon case instead
> of the state-smart word), but I guess it might be different for a
> native speaker; so I would be fine with a different term, but you have
> to convince Bernd Paysan.
> 
> - anton

I see. Thank you, as this is now a lot clearer to me and makes sense of
some of the recent conversations here. When I see smart I will just have
to think of a sharp, stinging pain.

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

Thread

COMPILE, and :NONAME "Alex McDonald" <blog@rivadpm.com> - 2015-05-29 12:48 +0100
  Re: COMPILE, and :NONAME Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-05-29 14:15 +0100
    Re: COMPILE, and :NONAME "Alex McDonald" <blog@rivadpm.com> - 2015-05-29 15:23 +0100
  Re: COMPILE, and :NONAME anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-29 13:25 +0000
    Re: COMPILE, and :NONAME "Alex McDonald" <blog@rivadpm.com> - 2015-05-29 15:22 +0100
      Re: COMPILE, and :NONAME anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-29 14:45 +0000
        Re: COMPILE, and :NONAME "Alex McDonald" <blog@rivadpm.com> - 2015-05-29 17:09 +0100
          Re: COMPILE, and :NONAME "Alex McDonald" <blog@rivadpm.com> - 2015-05-29 17:13 +0100
          Re: COMPILE, and :NONAME anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-29 17:21 +0000
            Re: COMPILE, and :NONAME "Alex McDonald" <blog@rivadpm.com> - 2015-05-29 19:36 +0100
        Re: COMPILE, and :NONAME Bernd Paysan <bernd.paysan@gmx.de> - 2015-05-29 22:47 +0200
          Re: COMPILE, and :NONAME "Alex McDonald" <blog@rivadpm.com> - 2015-05-29 23:23 +0100
            Re: COMPILE, and :NONAME Bernd Paysan <bernd.paysan@gmx.de> - 2015-05-30 02:03 +0200
              Re: COMPILE, and :NONAME "Alex McDonald" <blog@rivadpm.com> - 2015-05-30 20:58 +0100
            Re: COMPILE, and :NONAME anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-30 11:56 +0000
              Re: COMPILE, and :NONAME albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-05-30 13:34 +0000
              Re: COMPILE, and :NONAME "Alex McDonald" <blog@rivadpm.com> - 2015-05-30 20:54 +0100
                Re: COMPILE, and :NONAME foxaudioresearch@gmail.com - 2015-06-01 17:34 -0700
                Re: COMPILE, and :NONAME "Alex McDonald" <blog@rivadpm.com> - 2015-06-02 15:54 +0100
              Re: COMPILE, and :NONAME Bernd Paysan <bernd.paysan@gmx.de> - 2015-05-30 23:45 +0200

csiph-web