-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, November 24, 2002, at 05:21 PM, Ken Williams wrote:
On Monday, November 25, 2002, at 07:34 AM, Heather Madrone wrote:
Administrivia question: I'm getting a lot of duplicate responsese
because the Reply-to on the list is set to
On Monday, November 25, 2002, at 07:34 AM, Heather Madrone wrote:
Administrivia question: I'm getting a lot of duplicate responsese
because the Reply-to on the list is set to sender. On moderated
lists, this can be a good idea because the approval cycle causes
a lag between posting and mail
On Mon, Nov 25, 2002 at 02:43:46AM +0900, Dan Kogai wrote:
On Monday, Nov 25, 2002, at 01:05 Asia/Tokyo, Chris Nandor wrote:
The bottom line was that it'd be nice to have a PerlIO filter for perl
5.8.x, so that MacPerl can execute Unix and Windows text files, and
Mac OS X
perl can execute
Chris Nandor [EMAIL PROTECTED] writes:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Dan Kogai) wrote:
On Monday, Nov 25, 2002, at 01:05 Asia/Tokyo, Chris Nandor wrote:
The bottom line was that it'd be nice to have a PerlIO filter for perl
5.8.x, so that MacPerl can execute Unix
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Slaven Rezic) wrote:
Could this be made even more generic, but translating to \n instead of \012?
Or use source filters:
package Filter::Any2Unix;
Any2Native?
use Filter::Util::Call;
sub import {
if ($^O ne 'MacOS') {
#?
Chris Nandor [EMAIL PROTECTED] wrote:
That shouldn't work. By the time you get to it in the script, if you have a
#! line, then the entire script is one long comment, and the use() line
won't ever be executed.
That would be an argument for allowing -M/-m on the #! line.
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Heather Madrone) wrote:
At 11:05 AM 11/24/2002 -0500, Chris Nandor wrote:
But back to the point: there's been some discussion in this threa on
workarounds, but my personal feeling is that this is a bug, or at best a
broken feature, in perl.
On Mon, Nov 25, 2002 at 02:33:45PM +0100, Rafael Garcia-Suarez wrote:
Chris Nandor [EMAIL PROTECTED] wrote:
That shouldn't work. By the time you get to it in the script, if you have a
#! line, then the entire script is one long comment, and the use() line
won't ever be executed.
On Monday, November 25, 2002, at 02:09 PM, Chris Nandor wrote:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Slaven Rezic) wrote:
Could this be made even more generic, but translating to \n instead of
\012?
Or use source filters:
package Filter::Any2Unix;
Any2Native?
When I had
This Perl newbie needs a little advanced help. I'm trying a new
Login Hook to start classic, I made the Perl script out of an
Applescript. However, and probably not surprising to you, it did not
work.
It does work in the Applescript but I would prefer to make Perl for use
in a hook.
Hi Chuck,
Try this:
---
#!/usr/bin/perl
my $status = `open -a /System/Library/CoreServices/Classic Startup.app`;
---
I don't know what this means, though:
../cdTruBlueEnvironment;
Are you trying to cd into that dir?
Cheers,
Troy
This Perl newbie needs a little advanced help. I'm trying a
Thanks Troy,
The CD was a problem but not entirely, some of my close but not perfect
scripts did not contain the cdTruBlueEnvironment; statement. It's amazing
how you look at something a thousand times and never see something until
someone points it out.
TruBlueEnvironment is inside of the
On Monday, November 25, 2002, at 08:50 AM, Chris Nandor wrote:
While they're at it, they might drop file resource forks.
Again, they essentially have. They are still supported because, as
with the
CR issue, they cannot just abandon them. But most apps do not have
them;
instead, the resource
The apreq developers are planning a maintenance release of
libapreq-1.1. This version does not include support for
modperl-2, but it does address some outstanding problems in
1.0:
* OS X support
* perl 5.8 segfaults related to file uploads.
Please give the tarball at
On Monday, November 25, 2002, at 03:27 PM, William H. Magill wrote:
On Monday, November 25, 2002, at 08:50 AM, Chris Nandor wrote:
While they're at it, they might drop file resource forks.
Again, they essentially have. They are still supported because, as
with the
CR issue, they cannot
Hi Joe APReq,
I'm glad this is receiving attention, Apache::Request has had
some trouble on OS X as I'm sure you're aware. I just tested
the RC, using:
perl 5.6.1
Apache/1.3.26 (as shipped with the OS, uses dso)
OS X 10.1.5
and I get this error in 'make test':
dyld: t/httpd multiple
http://search.cpan.org/author/COOK/Device-SerialPort-0.12/SerialPort.pm
This would be handy (for me) but it doesn't build on OSX, no doubt
because IOKit's interface is different from POSIX/Linux style device
control.
I do have a couple pieces of sample source for talking to serial
Rob,
I got it to compile on 10.2, but I had to do some tweaks. I'm using it
to talk to serial port on a keyspan usb-serial device, and also in a imac
with a stealthport, works great. I used version 0.7 tho, and I'd have to
get it down to do a diff. If your interested, I can send you the
On Tuesday, November 26, 2002, at 12:22 PM, Joe Schaefer wrote:
Ken Williams [EMAIL PROTECTED] writes:
[...]
I've attached the full output.
Thanks, Ken. I looked over the result, but didn't see any
indication that you used the ./configure - make - make install
instructions from the web
At 13:51 + 25/11/02, Nicholas Clark wrote:
On Mon, Nov 25, 2002 at 02:33:45PM +0100, Rafael Garcia-Suarez wrote:
Chris Nandor [EMAIL PROTECTED] wrote:
That shouldn't work. By the time you get to it in the script,
if you have a
#! line, then the entire script is one long comment, and
On Tuesday, November 26, 2002, at 12:49 PM, Peter N Lewis wrote:
At 13:51 + 25/11/02, Nicholas Clark wrote:
On Mon, Nov 25, 2002 at 02:33:45PM +0100, Rafael Garcia-Suarez wrote:
Chris Nandor [EMAIL PROTECTED] wrote:
That shouldn't work. By the time you get to it in the
script, if
On Monday, November 25, 2002, at 10:09 PM, Ken Williams wrote:
There's nothing perl can do about this - the OS (in fact, the kernel,
I think) reads that shebang line in order to know it should call perl.
By the time perl gets to look at it, it's too late.
Kernel not involved. Shell looks
On Tuesday, November 26, 2002, at 03:38 PM, Chris wrote:
On Monday, November 25, 2002, at 10:09 PM, Ken Williams wrote:
There's nothing perl can do about this - the OS (in fact, the
kernel, I think) reads that shebang line in order to know it
should call perl. By the time perl gets to
At 15:09 +1100 26/11/02, Ken Williams wrote:
On Tuesday, November 26, 2002, at 12:49 PM, Peter N Lewis wrote:
But is there any reason the # comments are not terminated by the
first occurrence of *either* \012 or \015?
There's nothing perl can do about this - the OS (in fact, the
kernel, I
On Monday, November 25, 2002, at 11:20 PM, Ken Williams wrote:
On Tuesday, November 26, 2002, at 03:38 PM, Chris wrote:
On Monday, November 25, 2002, at 10:09 PM, Ken Williams wrote:
There's nothing perl can do about this - the OS (in fact, the
kernel, I think) reads that shebang line in
On Tuesday, November 26, 2002, at 04:40 PM, Chris wrote:
On Monday, November 25, 2002, at 11:20 PM, Ken Williams wrote:
On Tuesday, November 26, 2002, at 03:38 PM, Chris wrote:
On Monday, November 25, 2002, at 10:09 PM, Ken Williams wrote:
There's nothing perl can do about this - the OS
On Tuesday, November 26, 2002, at 01:38 AM, Ken Williams wrote:
On Tuesday, November 26, 2002, at 04:40 PM, Chris wrote:
On Monday, November 25, 2002, at 11:20 PM, Ken Williams wrote:
On Tuesday, November 26, 2002, at 03:38 PM, Chris wrote:
On Monday, November 25, 2002, at 10:09 PM,
27 matches
Mail list logo
