[EMAIL PROTECTED] schreef:
*PLONK*
--
Affijn, Ruud
"Gewoon is een tijger."
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
John W.Krahn <[EMAIL PROTECTED]> writes:
> After the module name, which has to be a bareword, must follow a
> *list*, which cannot be barewords.
My post had a typo in it .. again:
use Fcntl ':seek'; it should have said and in fact is how I have been
experimenting with it.
I'm not sure what I di
On Tuesday 11 December 2007 15:53, [EMAIL PROTECTED] wrote:
>
> John W.Krahn <[EMAIL PROTECTED]> writes:
> >
> > On Tuesday 11 December 2007 14:09, [EMAIL PROTECTED] wrote:
> >>
> >> John W.Krahn <[EMAIL PROTECTED]> writes:
> >> >
> >> > use Fcntl ':seek';
> >> >
> >> > seek FILE, -100, SEEK_END or
John W.Krahn <[EMAIL PROTECTED]> writes:
> On Tuesday 11 December 2007 14:09, [EMAIL PROTECTED] wrote:
>>
>> John W.Krahn <[EMAIL PROTECTED]> writes:
>> >
>> > use Fcntl ':seek';
>> >
>> > seek FILE, -100, SEEK_END or die "Cannot seek on './myfile' $!";
>>
>> Still seeing something I don't underst
From: [EMAIL PROTECTED]
> Using perldoc -q tail
> leading to
> perldoc -f seek
> perldoc -f tell
>
> I'm not getting how to use those functions. Partly because what
> passes for examples in those docs doesn't use normal language, instead
> they use terms like WHENCE, something that's almost never
On Tuesday 11 December 2007 14:09, [EMAIL PROTECTED] wrote:
>
> John W.Krahn <[EMAIL PROTECTED]> writes:
> >
> > use Fcntl ':seek';
> >
> > seek FILE, -100, SEEK_END or die "Cannot seek on './myfile' $!";
>
> Still seeing something I don't understand. Using a working version
> of the code I posted
On Tuesday 11 December 2007 12:57, [EMAIL PROTECTED] wrote:
>
> John W.Krahn <[EMAIL PROTECTED]> writes:
> >
> > Perl programmers usually frown on the use of CamelCase variable
> > names.
>
> Do you know wy perl programmers prefer same case variable names?
That is not what I said. In any case, se
John W.Krahn <[EMAIL PROTECTED]> writes:
> use Fcntl ':seek';
>
> seek FILE, -100, SEEK_END or die "Cannot seek on './myfile' $!";
Still seeing something I don't understand. Using a working version of
the code I posted (included at the end) telling seek to go to 100
bytes before the byte count a
On Tue, Dec 11, 2007 at 02:57:02PM -0600, [EMAIL PROTECTED] wrote:
> John W.Krahn <[EMAIL PROTECTED]> writes:
>
> > Perl programmers usually frown on the use of CamelCase variable names.
> Do you know wy perl programmers prefer same case variable names?
I suspect the answer to that is to be foun
On Tue, 11 Dec 2007 12:05:13 -0800
John W.Krahn <[EMAIL PROTECTED]> wrote:
[snip]
> This shows the influence that the C programming language has on Perl.
> for (;;) { ... } is used in C for an infinite loop. In Perl you could
> also write that as while (1) { ... }.
Minor quibble: 'while (1)
On Dec 11, 3:21 pm, [EMAIL PROTECTED] wrote:
> Whiners are just not worth the effort. Might have done well to just
> hold your tongue right along. Its puzzling why you didn't.
You just answered your own question. I didn't bother giving you any
explicit advice because half of your post was whi
John W.Krahn <[EMAIL PROTECTED]> writes:
> man 2 lseek
> [ SNIP ]
> NOTES
>This document's use of whence is incorrect English, but
>maintained for historical reasons.
OK, I see how having used WHERE in the perldoc stuff would be out of
step with what its all based on.
>> Even
Paul Lalli <[EMAIL PROTECTED]> writes:
> Read
> perldoc -f open
> for how to open a file in read/write mode.
Always amazes me when someone so taken with themselves as you seem to
be finds time to write a lengthy point by point rebuttal to a
non-debating post but fails to SHOW where the code is w
On Tuesday 11 December 2007 10:22, [EMAIL PROTECTED] wrote:
>
> Using perldoc -q tail
> leading to
> perldoc -f seek
> perldoc -f tell
>
> I'm not getting how to use those functions. Partly because what
> passes for examples in those docs doesn't use normal language,
> instead they use terms like
ahh I am sorry! all my fault!
I didn't see that line and I started searching for the meaning of WHENCE after
the Constants are explained.
oups! Regards.
Martin
On Tue, 11 Dec 2007 14:40:24 -0500
"Chas. Owens" <[EMAIL PROTECTED]> wrote:
> On Dec 11, 2007 2:32 PM, Martin Barth <[EMAIL PROTECTED
On Dec 11, 2007 2:32 PM, Martin Barth <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Dec 2007 14:28:01 -0500
> "Chas. Owens" <[EMAIL PROTECTED]> wrote:
>
> > The seek function has three ways of measuring what the second argument
> > means:
> > 0: move relative the beginning of the file
> > 1: move relati
On Tue, 11 Dec 2007 14:28:01 -0500
"Chas. Owens" <[EMAIL PROTECTED]> wrote:
> The seek function has three ways of measuring what the second argument means:
> 0: move relative the beginning of the file
> 1: move relative to the current position in the file
> 2: move relative to the end of the file
On Dec 11, 1:22 pm, [EMAIL PROTECTED] wrote:
> Using perldoc -q tail
> leading to
> perldoc -f seek
> perldoc -f tell
>
> I'm not getting how to use those functions.
There's a lot of things you're not getting, actually...
>for (;;) {
>for ($curpos = tel
On Dec 11, 2007 2:28 PM, Chas. Owens <[EMAIL PROTECTED]> wrote:
snip
> Whence is actually proper English. You may not here it often, but
snip
Hear, not here. See what I mean about declining standards?
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTE
On Dec 11, 2007 1:22 PM, <[EMAIL PROTECTED]> wrote:
> Using perldoc -q tail
> leading to
> perldoc -f seek
> perldoc -f tell
>
> I'm not getting how to use those functions. Partly because what
> passes for examples in those docs doesn't use normal language, instead
> they use terms like WHENCE, s
i hope i can clarify what whence means:
snip
For WHENCE you may use the constants "SEEK_SET", "SEEK_CUR", and
"SEEK_END" (start of the file, current position, end of the file)
from the Fcntl module.
snip
whence descripes from where you start counting bytes:
if you use "SE
21 matches
Mail list logo
