Stepping through code in Komodo seems to work in perl pretty well. The
below excerpt is from Komodo help:
#---------------------------------
Instead of running to the end of a program or to the next breakpoint,
the debugger can also step through code one statement at a time. The
following Debug menu items and toolbar buttons control stepping behavior:
* *Step In*: Executes the current statement and pauses at the
following statement.
* *Step Over*: Executes the current statement. If the line of code
calls a function or method, the function or method is executed in
the background and the debugger pauses at the statement that
follows the original one.
* *Step Out*: When the debugger is within a function or method,
*Step Out* will execute the code without stepping through the code
line by line. The debugger will stop on the line of code following
the function or method call in the calling program.
When stepping through a program which calls a function or method from an
external program (e.g. a module or package) the debugger steps into the
external program at the point where the function or method is called,
opening it in a new tab. Stepping continues in the external program
until the function call is completed.
*Note*: Perl operators |sort|, |map|, and |grep| behave like other
looping constructs with respect to stepping behavior in the debugger.
When Komodo has stopped at one of these operators, *Step Over* stops at
the first statement or expression used within the first argument of
these operators.
For example, if the debugger steps over a statement containing a
|foreach|, |while|, |map|, |grep|, or |sort| looping construct that
evaluates its body five times, the debugger remains inside that loop for
five iterations. When it steps over on the sixth iteration, the debugger
exits the loop and stops at the next statement.
To skip execution of such looping constructs, set a breakpoint on the
statement following the construct, and continue until Komodo reaches
that breakpoint.
#----------------------------------------------
Active State has also developed a way to easily distribute applications
(eg The Perl Development Kit or PDK for short). Here is more on the PDK:
http://www.activestate.com/products/perl_dev_kit/feature_list.plex
I haven't tried the PDK yet, because it may require that I switch my
development for regular perl to Active State's release of perl, which
isn't too bad, since Active State's release of perl is free and runs on
all the different platforms.
Anyway, the PDK look interesting to me as It would appear to allow me
to distribute my apps, including aLL necessary modules, in one bundle
that would run on the clients computer whether they had perl installed
or not.
Regards,
LelandJ
Kenneth Kixmoeller/fh wrote:
> Hey - - - ---- - -
>
> I know, why ask a PHP question in here?
>
> 1. You know the context of what I am talking about.
> 2. PHP forums main answer: "RTFM"
> -- not relevant for this question
> 3. Secondary PGP forum answer: "Search the archives"
> -- the archives, um, "inhale vigorously" (at least compared to
> what we are used to)
> 4. I know some of you are working in PHP
>
> So here goes:
>
> Is there any product out there that debugs PHP code reasonably
> similarly to the way that VFP's debugger works? By which I mean:
> - Set a breakpoint
> - Step through code line-by-line
> - See results (variable values, etc.)
>
> <Insert Deity>! I miss having the debug tool integrated into the
> product!!
>
> I have tried Komodo, which uses the DBG engine, I think. It *looks*
> like it is going to be similar, but breakpoints are unreliable, and a
> single "step" takes you off through a black hole, ending up in random
> spots 3 processes later. I have tried to set up XDebug, but didn't
> succeed. If I am going to work through the labyrinthine installation
> process, I would like to have some idea that is is going to work.
>
> For the moment, I am doing it in W2K, but would happily do it on my
> Mac or Linux machine if that would be easier.
>
> Now pardon me a while so I can go bang my head on my concrete wall.
> That is far less painful.
>
> Ken
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
