| IDLdoc 3.3 released [message #72989] |
Wed, 20 October 2010 10:30  |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
IDLdoc 3.3 was released today. For downloads and release notes, see
idldoc.idldev.com/wiki/Downloads
I think the biggest feature in this release are tutorial and reference
manuals detailing how to use IDLdoc. Read the tutorial for the
recommended method for documenting new code, while checking the
reference manual gives details on all the supported features (like
legacy format styles).
Mike
--
www.michaelgalloy.com
Research Mathematician
Tech-X Corporation
|
|
|
|
| Re: IDLdoc 3.3 released [message #73035 is a reply to message #72989] |
Mon, 25 October 2010 02:03  |
sh
Messages: 26
Registered: April 2010
|
Junior Member |
|
|
On Oct 24, 7:38 pm, Michael Galloy <mgal...@gmail.com> wrote:
> On 10/24/10 11:43 am, sh wrote:
>
>> I tried the new version and also an older one, but they didn't work!
>> Everytime IDL shuts down without any comment, it just closes itself.
>
>> Well, we have really a lot of code and after some time I realized that
>> the memory grow up to 1.2GB and after that (maybe) Windows forces IDL
>> to stop and close. Is there a work around for a lot of code? e.g. call
>> it several times?
>
> How many lines of code is this? Setting the NOSOURCE keyword to the
> IDLDOC call might help save some memory, if you are close to having
> enough memory. If your code is organized into multiple directories you
> could also make multiple runs, but the index and listings will be
> partial then.
>
> Mike
> --www.michaelgalloy.com
> Research Mathematician
> Tech-X Corporation
>
This doesn't work either, memory grew also up to 1.2GB and IDL died.
All together we have approx. 2500 files of code. What is the limit for
idldoc?
Is there any other solution? e.g. force windows to give
idl_opserver.exe more memory?
Sebastian
|
|
|
|
| Re: IDLdoc 3.3 released [message #73041 is a reply to message #72989] |
Sun, 24 October 2010 16:38 |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
On 10/24/10 11:43 am, sh wrote:
> I tried the new version and also an older one, but they didn't work!
> Everytime IDL shuts down without any comment, it just closes itself.
>
> Well, we have really a lot of code and after some time I realized that
> the memory grow up to 1.2GB and after that (maybe) Windows forces IDL
> to stop and close. Is there a work around for a lot of code? e.g. call
> it several times?
How many lines of code is this? Setting the NOSOURCE keyword to the
IDLDOC call might help save some memory, if you are close to having
enough memory. If your code is organized into multiple directories you
could also make multiple runs, but the index and listings will be
partial then.
Mike
--
www.michaelgalloy.com
Research Mathematician
Tech-X Corporation
--
www.michaelgalloy.com
Research Mathematician
Tech-X Corporation
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
