This seems good...the HOF stuff seems to have pretty well accepted, and
the thumbtack notation with it.
Dave
On Thu, 17 Aug 2000, Clayton Scott wrote:
On Wed, 16 Aug 2000, David L. Nicol wrote:
%record = loadrecord($studentID);
with %record {
Dave Storrs wrote:
On 17 Aug 2000, Johan Vromans wrote:
Dave Storrs [EMAIL PROTECTED] writes:
2) "express" should guarantee that, before it creates a variable
names $FOO, it first calls "local" on any existing $FOO
Why, if the variable is lexical (see 3)?
D'oh. s{2) .+^}{}
This seems less of a leap of logic/faith:
%record = loadrecord($studentID);
with %record {
print SPAM;
Dear ^name:
Your tuition is now due. Please send in a payment of at least
^minumum.
SPAM
};
"I do not thin' that
Damian Conway wrote:
So Cwith is going to have to do some pretty freaky magic to work out
it should call that sub as part of the Cprint. And call it with a
specifically ordered argument list.
Yes, I never said it would work, just that it looked nicer :)
However, your suggestion
I'm not sure if you are disagreeing with me or not.
The context was the statment that $STDOUT is the _default_ filehandle.
I was pointing out that by _overriding_ the instantaneous meaning of
$STDOUT to the default fail handle, one would lose the immediate
access to the previous value.
I.e.
Chaim Frenkel wrote:
Unless one wants to have a $DEFAULT filehandle and get rid of single
arg select.
Great minds think alike. :-)
I'm in the process of codifying an RFC that will be titled something
like:
"Replace default filehandle / select with $OUTPUT fileobject"
(chose $OUTPUT b/c
Chaim Frenkel wrote:
NW P.S. If you're not on -io, this implicitly means you DON'T CARE and are
NW willing to accept whatever we come up with. So, everyone that's
NW interested please get on -io. Thanks again.
That's a bit strong. All we are doing is filtering the garbage for Larry.
Peter Scott wrote:
I don't want to be in the -io discussion; I just want to know the
conclusions that might affect -language. It seems silly to discuss
command-line options for setting $| here if there isn't going to be a $|.
Ok, read this thread (4 messages long):
On Tue, Aug 15, 2000 at 12:57:46PM -0700, Nathan Wiger wrote:
This is a succinct summary of the basic conclusions thus far:
1. a default filehandle IS needed sometimes, but only
for stuff like print
Well, I think that Cprint should always print to $PERL::STDOUT (or
whatever we call
Jonathan Scott Duff wrote:
On Tue, Aug 15, 2000 at 12:57:46PM -0700, Nathan Wiger wrote:
This is a succinct summary of the basic conclusions thus far:
1. a default filehandle IS needed sometimes, but only
for stuff like print
Well, I think that Cprint should always print to
"JSD" == Jonathan Scott Duff [EMAIL PROTECTED] writes:
JSD On Tue, Aug 15, 2000 at 12:57:46PM -0700, Nathan Wiger wrote:
This is a succinct summary of the basic conclusions thus far:
1. a default filehandle IS needed sometimes, but only
for stuff like print
JSD Well, I think that Cprint
"NW" == Nathan Wiger [EMAIL PROTECTED] writes:
NW2. $|, $\, $/, etc will probably go away entirely in
NW favor of object methods such as $handle-autoflush
It think they will still be needed as lexical variables used as an
initializer for the corresponding per-filehandle value.
chaim
At 12:57 PM 8/15/00 -0700, Nathan Wiger wrote:
This is a succinct summary of the basic conclusions thus far:
1. a default filehandle IS needed sometimes, but only
for stuff like print
2. $|, $\, $/, etc will probably go away entirely in
favor of object methods such as
On Tue, Aug 15, 2000 at 06:53:30PM -0400, Chaim Frenkel wrote:
What if you want to print to a default file handle and also to STDOUT?
select(OTHERFH);
print "This goest to OTHERFH\n";
print STDOOUT "This went to STDOUT\n";
print $_ "Here I come to save the day!\n" for
14 matches
Mail list logo
