| Re: Help! Out of code space... [message #653] |
Fri, 29 January 1993 09:06 |
peba1231
Messages: 12
Registered: February 1992
|
Junior Member |
|
|
In IDL, you can use
.size Code_size, Data_size
to resize the respective memory areas
Peter
--
------------------------------------------------------------ ----------
Peter Bartsch | Tel. +49 (0)30 314 23093
TU Berlin, Sekr. F2 | FAX: +49 (0)30 314 22866
Marchstr. 14 |
1000 Berlin 10 | e-mail: peba1231@camillo.fb12.tu-berlin.de
------------------------------------------------------------ ----------
|
|
|
|
| Re: Help! Out of code space... [message #654 is a reply to message #653] |
Fri, 29 January 1993 04:20  |
zawodny
Messages: 121
Registered: August 1992
|
Senior Member |
|
|
In article <C1L4tq.LtM@usenet.ucs.indiana.edu> Rick McMullen writes:
> How does one increase the amount of code space to avoid this:
>
> WAVE> .run pf3dr
> % Compiled module: PLOTSET.
> % Compiled module: DEVINIT.
> % Compiled module: SHOWTITLE.
> % Compiled module: LOAD3DR.
> % Compiled module: GETCR.
> % Compiled module: GETSL.
> % Compiled module: GETCORS.
> % Compiled module: DRAWARC.
>
> contour,tt,zx,zz,xrange=[0,maxx],$
> ^
> % Program code area full.
> % 2 Compilation errors in module $MAIN$.
> WAVE>
Use the .SIZE command to increase your code and data region sizes so
that the proceedure will compile. Alternatively, Edit the offending program
(or proceedure) to split it up into smaller routines which will compile in the
default space. I understand that IDL V 3.0.0 has increased the default area
somewhat. If this happens often for you, you may want to execute a .SIZE in
your IDL_STARTUP file.
Joseph M. Zawodny (KO4LW) NASA Langley Research Center
zawodny@arbd0.larc.nasa.gov MS-475, Hampton VA, 23681
--
Joseph M. Zawodny (KO4LW) NASA Langley Research Center
zawodny@arbd0.larc.nasa.gov MS-475, Hampton VA, 23681
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
