Thanks, Tux, for Text:CSV. It keeps coming in handy both directly and indirectly.

I have a question about escaped quotes in incoming files. I would have expected the output for the three data lines below to be identical, but the second line misses the escaped single quote. Is an escaped single quote some kind of faux pax or even a mistake within the data or would it be one in something which Text::CSV draws on?

#!/usr/bin/perl

use Text::CSV qw(csv);

use strict;
use warnings;

my $csv = Text::CSV->new ({ binary => 1, auto_diag => 1 });
my $o = \*STDOUT;

# Read/parse CSV
while (my $row = $csv->getline (\*DATA)) {
    my @selected = ( splice(@{$row}, 0, 2), splice(@{$row}, -6, 2) );
    $csv->say($o, \@selected);
}

exit(0);

__DATA__ 
8, 9, NULL, 'Filler', '555-999', '77:88', 0, 0, 0, 0
8, 9, NULL, 'Filler', '555-999', '77:88', 'A \' B , C', 0, 0, 0
8, 9, NULL, 'Filler', '555-999', '77:88', 0, 0, 0, 0
[download]

This is based on something found in the wild.

SELECT db1.artist.name, db2.painting.title
  FROM db1.artist INNER JOIN db2.painting
  ON db1.artist.a_id = db2.painting.a_id;
[download]

which is similar to my application requirements. I can use DBI of course to connect to db1. And make ANOTHER connection to db2. But then I need to "prepare" - which needs a database connection. How can I create a handle connected to TWO databases as this statement requires? Maybe:

$db1->$db2->prepare( $query );
[download]

Gracias

Is there an easy way to find out when a feature or keyword was introduced to Perl?
In other words, which version introduced it...

I have a module that uses pos, a keyword I infrequently use. How can I find out when this, or any other keyword, was introduced so I can set the minimum required Perl version?

Obviously I could go through each delta until I find it but that seems rather tedious...

Emacs comes with two different major modes to edit Perl code: perl-mode and cperl-mode.

perl-mode is somewhat stuck with the Perl syntax of 5.14, has less features, but a cleaner implementation. cperl-mode is up to date with Perl 5.38 and has deeper understanding of Perl syntax, but a somewhat arcane implementation, most of it written in the previous century.

With all due respect to TIMTOWTDI, maintaining two major modes turns out to be not enough fun in the long run, and last week Stefan Kangas opened a wishlist item to Making perl-mode.el obsolete.

The mail thread shows that some people prefer perl-mode because it is less "colorful" and intrusive than cperl-mode. Therefore, the idea is to enable cperl-mode to (optionally) look like and behave like perl-mode. That way, perl-mode.el can be obsoleted without making those users uncomfortable: perl-mode would continue to exist as a custom theme of cperl-mode.

Users of perl-mode are now encouraged to try cperl-mode, and to report bugs against cperl-mode where they prefer the behavior of perl-mode. This has already started. The "current" cperl-mode.el is available from the repository: cperl-mode.el and is supposed to work with Emacs 26 and newer.

Keep the reports going!

This article also appears on blogs.perl.org.

Edited: Fixed the link to blogs.perl.org. Thanks to hippo for noticing!

I very much appreciate the thorough answers I receive here: they have helped me get reacquainted with Perl. The hardest part I still encounter is to understand what the symbols mean, not so much the concepts.

I'm simply asking for a "better" way to accomplish a task I already can do.

An example: I want to know if there's a way to send just one key & value per array/hash - preferably by reference - to a subroutine. In the example code below, I want to send all and only the {Sub_Name}s and their respective values. The code below works and I've come up with two ways to list the Sub_Name. I'm simply wanting to know if there's a better way to do it, so I don't have to make an array or send the entire array of hashes to the subroutine.

#!/usr/bin/env perl

#use 5.36.1;
use strict;
use warnings;

use Data::Dumper;
use autodie;
use File::Find;
use File::Copy;
use File::Rename;
use feature 'fc';
use File::Path qw( make_path );

my $Wait_Time = 10;    # Implement Time Delay

# Subscription DATA sets
my @Subscription = ( 
     {
     Sub_Name               => "Morph",
     Archive_File           => "Morph Archive.txt",
     },
     {
     Sub_Name               => "Analogue",
     Archive_File           => "Analogue Archive.txt",
     },
     {
     Sub_Name               => "Cat",
     Archive_File           => "Cat Archive.txt",
     },
     {
     Sub_Name               => "Zoonotic",
     Archive_File           => "Zoonotic Archive.txt",
     },
     {
     Sub_Name               => "Hydro",
     Archive_File           => "Hydro Archive.txt",
     },
);

#Subscription of Names
my @Subscription_Names_List;
for (@Subscription) {push @Subscription_Names_List, $_->{Sub_Name};}
List_Subscriptions(\@Subscription_Names_List);


for (@Subscription) {
    Display_Subs(\%$_);
}

sub Display_Subs { 
    my ($my_Sub) = @_;
    print "Testing Subscription to: $my_Sub->{Sub_Name}\n";
    return $my_Sub;
}

sub List_Subscriptions {
    my (@Sub_ARRAY) = @{$_[0]};
#    my (@Sub_ARRAY) = @_;

    print "The Current Subscription List:\n\n";
    for (@Sub_ARRAY) { print " \t$_ \n"; }
    print "\n\n";
}
[download]

Is it better to use a "packaged" easily installable version of Perl such as Strawberry on a Windows OS or to compile a version or there is no practical difference, etc...?

I primarily ask for two reasons: stability and speed. An underlying assumption to both reasons is that compiling code will always be faster, because it will compile based on specific chipsets and its respective native math libraries.

1. Stability. My systems run both AMD CPUs and GPUs. I have wondered if instability in GAMES are sometimes caused by various issues of the binaries being compiled for Intel CPUs and NVidia GPUs. By extension, is there an inherent stability benefit of compiling Perl on a Windows system?

2. Speed. This likely has no real practical value unless one is running a "large" server on Windows; but, I wanted to ask anyway. So, by a similar analogy to GAMES stability, since there is a real benefit to GAMES which have been optimized for either AMD or Intel/NVidia and sometimes specifically a chipset, is there a speed benefit to compiling Perl on Windows?

thanks