On Tue, Aug 08, 2000 at 02:44:59PM -0400, Uri Guttman wrote:
> the key word besides global is default. this would be the value used by
> any new filehandle created. you can override that at anytime in that
> filehandle. otherwise the default value for $/ for new handles will be
> hardcoded in %CON
> "JSD" == Jonathan Scott Duff <[EMAIL PROTECTED]> writes:
JSD> On Tue, Aug 08, 2000 at 01:46:41PM -0400, Uri Guttman wrote:
>> interesting point: we are all in agreement for filehandle specific
>> $/ and $\. but what about global default values for those handles
>> which hve not had
On Tue, Aug 08, 2000 at 01:50:35PM -0400, Ted Ashton wrote:
> Hear, hear! Chomp (which I still consider a useful critter :-), needs a
> $/ sort of thing to know what to chomp and the lines it chomps may or may
> not have come from a given file.
Chomping *is* useful, but it's a per-filehandle t
On Tue, Aug 08, 2000 at 01:46:41PM -0400, Uri Guttman wrote:
> interesting point: we are all in agreement for filehandle specific $/
> and $\. but what about global default values for those handles which hve
> not had theirs set? you can still set the global $/ and affect all
> handles which don't
Thus it was written in the epistle of Uri Guttman,
>
> interesting point: we are all in agreement for filehandle specific $/
> and $\. but what about global default values for those handles which hve
> not had theirs set? you can still set the global $/ and affect all
> handles which don't have p
At 01:46 PM 8/8/00 -0400, Uri Guttman wrote:
>interesting point: we are all in agreement for filehandle specific $/
>and $\. but what about global default values for those handles which hve
>not had theirs set? you can still set the global $/ and affect all
>handles which don't have private $/.
>
> "BL" == Bart Lateur <[EMAIL PROTECTED]> writes:
BL> On Tue, 08 Aug 2000 01:29:47 GMT, Ed Mills wrote:
>> I actually saw this in the newsgroups and thought it was a neat idea. What
>> about
>>
>> println $textvar;
i am against println. it is not so useful that i would be using i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
>This is probably what I disliked most about Pascal - it presumes it
>knows best what units of output you want to write at any one time - a
>piece of a line or an entire line. I feel this dates back to the
>mainframe world (a
On Tue, 08 Aug 2000 01:29:47 GMT, Ed Mills wrote:
>I actually saw this in the newsgroups and thought it was a neat idea. What
>about
>
> println $textvar;
>
>instead of
>
> print "$textvar\n";
I can currently do that with $\, and $, for strings between items. For
example:
($\, $,)
Ed Mills wrote:
>
> I actually saw this in the newsgroups and thought it was a neat idea. What
> about
>
>println $textvar;
>
> instead of
>
>print "$textvar\n";
>
> Ever so much easier to read and write, prints the arg and appends \n.
This is probably what I disliked most about Pasc
Too special purpose.
I assume you don't do
print "foo\nbar\gasp\n";
very often.
> "EM" == Ed Mills <[EMAIL PROTECTED]> writes:
EM> I actually saw this in the newsgroups and thought it was a neat idea. What
EM> about
EM>println $textvar;
EM> instead of
EM>print "$tex
[Reply-To set to [EMAIL PROTECTED]]
Ed Mills wrote:
>
> I actually saw this in the newsgroups and thought it was a neat idea. What
> about
>
>println $textvar;
>
> instead of
>
>print "$textvar\n";
>
> Ever so much easier to read and write, prints the arg and appends \n.
You can cur
12 matches
Mail list logo
