ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> komodo-beta
komodo-beta
Re: [Komodo-3-beta] Various findings
by Trent Mick other posts by this author
Jul 5 2004 10:28AM messages near this date
view in the new Beta List Site
[Komodo-3-beta] Various findings | [Komodo-3-beta] I just signed up and ...
[Jouke Visser wrote]
>  I've been using Komodo 3.0 beta in the past week on WinXP SP 1 
>  (developing Perl only) and these are the things that I ran into:
>  
>  1. It crashed 3 times at unpredictable moments. I wasn't able to 
>  reproduce this. My Komodo 2.5 has maybe crashed once in the past year.

We have noticed that some WinXP-specific crash situations are fixed by
fully updating the OS with critical and recommended patches from Windows
Update.

>  2. The debugger yesterday refused to give me the values of any variable. 
>  It just said 'bizarre copy of array blablabla' in the debugger DLL.

If you could log a bug with specifics (OS details, version of Perl,
example scripts, steps to repro, attaching Komodo's log files
"stdout.tmp" and "stderr.tmp", quoting error messages exactly -- did it
really say "bizarre"?) that would be helpful:

    http://bugs.activestate.com/Komodo

>  3. I wasn't able to find out how in the code-pane on the left I could 
>  make the 'No documentation available' show the documentation on a 
>  function I selected. The POD documentation at the bottom of the file 
>  should have appeared there I presume?

Unfortunately POD is not currently picked up for "Code Intelligence
scanning" of Perl so that information isn't available to the pane you
are referring to (the "description area" of the Code Browser).

>  4. Komodo thought that a file with mixed DOS and Unix line endings 
>  should be reported as syntax errors (a file with those was all green 
>  underlined). I had to use UltraEdit to convert the file to all Unix line 
>  endings to make this annoying thing disappear.

Yes, they are reported as syntax warnings (as they usually should be).
Granted there are some cases in Komodo where the wrong EOLs will get
inserted into you document. Note that you could have used Komodo's
    "Code | Clean Line Endings"
menu option or unchecked the "Preserve existing line endings" in that
file's "Properties and Settings" dialog to fix the line endings. 


Trent

-- 
Trent Mick
TrentM@ActiveState.com
Thread:
Jouke Visser
Trent Mick

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved