ActiveState Community

We use the perl interpreter in our applications, currently that is MS Visual Studio 2008 where we use it in native C++ applications. We used to do this with the perl 5.6 distribution (and thus linking the perl56.lib). This worked well but now we want "upgrade" to 5.10. I replace all header files and referred to perl510.lib. Compilation is without any problem, however, when I try to run the exact same app, any call to perl_parse (or eval_pv for that mather) crashes with an access violation.

Hi!

I'm totally new to Komodo but I'm very interested to use it for python scripting (I'm not new in Python scripting)... But before taking the time to learn it, I have some questions...

First, my configuration... I'm not using any installation of Python (directly), but I'm using an application that is using Python. The application is named Poser 8 (by Smith Micro). It has a built in python (version 2.4.2 and wxPython 2.8).

First question:
I made some little testing with Komodo Edit and am able to work with the basic python codes... The Code Intelligence seems to be working...

How do you use multiple version of Python in Komodo Edit 5.1.4 in Vista? It seems that it only recognizes version 3.1 and nothing else. I need to use both, but every time I type in 2.6, I get syntax errors. I have both 3.1 and 2.6 in my PATH, and I tell it to use the PATH, but it doesn't work.

I also tried starting a project, and I set the project preference to use the Python26 folder, and STILL it only recognizes 3.1 syntax.

I have a project with number of modules in different directories. Goto definition works within one module but does not work between modules. From pystderr.log it seems that Komodo fails to find the symbol

After I added my working directory to PYTHONPATH, I got different error

error: evaluating 'rdr.get_subscription_list' at main.py#22: hit eval sentinel: expr 'GoogleReader' eval count is 10 (abort)

I am using the Komodo 5.1 perl debugger. When I run the debugger, I set the Directory in the Debugger Options window and run the program. When I rerun the debugger, the Directory does not have the value I entered in the previous run. I created a new default cofig after entering the directory, but the new config still opens with an empty default directory.

Earlier versions of the debugger remembered it so I didn't have to enter it each time I ran.

How do I get the debugger to remember the values in the Debugger options window?

Thanks,

Barry

In Preferences / Editor / Indentation I have:

Auto-Indent Style: Use Smart Indent
"Allow file contents to override Tab settings" is unchecked.
"Prefer Tab characters over spaces" is checked.

These settings are also in Edit / Current File Settings.

In a new PHP file, I type in "if (TRUE) {" and press Enter. Komodo will auto-indent, but using spaces.

What am I missing here?

Hi,
I downloaded the add-on Klimt a couple of weeks ago. Until today, it seemed to be working, whereby it would display for me any syntax errors in my Ruby code.
But, this morning, it doesn't seem to be working. I purposely deleted the letter "F" from a FileUtils statement, and, it tells me there are no syntax errors!
Why?
Thanks,
Peter

It hang when I was trying to open a file.

version 5.2.0-beta1, build 33349, platform win32-x86

I am running Komodo IDE 5.2 beta 1 right now, and in the beginning of a session (while code intelligence isn't ready yet), I get the following message in the status bar: "This buffer is configured with 486 PHP import dirs: this may result in poor completion performance".

Where are these 486 dirs located?
Why does Komodo think it has to import all of them?
Is 486 really big enough to significantly impact performance?

Hi,
When I press F5 to run certain Ruby scripts, it sometimes stops and places me in the middle of one of the Ruby gems that I'd "required" at the top of the script. A common gem I use is FileUtils.rb. So, often, I'll run a script and all of a sudden everything stops and the screen shows me in the middle of the FileUtils.rb gem. Why is this? When I press F7 instead of F7, it seems to just go all the way through without a problem.
Thanks.