This message was created automatically by mail delivery software.
A message that you sent could not be delivered to all of its recipients. The
following address(es) failed:
[EMAIL PROTECTED]:
Disc quota exceeded:
retry timeout exceeded
------ This is a copy of the message, including all the headers. ------
Return-path: <[EMAIL PROTECTED]>
Received: from mauve.csi.cam.ac.uk ([131.111.8.38] ident=exim)
by red.csi.cam.ac.uk with esmtp (Exim 3.03 #1)
id 11yuws-00078B-00
for [EMAIL PROTECTED]; Fri, 17 Dec 1999 10:49:22 +0000
Received: from [208.156.39.203] (helo=BFLITEMAIL3)
by mauve.csi.cam.ac.uk with smtp (Exim 3.03 #1)
id 11yuwr-0004TF-00
for [EMAIL PROTECTED]; Fri, 17 Dec 1999 10:49:21 +0000
Received: from deck.metacard.com ([209.180.240.46])
by BFLITEMAIL3.bigfoot.com (LiteMail v1.3 (1)) with SMTP id
17Dec1999_BFLITEMAIL3_19422_80480117;
Fri, 17 Dec 1999 05:49:55 -0500 EST
Received: (from majordomo@localhost)
by deck.metacard.com (8.9.1/8.9.1) id DAA30155
for xtalk-digest-outgoing; Fri, 17 Dec 1999 03:13:05 -0700
Date: Fri, 17 Dec 1999 03:13:05 -0700
Message-Id: <[EMAIL PROTECTED]>
X-Authentication-Warning: deck.metacard.com: majordomo set sender to
[EMAIL PROTECTED] using -f
From: [EMAIL PROTECTED] (xtalk)
To: [EMAIL PROTECTED]
Subject: xtalk V1 #350
Reply-To: [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
Precedence: bulk
xtalk Friday, December 17 1999 Volume 01 : Number 350
In this issue:
Re: Re: xTalk: Getting input from console
Re: xTalk: Getting input from console
Re: xTalk: Getting input from console
----------------------------------------------------------------------
Date: Thu, 16 Dec 1999 14:51:12 +0100
From: "M. Uli Kusterer" <[EMAIL PROTECTED]>
Subject: Re: Re: xTalk: Getting input from console
>Users of these terminal/console windows are in real life programmers,
>most are C programmers. The whole concept is tied into the C language
>and "normal" people do not use command lines very often, although they
>could accomplish enormous tasks with commands like sed or even just
>grep! But end users are spoiled by those terrible GUIs ;-) and can only
>think in menus and are simply unable to grasp the concepts that go on
>behind that stuff on the surface. ;-)
R�diger,
sure, but these shell windows are still rather common under Unix, some
people told me (at least they are using them rather frequently), and they
used to be used under DOS. What were they called there? Shell? Could we
maybe make that a synonym to stdin and stdout?
Never mind. Since we're really talking about a Dodo thing here, I guess
it's no use to add another synonym for a rarely-used feature, especially
since for CGIs standardInput and standardOutput actually make sense.
Cheers,
- -- M. Uli Kusterer
- ------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
- --- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
------------------------------
Date: Thu, 16 Dec 1999 10:14:00 -0500
From: "Raymond E. Griffith" <[EMAIL PROTECTED]>
Subject: Re: xTalk: Getting input from console
- ----------
>From: "M. Uli Kusterer" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Re: xTalk: Getting input from console
>Date: Thu, Dec 16, 1999, 8:51 AM
>
>>Users of these terminal/console windows are in real life programmers,
>>most are C programmers. The whole concept is tied into the C language
>>and "normal" people do not use command lines very often, although they
>>could accomplish enormous tasks with commands like sed or even just
>>grep! But end users are spoiled by those terrible GUIs ;-) and can only
>>think in menus and are simply unable to grasp the concepts that go on
>>behind that stuff on the surface. ;-)
>
> R�diger,
>
> sure, but these shell windows are still rather common under Unix, some
> people told me (at least they are using them rather frequently), and they
> used to be used under DOS. What were they called there? Shell? Could we
> maybe make that a synonym to stdin and stdout?
>
> Never mind. Since we're really talking about a Dodo thing here, I guess
> it's no use to add another synonym for a rarely-used feature, especially
> since for CGIs standardInput and standardOutput actually make sense.
>
> Cheers,
> -- M. Uli Kusterer
>
R�diger,
Ok, so I am a GUI spoiled .... (now why am I thinking about the stuff
that's been in the refrigerator too long?)
He, he. But I do like the graphical interface. I used to be passing fair
in Pascal. But most people, me included, like our GUIs. And OOP is so much
easier when you can see the objects!
That's why I require graphing calculators in my math classes. If students
can see the functions, then they can work with them a *lot* more easily.
So Scott and company, keep up the good work! MetaCard is great!
Raymond
------------------------------
Date: Fri, 17 Dec 1999 09:28:02 +1100
From: "Steven D'Aprano" <[EMAIL PROTECTED]>
Subject: Re: xTalk: Getting input from console
M. Uli Kusterer wrote:
>
> Since we're really talking about a Dodo thing here
Since being introduced to Linux, I've come to appreciate the power of
the command line. Where ever practical, I try to allow *both* a GUI and
CLI for an application. (If you're clever, your GUI can simply call the
CLI in most cases.)
> I guess it's no use to add another synonym for a rarely-used
> feature, especially since for CGIs standardInput and standardOutput
> actually make sense.
Assuming there's no performance penalties involved, I vote for keeping
stdin/stout/stderr as well as synonyms standardInput etc.
- --
Steven D'Aprano
==========================================
M.B. Sales Pty Ltd Ph: +61 3 9460-5244
A.C.N. 005-964-796 Fax: +61 3 9462-1161
------------------------------
End of xtalk V1 #350
********************
