In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Derek Hansen) wrote:
Two days ago I attempted to upgrade Perl to 5.8.0 following the
instructions on Apple's web site. Ever since then I have been getting
dyld errors. I read the perldelta FAQ which mentions a solution for OS
X, but even
hi
i tried the active state visual debugger the other day and found it
extremely easy and rather convenient to use. does anyone know of a
similar product that works under os x ?
./allan
allan wrote:
hi
i tried the active state visual debugger the other day and found it
extremely easy and rather convenient to use. does anyone know of a
similar product that works under os x ?
./allan
try mozilla's venkman
allan wrote:
hi
i tried the active state visual debugger the other day and found it
extremely easy and rather convenient to use. does anyone know of a
similar product that works under os x ?
./allan
what was I thinking... venkman is for Javascript. sorry.
mi, the Japanese editor I posted
Am Montag, 06.01.03 um 21:01 Uhr schrieb Puneet Kishor:
allan wrote:
hi
i tried the active state visual debugger the other day and found it
extremely easy and rather convenient to use. does anyone know of a
similar product that works under os x ?
./allan
try mozilla's venkman
I use ptkdb,
Hi,
I upgraded to Jaguar this weekend and was annoyed to find that
Terminal.app had screwed up the horizontal font spacing in my setup.
I'm no font layout snob, but for some reason this was really annoying -
using Monaco 9, there was a column of pixels missing between columns 1
and 2 of
On 1/6/03 4:15 PM, Ken Williams wrote:
What finally worked was to add the following to any of my .term files,
and to ~/Library/Preferences/com.apple.Terminal.plist :
keyFontWidthSpacing/key
string1.002/string
Hm, doesn't work for me. Also, my plist files have the value in
On Monday, January 6, 2003, at 03:48 PM, John Siracusa wrote:
On 1/6/03 4:40 PM, John Siracusa wrote:
On 1/6/03 4:15 PM, Ken Williams wrote:
What finally worked was to add the following to any of my .term
files,
and to ~/Library/Preferences/com.apple.Terminal.plist :
I'm writing a little toy tool to teach myself more Perl than I have
used before, and I am puzzled by error messages I get when trying to
run and debug it:
syntax error at ./nudice-01c line 187, near sub displayResults
syntax error at ./nudice-01c line 305, near sub rollRequest
syntax error at
In a message dated Mon, 6 Jan 2003, Christopher D. Lewis writes:
Any ideas how I debug lines which don't exist? Any ideas why Perl is
reporting nonexistent line numbers? Perl 5.8.0.
What modules are you using? If you're using any source filters, line
numbers will be incorrect.
Trey
--
syntax error at ./nudice-01c line 187, near sub displayResults
syntax error at ./nudice-01c line 305, near sub rollRequest
The problem is, you see, that (according to two different text editors)
nudice-01c has only 304 lines
Line numbers aside, you can find sub rollRequest, cancha?
On Monday, Jan 6, 2003, at 15:34 US/Pacific, Christopher D. Lewis wrote:
I'm writing a little toy tool to teach myself more Perl than I have
used before, and I am puzzled by error messages I get when trying to
run and debug it:
syntax error at ./nudice-01c line 187, near sub displayResults
On Monday, January 6, 2003, at 06:39 PM, Andy Lester wrote:
syntax error at ./nudice-01c line 187, near sub displayResults
syntax error at ./nudice-01c line 305, near sub rollRequest
The problem is, you see, that (according to two different text
editors)
nudice-01c has only 304 lines
On Monday, January 6, 2003, at 06:49 PM, Christopher D. Lewis wrote:
displayResults begins on 130 and goes to 187, though several intended
features are not actually implemented yet -- I just wanted to see what
I needed to do to get it running. I was able to eliminate several
compile errors,
On Monday, Jan 6, 2003, at 18:01 US/Pacific, Ken Williams wrote:
On Monday, January 6, 2003, at 06:49 PM, Christopher D. Lewis wrote:
displayResults begins on 130 and goes to 187, though several intended
features are not actually implemented yet -- I just wanted to see
what I needed to do to
On Mon, 6 Jan 2003, Christopher D. Lewis wrote:
I was able to eliminate several compile errors, but got stuck when the
errors stopped giving me clues I knew how to follow.
Are you running with warnings strict mode?
#!/usr/bin/perl -w
use strict;
# .
That might make the
On Mon, 6 Jan 2003, Chris Devers wrote:
Are you running with warnings strict mode?
And the other thing, which I forgot to mention, is that if you can narrow
down the broken region of your script still can't figure it out, by all
means send that code the errors it produces to the list for
GViM works pretty well. Course you have to find/build rc files. There
were some tips on perlmonks for mapping syntax checks and debugging to
function keys. Not very polished, but reasonable functional. BBedit does
similar without the muss and fuss.
allan wrote:
hi
i tried the active state
rant
I've avoided the upgrade to Jaguar for a number of reasons.
- Annoyed over being charged for what still seems like a maintenance
release to me.
- Listening to all of the pain you folks and others have gone through
getting things to work.
I'd really like to get there, but I have dozens
19 matches
Mail list logo
