On 09/25/2017 09:42 AM, Parrot Raiser wrote:
Have you considered simply "touch"ing the file? That updates the timestamp.
yes.
The way I actually did it forced me to (keep) learn(ing)
how to write and read to files.
A lot of the things I do, I do the hard way so that I am
forced to learn.
I
On Mon, Sep 25, 2017 at 10:49 PM, ToddAndMargo
wrote:
> There is another operating system other than Linux? I
> had heard rumors of that: it is slow, expensive, crashes
> all the time. But I thought is was only a story to frighten
> little children and young programmers.
O> On Mon, Sep 25, 2017 at 10:19 AM, Brandon Allbery > wrote:
On Mon, Sep 25, 2017 at 3:09 AM, Julien Simonet
> wrote:
I think your problem is coming from a (") missing at
On 09/25/2017 06:39 AM, Timo Paulssen wrote:
Second itteration:
#!/usr/bin/env perl6
say "Full file name <$?FILE>";
my $IAm;
my $IAmFrom;
$?FILE ~~ m|(.*\/)(.*)|;
$IAmFrom = $0;
$IAm = $1;
say "IAm <$IAm>";
say "IAmFrom <$IAmFrom>";
Please don't use string
On 09/25/2017 12:51 PM, Parrot Raiser wrote:
ToddAndMargo might save some time by asking "Is this a problem someone
else might have solved, and if so, how?" before plunging ahead and
coding. From this and previous postings, it looks as though the answer
might frequently start with "Yes", and
On Mon, Sep 25, 2017 at 10:23 PM, ToddAndMargo
wrote:
> On 09/25/2017 07:25 AM, Brandon Allbery wrote:
>
>> So as to make this not entirely content-free: I would suggest that the
>> string language note the line on which it sees a bare newline, and if it
>> subsequently
On 09/25/2017 07:25 AM, Brandon Allbery wrote:
So as to make this not entirely content-free: I would suggest that the
string language note the line on which it sees a bare newline, and if it
subsequently hits a syntax error while still parsing that string it
could output something like perl
ToddAndMargo might save some time by asking "Is this a problem someone
else might have solved, and if so, how?" before plunging ahead and
coding. From this and previous postings, it looks as though the answer
might frequently start with "Yes", and would save a lot of redundant
effort.
Have you considered simply "touch"ing the file? That updates the timestamp.
So as to make this not entirely content-free: I would suggest that the
string language note the line on which it sees a bare newline, and if it
subsequently hits a syntax error while still parsing that string it could
output something like perl 5's "Possible runaway multi-line string starting
on
On Mon, Sep 25, 2017 at 3:09 AM, Julien Simonet
wrote:
> I think your problem is coming from a (") missing at line 3.
> At the same line, the semicolon (;) is misplaced : it should be at the end
> if line.
>
It took older perl over a decade to come up with better error
> Second itteration:
>
>
> #!/usr/bin/env perl6
>
> say "Full file name <$?FILE>";
>
> my $IAm;
> my $IAmFrom;
>
> $?FILE ~~ m|(.*\/)(.*)|;
> $IAmFrom = $0;
> $IAm = $1;
> say "IAm <$IAm>";
> say "IAmFrom <$IAmFrom>";
>
Please don't use string functions on paths; doing it
On 09/25/2017 12:22 AM, ToddAndMargo wrote:
On 09/25/2017 12:14 AM, ToddAndMargo wrote:
Le 25 septembre 2017 08:55:59 GMT+02:00, ToddAndMargo
a écrit :
1: #!/usr/bin/env perl6
2:
3: say "Full file name <$?FILE;>
4:
5: my $IAmFrom;
6:
On 09/25/2017 12:14 AM, ToddAndMargo wrote:
Le 25 septembre 2017 08:55:59 GMT+02:00, ToddAndMargo
a écrit :
1: #!/usr/bin/env perl6
2:
3: say "Full file name <$?FILE;>
4:
5: my $IAmFrom;
6: $IAmFrom = $?FILE;
7: $IAmFrom ~~ \.*/||;
Le 25 septembre 2017 08:55:59 GMT+02:00, ToddAndMargo
a écrit :
1: #!/usr/bin/env perl6
2:
3: say "Full file name <$?FILE;>
4:
5: my $IAmFrom;
6: $IAmFrom = $?FILE;
7: $IAmFrom ~~ \.*/||;
8: say "IAmFrom <$IAmFrom>";
$
Hello,
I think your problem is coming from a (") missing at line 3.
At the same line, the semicolon (;) is misplaced : it should be at the end if
line.
I hope I helped :)
Le 25 septembre 2017 08:55:59 GMT+02:00, ToddAndMargo a
écrit :
>
>1: #!/usr/bin/env perl6
>2:
16 matches
Mail list logo