[31382] in Perl-Users-Digest
Perl-Users Digest, Issue: 2634 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Oct 13 09:09:42 2009
Date: Tue, 13 Oct 2009 06:09:07 -0700 (PDT)
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, 13 Oct 2009 Volume: 11 Number: 2634
Today's topics:
Re: Finding directory my perl program was loaded from <jurgenex@hotmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: problem with perl + thread + extension <aotto1968@users.sourceforge.net>
Re: problem with perl + thread + extension <ben@morrow.me.uk>
Re: problem with perl + thread + extension <aotto1968@users.sourceforge.net>
Re: problem with perl + thread + extension <ben@morrow.me.uk>
Re: problem with perl + thread + extension <aotto1968@users.sourceforge.net>
Re: problem with perl + thread + extension <aotto1968@users.sourceforge.net>
Re: regexp assistance <justin.0908@purestblue.com>
Re: regexp assistance <tadmc@seesig.invalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 12 Oct 2009 21:12:02 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Finding directory my perl program was loaded from
Message-Id: <4nu7d55a0v3jui1gvrd96iuaebs3t9etoj@4ax.com>
[comp.lang.perl has been rm-grouped some 15 years ago. If your ISP still
carries this instead of comp.lang.perl.* you should wonder what else you
are missing.]
[x-post and f'up to comp.lang.perl.misc]
Joe Green <joe.green@hmtown.com> wrote:
>I will put my template file in the same directory that my perl program was loaded from. Is there a reasonable way to determine this directory?
See the second and following parts of "perldoc -q directory":
"How do I add the directory my program lives in"
>Then internally I will (if I get a little help) access "fullPath...template.txt". Until I find out how to do this that line from my patch file will read like . . .
>
>Perl "fullPath...xlate.pl" "fullPath...translate.txt" user.asm >temp.asm
If you don't call the perl interpreter explicitely but just use
"fullPath...xlate.pl ..." then you should find the full path in $0.
Extracting the directory from $0 is trivial using functions from
File::Basename
>I would prefer to not use path environment settings.
Well, $ENV{PATH} does play a major role in deciding which executables to
use, so you cannot just ignore it.
jue
------------------------------
Date: Tue, 13 Oct 2009 02:25:03 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <O7idnWCmeufStknXnZ2dnUVZ_oednZ2d@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.noitatibaher\100cmdat/"
------------------------------
Date: Tue, 13 Oct 2009 09:56:53 +0200
From: Andreas Otto <aotto1968@users.sourceforge.net>
Subject: Re: problem with perl + thread + extension
Message-Id: <hb1bs5$ea4$03$1@news.t-online.com>
Hi,
The problem is solved ...
the method reference from:
>>>>>>>>>>>>>>>>>>>>><
static enum MqErrorE
ProcCall (
struct MqS * const context,
MQ_PTR const data
)
{
dSP;
SV * method = (SV*) data;
enum MqErrorE ret = MQ_OK;
ENTER;
SAVETMPS;
PUSHMARK(SP);
XPUSHs((SV*)context->self);
PUTBACK;
call_sv (method, G_SCALAR|G_DISCARD|G_EVAL);
^^^^^^^^^^^^^^^^^^^ the "method" ^^^^^^^^^^^^^^^^^^^^^^^
ret = ProcError (aTHX_ context, ERRSV);
FREETMPS;
LEAVE;
return ret;
}
<<<<<<<<<<<<<<<<<<<<<
point to the "old" interpreter ... In Fact I call this a
libmsgque bug because the "copyConstructor" for
this sub-ref is not available in the public perl-api.
all other languages have a "copyConstructor" and so
the libmsgque code was to throw away the "right" values
from the "objectConstructor" and use the "copyConstructor"
to set this value to the new value.
now libmsgque check if this value was already set in the
"objectConstructor" and do !!not!! use the "copyConstructor"
(this one not exit in the public perl API) to set it again.
mfg
Andreas Otto
------------------------------
Date: Tue, 13 Oct 2009 09:26:44 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: problem with perl + thread + extension
Message-Id: <47qdq6-u213.ln1@osiris.mauzo.dyndns.org>
Quoth Andreas Otto <aotto1968@users.sourceforge.net>:
> Hi,
>
> The problem is solved ...
>
> the method reference from:
>
> >>>>>>>>>>>>>>>>>>>>><
> static enum MqErrorE
> ProcCall (
> struct MqS * const context,
> MQ_PTR const data
> )
> {
> dSP;
> SV * method = (SV*) data;
> enum MqErrorE ret = MQ_OK;
>
> ENTER;
> SAVETMPS;
>
> PUSHMARK(SP);
> XPUSHs((SV*)context->self);
> PUTBACK;
>
> call_sv (method, G_SCALAR|G_DISCARD|G_EVAL);
>
> ^^^^^^^^^^^^^^^^^^^ the "method" ^^^^^^^^^^^^^^^^^^^^^^^
You do realise this isn't actually a method call, don't you? You need
G_METHOD for that.
> point to the "old" interpreter ... In Fact I call this a
> libmsgque bug because the "copyConstructor" for
> this sub-ref is not available in the public perl-api.
You can use sv_dup to copy SVs from one interpreter to another (is this
what you mean by 'copyConstructor'?). You call it in the context of the
new interpreter.
Ben
------------------------------
Date: Tue, 13 Oct 2009 10:50:40 +0200
From: Andreas Otto <aotto1968@users.sourceforge.net>
Subject: Re: problem with perl + thread + extension
Message-Id: <hb1f10$kdr$03$1@news.t-online.com>
Ben Morrow wrote:
>
> Quoth Andreas Otto <aotto1968@users.sourceforge.net>:
>> Hi,
>>
>> The problem is solved ...
>>
>> the method reference from:
>>
>> >>>>>>>>>>>>>>>>>>>>><
>> static enum MqErrorE
>> ProcCall (
>> struct MqS * const context,
>> MQ_PTR const data
>> )
>> {
>> dSP;
>> SV * method = (SV*) data;
>> enum MqErrorE ret = MQ_OK;
>>
>> ENTER;
>> SAVETMPS;
>>
>> PUSHMARK(SP);
>> XPUSHs((SV*)context->self);
>> PUTBACK;
>>
>> call_sv (method, G_SCALAR|G_DISCARD|G_EVAL);
>>
>> ^^^^^^^^^^^^^^^^^^^ the "method" ^^^^^^^^^^^^^^^^^^^^^^^
>
> You do realise this isn't actually a method call, don't you? You need
> G_METHOD for that.
G_METHOD is not in the public perl api -> this was the reason
I don't use it for me I only use sub-ref and it works
public is "call_method" but this does not accept references
>
>> point to the "old" interpreter ... In Fact I call this a
>> libmsgque bug because the "copyConstructor" for
>> this sub-ref is not available in the public perl-api.
>
> You can use sv_dup to copy SVs from one interpreter to another (is this
yes I check for sv_dup but this is again not part of the public perl API
and it is not documented
> what you mean by 'copyConstructor'?). You call it in the context of the
> new interpreter.
copyConstructor:
1. I have a sub-ref in interpreter one
2. I use perl_clone to get a new interpreter
3. I want to use the sub-ref from 1. in the new interpreter
my solution right now you have to define all "callbacks"
in the object constructor
this is OK and as close as possible to the "interface" programming template
of C++, JAVA and C#
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
package Server;
use base qw(MqS);
...
sub ServerSetup {
my $ctx = shift;
...
}
...
sub new {
my $class = shift;
my $ctx = $class->SUPER::new(@_);
$ctx->ConfigSetName("server");
$ctx->ConfigSetServerSetup(\&ServerSetup);
$ctx->ConfigSetServerCleanup(\&ServerCleanup);
$ctx->ConfigSetFactory(
sub {
new Server()
}
);
return $ctx;
}
...
package main;
our $srv = new Server();
eval {
$srv->LinkCreate(@ARGV);
$srv->ProcessEvent({wait => "FOREVER"});
};
if ($@) {
$srv->ErrorSet($@);
}
$srv->Exit();
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> Ben
------------------------------
Date: Tue, 13 Oct 2009 12:18:14 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: problem with perl + thread + extension
Message-Id: <m84eq6-dm.ln1@osiris.mauzo.dyndns.org>
Quoth Andreas Otto <aotto1968@users.sourceforge.net>:
> Ben Morrow wrote:
> > Quoth Andreas Otto <aotto1968@users.sourceforge.net>:
> >>
> >> call_sv (method, G_SCALAR|G_DISCARD|G_EVAL);
> >>
> >> ^^^^^^^^^^^^^^^^^^^ the "method" ^^^^^^^^^^^^^^^^^^^^^^^
> >
> > You do realise this isn't actually a method call, don't you? You need
> > G_METHOD for that.
>
> G_METHOD is not in the public perl api -> this was the reason
> I don't use it for me I only use sub-ref and it works
OK. G_METHOD has been there since 2000, so I doubt it's going anywhere,
but sticking carefully to the public API is still a good idea. As long
as you realise that this call is
$subref->($object);
rather than
$object->method;
In your place I would probably allow the user to pass in a string as
well, and choose call_sv or call_method based on what type of SV I got.
> >> point to the "old" interpreter ... In Fact I call this a
> >> libmsgque bug because the "copyConstructor" for
> >> this sub-ref is not available in the public perl-api.
> >
> > You can use sv_dup to copy SVs from one interpreter to another (is this
>
> yes I check for sv_dup but this is again not part of the public perl API
> and it is not documented
I agree it's not documented, but if you check
http://perl5.git.perl.org/perl.git/blob/HEAD:/embed.fnc you will find
ApR |SV* |sv_dup |NULLOK const SV *const sstr|NN
CLONE_PARAMS *const param
where the initial 'A' means this is a public API function. I suspect the
lack of documentation is simply an oversight.
If you have questions about what is and isn't a supported part of the
API, you can take them to perl5-porters@perl.org: actually, if you have
questions about using the more advanced parts of the perl API, you will
probably find more people there who know about them than you will here.
> package Server;
> use base qw(MqS);
I will point out again that you should probably avoid top-level
namespaces, and you certainly should if you are thinking of uploading
your code to CPAN at some point. (You should, of course, be thinking of
uploading your code to CPAN, unless it's proprietary :).)
Ben
------------------------------
Date: Tue, 13 Oct 2009 14:19:50 +0200
From: Andreas Otto <aotto1968@users.sourceforge.net>
Subject: Re: problem with perl + thread + extension
Message-Id: <hb1r9g$dgv$03$1@news.t-online.com>
Ben Morrow wrote:
>
> Quoth Andreas Otto <aotto1968@users.sourceforge.net>:
>> Ben Morrow wrote:
>> > Quoth Andreas Otto <aotto1968@users.sourceforge.net>:
>> >>
>> >> call_sv (method, G_SCALAR|G_DISCARD|G_EVAL);
>> >>
>> >> ^^^^^^^^^^^^^^^^^^^ the "method" ^^^^^^^^^^^^^^^^^^^^^^^
>> >
>> > You do realise this isn't actually a method call, don't you? You need
>> > G_METHOD for that.
>>
>> G_METHOD is not in the public perl api -> this was the reason
>> I don't use it for me I only use sub-ref and it works
>
> OK. G_METHOD has been there since 2000, so I doubt it's going anywhere,
> but sticking carefully to the public API is still a good idea. As long
> as you realise that this call is
>
> $subref->($object);
>
> rather than
>
> $object->method;
>
> In your place I would probably allow the user to pass in a string as
> well, and choose call_sv or call_method based on what type of SV I got.
well "man perl_call" -> "Using call_sv ..." says something about this:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><
Because we are using an SV to call fred the following can all be used
CallSubSV("fred");
CallSubSV(\&fred);
$ref = \&fred;
CallSubSV($ref);
CallSubSV( sub { print "Hello there\n" } );
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
you see "call_sv" already covers all kind of possibilities
>
>> >> point to the "old" interpreter ... In Fact I call this a
>> >> libmsgque bug because the "copyConstructor" for
>> >> this sub-ref is not available in the public perl-api.
>> >
>> > You can use sv_dup to copy SVs from one interpreter to another (is this
>>
>> yes I check for sv_dup but this is again not part of the public perl API
>> and it is not documented
>
> I agree it's not documented, but if you check
> http://perl5.git.perl.org/perl.git/blob/HEAD:/embed.fnc you will find
>
> ApR |SV* |sv_dup |NULLOK const SV *const sstr|NN
> CLONE_PARAMS *const param
but I still not know what to do with the last parameter...CLONE_PARAMS
-> what to fill in
>
> where the initial 'A' means this is a public API function. I suspect the
> lack of documentation is simply an oversight.
>
> If you have questions about what is and isn't a supported part of the
> API, you can take them to perl5-porters@perl.org: actually, if you have
> questions about using the more advanced parts of the perl API, you will
> probably find more people there who know about them than you will here.
>
>> package Server;
>> use base qw(MqS);
>
this is not all of my code the "toplevel" package called "perlmsgque"
from the start
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
use strict;
use Switch;
use perlmsgque;
...
package Server;
use base qw(MqS);
...
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
"MqS" (this is from me) and is just a "subpackage" of "perlmsgque"
(this is also from me)
the package "Server" is a synonym for a "end-user" package
I use this name for testing only
the full name is "perlmsgque::MqS"
> I will point out again that you should probably avoid top-level
> namespaces, and you certainly should if you are thinking of uploading
> your code to CPAN at some point. (You should, of course, be thinking of
> uploading your code to CPAN, unless it's proprietary :).)
>
> Ben
------------------------------
Date: Tue, 13 Oct 2009 14:50:50 +0200
From: Andreas Otto <aotto1968@users.sourceforge.net>
Subject: Re: problem with perl + thread + extension
Message-Id: <hb1t3a$3k3$02$1@news.t-online.com>
right now I have a more serious problem:
as opposite to "FactoryCreate" I have a "FactoryDelete" too
>>>>>>>>>>>>>>>>>>>>>>>
static void FactoryDelete (
struct MqS * context,
MQ_BOL doFactoryCleanup,
MQ_PTR data
) {
enum MqStatusIsE statusIs = context->statusIs;
PerlInterpreter *itp = context->threadData;
if (statusIs & MQ_STATUS_IS_THREAD) {
PERL_SET_CONTEXT(itp);
perl_destruct (itp);
PERL_SET_CONTEXT(itp);
perl_free (itp);
} else {
SvREFCNT_dec((SV*)context->self);
}
}
<<<<<<<<<<<<<<<<<<<<<<<<<
now the problem :
"perl_destruct" delete all objects even the
ones from the "original" interpreter copied
into the new interpreter using "perl_clone"
for me every object is linked to a pointer
of type "struct MqS" from "libmsgque"
now shutdown of interpreter "1" delete the
"libmsgque" objects belonging to the original interpreter "0"
too => not good :-(
mfg
Andreas Otto
------------------------------
Date: Tue, 13 Oct 2009 12:11:35 -0000
From: Justin C <justin.0908@purestblue.com>
Subject: Re: regexp assistance
Message-Id: <5268.4ad46e77.aede@zem>
On 2009-10-12, mike <mikaelpetterson@hotmail.com> wrote:
> Is \z not to match at the end of a string?
No, $ matches end of string. /^string$/
Justin.
--
Justin C, by the sea.
------------------------------
Date: Tue, 13 Oct 2009 07:45:02 -0500
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: regexp assistance
Message-Id: <slrnhd8sm9.itd.tadmc@tadmc30.sbcglobal.net>
Justin C <justin.0908@purestblue.com> wrote:
> On 2009-10-12, mike <mikaelpetterson@hotmail.com> wrote:
>> Is \z not to match at the end of a string?
>
> No, $ matches end of string. /^string$/
Yes, \z matches end of string.
$ matches end of string or before a newline at end of string.
---------------
#!/usr/bin/perl
use warnings;
use strict;
$_ = "matches end of string\n";
print "matched dollar\n" if /string$/;
print "matched z\n" if /string\z/;
chomp;
print "matched z 2\n" if /string\z/;
---------------
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
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 2634
***************************************
