On Tuesday, November 19, 2002, at 01:17 AM, Heather Madrone wrote:
I also got the developer tools unpacked, so the Darwin
shell is starting to look a bit more like home.
One thing about the Shells under OS X -- you have neither csh nor sh!
csh is a link to tcsh and sh a link to bash. zsh is
Hi All,
I've been using mod_ssl with Apache 1.3.x on Mac OS X for a while now,
and it works great. I've had to use gdbm to get it to compile, but that
was okay with me.
Now, however, I'm writing an article about this, and want to try to
eliminate the gdbm dependency in the name of simplicity.
David
[macjerry:/usr/lib]$ otool -vM libSystem.dylib | grep module_name | grep db
module_name = ndbm.So
module_name = db.So
module_name = aliasdb.o
module_name = printerdb.o
Looks like something is there :) Regrettably I don't understand shared
library syntax. Ie how to specify
On Wednesday, November 20, 2002, at 08:06 AM, David Wheeler wrote:
Hi All,
I've been using mod_ssl with Apache 1.3.x on Mac OS X for a
while now, and it works great. I've had to use gdbm to get it
to compile, but that was okay with me.
Now, however, I'm writing an article about this, and
On Tuesday, November 19, 2002, at 04:06 PM, Ken Williams wrote:
Maybe what's required is just to keep mod_ssl from complaining about
-ldbm (i.e. not search for it), and link against libSystem?
According to this document from Apple (entitled ]Inside Mac OS X: UNIX
Porting Guide), libSystem
On Tuesday, November 19, 2002, at 03:35 PM, Jerry LeVan wrote:
[macjerry:/usr/lib]$ otool -vM libSystem.dylib | grep module_name |
grep db
module_name = ndbm.So
module_name = db.So
module_name = aliasdb.o
module_name = printerdb.o
Looks like something is there :) Regrettably I
On Wednesday, November 20, 2002, at 10:50 AM, David Wheeler wrote:
On Tuesday, November 19, 2002, at 04:06 PM, Ken Williams wrote:
Maybe what's required is just to keep mod_ssl from complaining
about -ldbm (i.e. not search for it), and link against
libSystem?
According to this document
I've already encountered a few text file anomalies on OS X. Most GUI
applications
seem to default to Mac-style text files (linefeeds only), but shell
programs such as
vi do not handle Mac-style text files gracefully.
Is perl on the Mac going to care whether source files are Mac-style
or
There is some discussion of this issue in the docs, check out:
perldoc perlport
And page through to a section called Newlines...
I guess the real question I have is does Perl on OS X qualify as MacPerl
or Unix perl ... I defer to the mac os x experts, but would guess Unix perl.
On Wednesday, November 20, 2002, at 01:45 AM, Wiggins d'Anconia wrote:
Heather Madrone wrote:
I've already encountered a few text file anomalies on OS X. Most GUI
applications
seem to default to Mac-style text files (linefeeds only), but shell
programs such as
vi do not handle Mac-style text
Hmm - none of those are 'dbm', though. David, can you show/quote the
page that claimed that dbm was a part of libSystem?
-Ken
On Wednesday, November 20, 2002, at 10:35 AM, Jerry LeVan wrote:
David
[macjerry:/usr/lib]$ otool -vM libSystem.dylib | grep module_name |
grep db
On Wednesday, November 20, 2002, at 10:50 AM, David Wheeler wrote:
On Tuesday, November 19, 2002, at 04:06 PM, Ken Williams wrote:
Maybe what's required is just to keep mod_ssl from complaining about
-ldbm (i.e. not search for it), and link against libSystem?
According to this document
At 16:30 -0800 11/19/02, Heather Madrone wrote:
I've already encountered a few text file anomalies on OS X. Most GUI applications
seem to default to Mac-style text files (linefeeds only),
I think that's returns only for Mac style. Don't be fooled by MPW's and perhaps
MacPerl's redefinition of \n
At 05:55 PM 11/19/2002 -0700, Doug McNutt wrote:
At 16:30 -0800 11/19/02, Heather Madrone wrote:
I've already encountered a few text file anomalies on OS X. Most GUI applications
seem to default to Mac-style text files (linefeeds only),
I think that's returns only for Mac style. Don't be fooled
At 16:30 -0800 19/11/02, Heather Madrone wrote:
I've already encountered a few text file anomalies on OS X. Most GUI
applications seem to default to Mac-style text files (linefeeds
only), but shell programs such as vi do not handle Mac-style text
files gracefully.
Is perl on the Mac going to
An alternative is to read the entire file in (undef $/) and then split
it:
My suggestion is to put some code like this in your script:
local $/ = get_line_ending($fh);
sub get_line_ending {
my $fh = shift;
my $char;
while (read $fh, $char, 1) {
if ($char eq \n) {
seek $fh, 0, 0;
At 19:01 -0800 19/11/02, gene wrote:
An alternative is to read the entire file in (undef $/) and then split it:
My suggestion is to put some code like this in your script:
It's a good solution. Probably for files less than a few hundred k
it makes no difference (since you'll need to read
All,
What is the best method you use to install modules not hosted on CPAN
but need to be available to a group of people who are not too familiar
with Perl per se.
I have some distributions that I want to be able for the user to
basically type 'installer.pl' or 2x-click on it and it use CPAN
18 matches
Mail list logo
