0 and mine.
One of these days I'll get around to working on the safe_spawn changes, but
so far I don't know when.
Thanks,
Michael Downey
't had any
time to try to convert things over to use the C RTL yet so I don't know if
this is a problem with the LIB$SPAWN code or something else.
Thanks,
Michael Downey
ed to
be changed then I probably can handle this task. Also I'm not too sure what
defines we have to determine the version of VMS we are on. If I could do
something like:
if (VMS_VERSION > 7.3)
{
all the changes needed to do this
}
else
{
normal stuff
}
Then I think I could put these changes in.
Michael Downey
rks correctly under 5.8. I regrettably haven't been able to
test this using the very latest Perl so if someone could do a quick test
that would be much appreciated. I am currently running my test on VMS 7.3-1
using the latest DEC C compiler. I've tested on both 5.8.0 and 5.8.1 of
Perl.
Michael Downey
"Mark Berryman" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Michael Downey wrote:
> >
> > Mark Berryman replied after this but I don't add it here as my mail
viewer
> > blocked his attachment. But his argument was that it should be u
"Craig A. Berry" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> At 11:25 AM -0700 11/7/03, Michael Downey wrote:
> >The limitation I believe you are talking about is the transmit and
receive
> >buffer sizes for the socket. These generally can&
for VMS.
If you have a different understanding of how that works please let me know
as I currently use this information in an abstraction layer that we use for
both UNIX and VMS.
Michael Downey
ely isn't and would need to be fixed. I can't
remember if there was any documentation about this limitation but we phoned
Compaq, now HP, on the problem and that was their response. They weren't
sure whether they were going to fix the problem in a later release.
Michael Downey
"Sebastian Bazley" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> When VMS Perl (5.5-3A3) opens files, it uses the C RTL open(), which
> defaults to exclusive mode, even for read.
>
> This means that Perl cannot read files that are open for write, even if
the
> writer specified that
"Karol Zielonko" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> --
-
>
> I need to invoke a perl script (SPAMASSASSIN FWIW) from a C program with
command
> line parameters and input and output re-direction. Curre
se. I'd perfer not to use popen for
the system call as popen may require a bit more work to get it to work
correctly. The system() call keeps us from having to manage the I/O and
process startup and cleanup. If there is another reason for using popen
instead please let me know. Also there currently is a system() hook in
PP_SYS.C which would make sense if it called system() but it doesn't, anyone
know why?
Hopefully that all makes sense,
Michael Downey
't who maintains that file. I'll gladly make
the changes but would prefer to have someone who knows the over code to do
it as I wouldn't know what affects what.
If someone would give me a good idea of where to start then I'd be happy to
make some changes and test it out. Either that or if we know what we should
change VMSPIPE.COM to I'll gladly add the code in and test it.
Michael Downey
OUTPUT and
SYS$ERROR of all other programs and DCL scripts. Actually I wonder if we
could use decc$set_child_standard_streams() to solve our problem. Instead
of using VMSPIPE.COM we might be able to make the call to
decc$set_child_standard_streams() before the lib$spawn and it might work. I
don't know when I'd be able to work on this but if I get a chance I'll give
it a try.
Hope that makes sense,
Michael Downey
perl_popen_out'
> $! --- build command line to get max possible length
> [eop]
>
>From my initial testing this looks to work correctly with just this change.
I have pulled out my code in VMS.C and added this into the VMSPIPE.COM as
well as in the code in VMS.C that builds the temporary files if it can't
find VMSPIPE.COM.
Michael Downey
MegaSys Computer Technologies
"Craig A. Berry" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> At 11:41 AM -0600 5/29/03, Michael Downey wrote:
>
> >You shouldn't have to set up mailbox piping because the system() call is
a
> >blocking call. Therefore, any shari
a large part of what makes Perl so great.
> And the test suite doesn't really test these things very well, IMO.
> --
> Chuck Lane [EMAIL PROTECTED]
I agree, possibly creating a new test for these issues should be looked at.
I'm hoping for more input on this problem as I have just recently started
looking into the guts of VMS Perl. I have programmed on VMS extensively but
would think that others would be more familiar with the VMS code. Right now
we only have systems running 7.2 or better and we likely will be moving
everything to 7.3-1 as it seems to have the best support for threads and the
C RTL. So testing on earlier versions is a bit hard for me.
Thanks a lot for your info, especially on the LIB$GET_LOGICAL problem as it
wasn't making too much sense to me.
Michael Downey
MegaSys Computer Technologies
ompiling perl with just the standard configure and all
the tests passed except for the few known tests that don't. If anyone could
verify that I'm not out to lunch that would be much appreciated. Also if
anyone would know what lib$get_logical puts in the first 4 characters of the
array that would also be helpful.
Thanks,
Michael Downey
MegaSys Computer Technologies
17 matches
Mail list logo
