[32288] in Perl-Users-Digest
Perl-Users Digest, Issue: 3555 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Nov 30 00:09:21 2011
Date: Tue, 29 Nov 2011 21:09:05 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 29 Nov 2011 Volume: 11 Number: 3555
Today's topics:
Re: Index position of array item by string match? <rweikusat@mssgmbh.com>
Re: Index position of array item by string match? <tadmc@seesig.invalid>
Re: Index position of array item by string match? <ben@morrow.me.uk>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Problem configuring OS/2 for installing CPAN packag <dave@invalid.invalid>
Re: Problem configuring OS/2 for installing CPAN packag <ben@morrow.me.uk>
Re: Problem configuring OS/2 for installing CPAN packag <dave.r.yeo@gmail.com>
Programing Language: latitude-longitude-decimalize <xahlee@gmail.com>
Re: Programing Language: latitude-longitude-decimalize <thad@thadlabs.com>
Re: Programing Language: latitude-longitude-decimalize <jurgenex@hotmail.com>
Re: Programing Language: latitude-longitude-decimalize <thad@thadlabs.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 29 Nov 2011 10:17:19 +0000
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Index position of array item by string match?
Message-Id: <874nxn6xn4.fsf@sapphire.mobileactivedefense.com>
Ben Morrow <ben@morrow.me.uk> writes:
> Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
>>
>> --------------
>> my $ndx;
>>
>> for (@images) {
>> last if $_ eq $img;
>> ++$ndx;
>> }
>>
>> printf('<a href="display.pl?%s">', $images[$ndx - 1]) if $ndx;
>> printf('<a href="display.pl?%s">', $images[$ndx + 1]) if $ndx < $#images;
>> --------------
>>
>> NB: If you're afraid of pointless warnings, make that my $ndx = 0;
>
> ++ doesn't warn about undef, because that would be irritating.
The second printf statement should generate two of them if $img was
equal to the first image name in the array.
------------------------------
Date: Tue, 29 Nov 2011 08:12:00 -0600
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: Index position of array item by string match?
Message-Id: <slrnjd9q5d.9d9.tadmc@tadbox.sbcglobal.net>
Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
> Tad McClellan <tadmc@seesig.invalid> writes:
>> Tuxedo <tuxedo@mailinator.com> wrote:
>
> [...]
>
>>> # ???
>>> # find the index position of by matching $img string
>>
>>
>> my($i) = grep $img eq $images[$_], 0..$#images;
>
> This is bad because it always compares the input name to all names in
> the array.
Yes, I know.
The best way and the simplest way were mutually exclusive,
so I had to choose one.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Tue, 29 Nov 2011 19:55:01 -0600
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Index position of array item by string match?
Message-Id: <-9udnXm4VedoEUjTnZ2dnUVZ8lKdnZ2d@bt.com>
Quoth Tad McClellan <tadmc@seesig.invalid>:
> Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
> > Tad McClellan <tadmc@seesig.invalid> writes:
> >> Tuxedo <tuxedo@mailinator.com> wrote:
> >
> >>> # ???
> >>> # find the index position of by matching $img string
> >>
> >>
> >> my($i) = grep $img eq $images[$_], 0..$#images;
> >
> > This is bad because it always compares the input name to all names in
> > the array.
>
> Yes, I know.
>
> The best way and the simplest way were mutually exclusive,
> so I had to choose one.
In any case 'best' is a vague term. The grep is simple, easy to
understand, and an obvious solution to anyone familiar with Perl. Under
many circumstances that's 'better' than a more complicated solution that
is marginally more efficient.
Ben
------------------------------
Date: Tue, 29 Nov 2011 02:07:59 -0600
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <8-GdnXcphaxCD0nTnZ2dnUVZ_jydnZ2d@giganews.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Tue, 29 Nov 2011 08:52:43 +0000 (UTC)
From: "Dave Saville" <dave@invalid.invalid>
Subject: Re: Problem configuring OS/2 for installing CPAN packages
Message-Id: <fV45K0OBJxbE-pn2-qDDPCUcmPzXg@localhost>
On Mon, 28 Nov 2011 23:00:53 UTC, "Andy"
<nospam-abwillis1-nopspam@nospam-gmail.com> wrote:
> On Mon, 28 Nov 2011 18:43:16 UTC, Shmuel (Seymour J.) Metz
> <spamtrap@library.lspace.org.invalid> wrote:
>
> > I'm attempting to install a CPAN package for Perl 5.10 under
> > eComStation 2.0 GA, a rebranded OS/2. I took the defaults when I ran
> > 1.1. perl -MCPAN -e "shell". The kLIBC Paths application is mapping
> > /perl and /perl5 to Q:\PROGRAMS\PERL. I get the following messages.
> >
> > [h:\]cdd H:\vendors\cpan\HTML-Tagset-3.20
> > [h:\vendors\cpan\html-tagset-3.20]perl Makefile.PL
> > Have Q:/PROGRAMS/PERL/LIB/5.10.0/os2/Config.pm expected
> > /perl5/lib/5.10.0/os2/Config.pm
> > Your perl and your Config.pm seem to have different ideas about the
> > architecture they are running on.
> > Perl thinks: [os2]
> > Config says: [os2]
> > This may or may not cause problems. Please check your installation
> > of perl
> > if you have problems building this extension.
> > Note (probably harmless): No library found for -lsocket
> > Writing Makefile for HTML::Tagset
> > [h:\vendors\cpan\html-tagset-3.20]Q:\moztools\make.exe
> > make.exe: *** No rule to make target
> > `/perl5/lib/5.10.0/os2/Config.pm', needed by `Makefile'. Stop.
> >
> > I assume that I need to edit a configuration file, but I didn't see
> > anything obvious in the documentation.
> >
> There is an open bug on this issue I believe:
> http://mantis.smedley.info/view.php?id=303
>
I have almost given up on installing stuff from CPAN for OS/2 - Some
packages install, others barf on out of date packages that can't be
updated because they need updated packages that won't install because
the latest version needs updated packages................... The CPAN
module itself being a prime example.
Secondly if the install needs to compile something this always fails
because *your* build environment does not match to the last byte the
one perl was complied with. I have tried and failed to get perl to
compile with my build. One of the problems is the old one of drive
letters and libs being on different drives whereas on *nix everything
is findable under "/".
--
Regards
Dave Saville
------------------------------
Date: Tue, 29 Nov 2011 19:50:33 -0600
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Problem configuring OS/2 for installing CPAN packages
Message-Id: <-9udnX64Ved0FkjTnZ2dnUVZ8lKdnZ2d@bt.com>
Quoth Shmuel (Seymour J.) Metz <spamtrap@library.lspace.org.invalid>:
> In <QIadnRHMSrAkpUnTnZ2dnUVZ8sydnZ2d@bt.com>, on 11/28/2011
> at 07:43 PM, Ben Morrow <ben@morrow.me.uk> said:
>
> >Is this a standard OS/2 build of perl from the perl source,
>
> It's a 5.10.0 build from
> <http://download.smedley.info/perl-5.10.0-os2-20071227.zip>.
OK. That site doesn't seem to say anything about patches applied to
perl, but it does seem to build everything against a libc with some sort
of Cygwin-like Unix emulation layer. Since the perl libraries are
expecting OS/2 to use OS/2 paths (starting with a drive letter) I'm not
sure that is the most helpful thing to do.
> >README.os2 doesn't mention anything about any path remapping.
>
> I believe that 5.8.0 was the last official OS/2 build. I don't know
> whether the path remapping is something that Paul Smedley or whether
> it was in the source.
When you say 'official' do you mean the builds Ilya used to do? There
are no official binary builds of perl (for any platform): the only
release supported by p5p is the source release. If you were on a Unix
system I would at this point be suggesting you install a proper dev
environment and build perl yourself from the source tarball. I don't
know whether that's something you would be able to do, but IME getting
MakeMaker and the CPAN shell to work with pre-packaged binary builds is
a nightmare. There are just too many details of the build environment to
get wrong.
If you do try to build from source, I don't know if the gcc packages
from Paul Smedley are suitable. I understand building perl on OS/2
requires something called 'EMX', which I presume you have, but those gcc
builds seem to be using an additional emulation layer on top of that.
(In Win32 terms, it seems to me Paul is providing the equivalent of
Cygwin when the equivalent of MinGW would probably be better.)
The rest of this is about trying to fix the installation you've got,
assuming you can't build one that works better.
> >is there some way you can invoke it as /perl5/bin/perl (or whatever
> >the proper path is) instead of Q:\PROGRAMS\PERL\BIN\PERL?
>
> Q:\PROGRAMS\PERL\BIN\perl.exe is the actual location[1].
I wasn't clear. I realise that the binary is actually in
q:\programs\perl\bin, however there appear to be some parts of the
system that want to call that directory /perl5/bin. Presumably if you
were to type '/perl5/bin/perl' into cmd.exe it would either complain
about a non-existent binary or about the wrong sort of slashes. Do you
have some other shell, built against kLibc, which *will* let you invoke
perl by that path?
(I've no idea if this will make a difference. I am simply mystified as
to where perl got the path Q:\PROGRAMS\PERL\LIB from, and can only
assume it is starting with the path to the invoked binary and working
back from there.)
For reference, what does 'perl -V' give you? Does the @INC list at the
end have paths under q:\programs\perl or under /perl5?
> >Is this the make used to build that copy of perl?
>
> Probably not. I've got one in U:\extras\bin that may be the one used
> for the build; I'll try it and see what happens.
OK. If your perl is going to write Makefiles with Unix-mapped paths, you
will need a make that understands them. If the Config-editing below
works, you may be able to get perl to write Makefiles with native OS/2
paths, at which point you need to go back to the first make again.
> >....on the other hand, you could try simply editing that copy of
> >Config.pm and globally replacing /perl and /perl5 with
> >Q:/PROGRAMS/PERL.
>
> I've got files by that name in
<snip>
> Is q:\PROGRAMS\PERL\lib\5.10.0\CPAN\Config.pm the right one?
No. That file is for the module CPAN::Config, which is for CPAN
configuration; what we are talking about here is the module Config,
which is a record of the build-time core perl configuration.
> It
> doesn't contain the string /perl, although these do:
>
> q:\Perl\lib\5.8.0\os2\Config.pm
This is left over from a previous installation of perl?
> q:\PROGRAMS\PERL\lib\5.10.0\CPANPLUS\Config.pm
This, similarly, is the module CPANPLUS::Config, for configuring
CPANPLUS. You almost certainly don't care about it.
> q:\PROGRAMS\PERL\lib\5.10.0\os2\Config.pm
This is the file you need to edit; and I've just remembered that Config
uses a delay-loading hack, so you also need to edit
q:\programs\perl\lib\5.10.0\os2\Config_heavy.pl
(sorry, I should've mentioned that before).
> One of the things that puzzles me is that in
>
> > Perl thinks: [os2]
> > Config says: [os2]
>
> the "mismatched" strings are the same.
Yes. That message is extremely unhelpful. The two strings it actually
compared are the 'Have ... expected ...' paths listed on the line before
(which looks to me suspiciously like a debugging statement someone
forgot to take out). It then pulls out the architecture components and
displays them, even if that wasn't the problem.
Unfortunately, MakeMaker is one of the gnarliest parts of the perl
toolchain. Much of it is, frankly, a stinking mess. However, it
(usually) works, and it mustn't be broken, so fixing the mess is slow
and tedious work.
Ben
------------------------------
Date: Tue, 29 Nov 2011 19:32:31 -0800
From: Dave Yeo <dave.r.yeo@gmail.com>
Subject: Re: Problem configuring OS/2 for installing CPAN packages
Message-Id: <4ed5a3e8$0$5506$c3e8da3$eb767761@news.astraweb.com>
Jumping in to try to clarify a few things,
Ben Morrow wrote:
>
> Quoth Shmuel (Seymour J.) Metz<spamtrap@library.lspace.org.invalid>:
>> In<QIadnRHMSrAkpUnTnZ2dnUVZ8sydnZ2d@bt.com>, on 11/28/2011
>> at 07:43 PM, Ben Morrow<ben@morrow.me.uk> said:
>>
>>> Is this a standard OS/2 build of perl from the perl source,
>>
>> It's a 5.10.0 build from
>> <http://download.smedley.info/perl-5.10.0-os2-20071227.zip>.
>
> OK. That site doesn't seem to say anything about patches applied to
> perl, but it does seem to build everything against a libc with some sort
> of Cygwin-like Unix emulation layer. Since the perl libraries are
> expecting OS/2 to use OS/2 paths (starting with a drive letter) I'm not
> sure that is the most helpful thing to do.
Klibc is actually a fork of EMX, understands drive letters fine along
with both types of directory separators.
>
>>> README.os2 doesn't mention anything about any path remapping.
>>
>> I believe that 5.8.0 was the last official OS/2 build. I don't know
>> whether the path remapping is something that Paul Smedley or whether
>> it was in the source.
>
> When you say 'official' do you mean the builds Ilya used to do? There
> are no official binary builds of perl (for any platform): the only
> release supported by p5p is the source release.
5.8.0 is the last build that trivially built out of the box (using EMX)
though I don't think Ilya ever released a 5.8.0.
> If you were on a Unix
> system I would at this point be suggesting you install a proper dev
> environment and build perl yourself from the source tarball. I don't
> know whether that's something you would be able to do, but IME getting
> MakeMaker and the CPAN shell to work with pre-packaged binary builds is
> a nightmare. There are just too many details of the build environment to
> get wrong.
>
> If you do try to build from source, I don't know if the gcc packages
> from Paul Smedley are suitable. I understand building perl on OS/2
> requires something called 'EMX', which I presume you have, but those gcc
> builds seem to be using an additional emulation layer on top of that.
> (In Win32 terms, it seems to me Paul is providing the equivalent of
> Cygwin when the equivalent of MinGW would probably be better.)
As I said, it's a fork with updated headers, updated GCC (which Paul has
updated more) and some stuff removed such as DOS support. Generally it
is quite compatible with EMX but Perl is complex. In the past I tried
building with klibc but don't remember the problems. Personally I still
use 5.8.0 as it was built for my system and works fine including CPAN
(using EMX) last time I tried a few years back.
EMX is really old now, missing a lot of common headers and using GCC 2.8.1
>
> The rest of this is about trying to fix the installation you've got,
> assuming you can't build one that works better.
>
>>> is there some way you can invoke it as /perl5/bin/perl (or whatever
>>> the proper path is) instead of Q:\PROGRAMS\PERL\BIN\PERL?
>>
>> Q:\PROGRAMS\PERL\BIN\perl.exe is the actual location[1].
>
> I wasn't clear. I realise that the binary is actually in
> q:\programs\perl\bin, however there appear to be some parts of the
> system that want to call that directory /perl5/bin. Presumably if you
> were to type '/perl5/bin/perl' into cmd.exe it would either complain
> about a non-existent binary or about the wrong sort of slashes. Do you
> have some other shell, built against kLibc, which *will* let you invoke
> perl by that path?
>
> (I've no idea if this will make a difference. I am simply mystified as
> to where perl got the path Q:\PROGRAMS\PERL\LIB from, and can only
> assume it is starting with the path to the invoked binary and working
> back from there.)
>
> For reference, what does 'perl -V' give you? Does the @INC list at the
> end have paths under q:\programs\perl or under /perl5?
>
>>> Is this the make used to build that copy of perl?
Any recent make should work but it is important to have the MAKESHELL
environment variable set correctly, to (pdk)sh.exe IIRC, not cmd.exe.
Ash.exe might well work as well.
Helps also to have sh.exe in \bin
[...]
Dave
------------------------------
Date: Tue, 29 Nov 2011 14:53:15 -0800 (PST)
From: Xah Lee <xahlee@gmail.com>
Subject: Programing Language: latitude-longitude-decimalize
Message-Id: <a601dea8-c143-4f69-8664-88000340f5af@cu3g2000vbb.googlegroups.com>
fun programing exercise. Write a function =E2=80=9Clatitude-longitude-
decimalize=E2=80=9D.
It should take a string like this: =E3=80=8C"37=C2=B026=E2=80=B236.42=E2=80=
=B3N 06=C2=B015=E2=80=B214.28=E2=80=B3W"=E3=80=8D.
The return value should be a pair of numbers, like this: =E3=80=8C[37.44345
-6.25396]=E3=80=8D.
Feel free to use perl, python, ruby, lisp, etc. I'll post a emacs lisp
solution in a couple of days.
Xah
------------------------------
Date: Tue, 29 Nov 2011 15:50:33 -0800
From: Thad Floryan <thad@thadlabs.com>
Subject: Re: Programing Language: latitude-longitude-decimalize
Message-Id: <4ED56FC9.5020007@thadlabs.com>
On 11/29/2011 2:53 PM, Xah Lee wrote:
> fun programing exercise. Write a function “latitude-longitude-
> decimalize”.
>
> It should take a string like this: 「"37°26′36.42″N 06°15′14.28″W"」.
> The return value should be a pair of numbers, like this: 「[37.44345
> -6.25396]」.
>
> Feel free to use perl, python, ruby, lisp, etc. I'll post a emacs lisp
> solution in a couple of days.
What a waste of time when the following works fine (probably Java):
<http://transition.fcc.gov/mb/audio/bickel/DDDMMSS-decimal.html>
------------------------------
Date: Tue, 29 Nov 2011 17:14:23 -0800
From: Jrgen Exner <jurgenex@hotmail.com>
Subject: Re: Programing Language: latitude-longitude-decimalize
Message-Id: <nq0bd71o9npm5ts9re3p77fq1jsgccbjou@4ax.com>
Thad Floryan <thad@thadlabs.com> wrote:
>On 11/29/2011 2:53 PM, Xah Lee wrote:
Please do not reply to the eternal troll
Thanks
jue
------------------------------
Date: Tue, 29 Nov 2011 18:10:17 -0800
From: Thad Floryan <thad@thadlabs.com>
Subject: Re: Programing Language: latitude-longitude-decimalize
Message-Id: <4ED59089.4000101@thadlabs.com>
On 11/29/2011 5:14 PM, Jrgen Exner wrote:
> Thad Floryan <thad@thadlabs.com> wrote:
>> On 11/29/2011 2:53 PM, Xah Lee wrote:
>
> Please do not reply to the eternal troll
>
> Thanks
Mea culpa, you're correct. I responded only because the subject
is something with which I'm familiar, e.g., one of my posts from
1988 (23 years ago):
<http://groups.google.com/group/sci.math/msg/d6c891302914fd84>
and
<http://groups.google.co.jp/group/sci.math/msg/d6c891302914fd84>
:-)
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 3555
***************************************
