| Compiling errors [message #64287] |
Wed, 17 December 2008 02:11  |
loebasboy
Messages: 26
Registered: August 2008
|
Junior Member |
|
|
I have a procedure where i use a self written function in. If I
compile the procedure and then type in the command line the following:
.reset_session
resolve_all
all dependent functions are compiled. Then if i try to run the
procedure I get an error on the line where i use the self written
function:
% Keyword parameters not allowed in call.
I've rewritten the function some time ago with different input
parameters as a result. If I then compile the self written function
manually, everything works.
What seems to be the problem here? Am I doing something wrong here,
apart for rewriting the function.
Also, if I use 'resolve_all' with IDL + ENVI on, i get alot of errors,
with being the first:
% Attempt to call undefined procedure/function: 'ADAPT_FILT_EVENT'.
What am I doing wrong?
|
|
|
|
| Re: Compiling errors [message #64366 is a reply to message #64287] |
Thu, 18 December 2008 01:39  |
loebasboy
Messages: 26
Registered: August 2008
|
Junior Member |
|
|
On 18 dec, 10:37, loebasboy <stijn....@gmail.com> wrote:
> On 17 dec, 13:37, "Jean H." <jghas...@DELTHIS.ucalgary.ANDTHIS.ca>
> wrote:
>
>
>
>
>
>> loebasboy wrote:
>>> I have a procedure where i use a self written function in. If I
>>> compile the procedure and then type in the command line the following:
>
>>> .reset_session
>>> resolve_all
>
>>> all dependent functions are compiled. Then if i try to run the
>>> procedure I get an error on the line where i use the self written
>>> function:
>
>>> % Keyword parameters not allowed in call.
>
>>> I've rewritten the function some time ago with different input
>>> parameters as a result. If I then compile the self written function
>>> manually, everything works.
>
>> is it a system function?
>> Do you still have the old one in your path? ... I have found IDL7 to use
>> the dumbest file it could (like function_backup.pro will be used before
>> function.pro)
>
>>> What seems to be the problem here? Am I doing something wrong here,
>>> apart for rewriting the function.
>
>>> Also, if I use 'resolve_all' with IDL + ENVI on, i get alot of errors,
>>> with being the first:
>
>>> % Attempt to call undefined procedure/function: 'ADAPT_FILT_EVENT'.
>
>>> What am I doing wrong?
>
>> Nothing, resolve_all calls all (really all of them?) Envi functions when
>> Envi is open... nothing to worry about!
>
>> Jean- Tekst uit oorspronkelijk bericht niet weergeven -
>
>> - Tekst uit oorspronkelijk bericht weergeven -
>
> Thanks for the answer, the self written function is called
> 'read_hdf5'. A function that is not a system function by my knowing.
> The only thing resembling is the example program 'ex_read_hdf5'.- Tekst uit oorspronkelijk bericht niet weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -
Also, I forgot to say, the old function still exists, I think, but in
a completely different path (as a backup of some sort).
|
|
|
|
| Re: Compiling errors [message #64403 is a reply to message #64366] |
Mon, 22 December 2008 01:26 |
loebasboy
Messages: 26
Registered: August 2008
|
Junior Member |
|
|
On 18 dec, 10:39, loebasboy <stijn....@gmail.com> wrote:
> On 18 dec, 10:37, loebasboy <stijn....@gmail.com> wrote:
>
>
>
>
>
>> On 17 dec, 13:37, "Jean H." <jghas...@DELTHIS.ucalgary.ANDTHIS.ca>
>> wrote:
>
>>> loebasboy wrote:
>>>> I have a procedure where i use a self written function in. If I
>>>> compile the procedure and then type in the command line the following:
>
>>>> .reset_session
>>>> resolve_all
>
>>>> all dependent functions are compiled. Then if i try to run the
>>>> procedure I get an error on the line where i use the self written
>>>> function:
>
>>>> % Keyword parameters not allowed in call.
>
>>>> I've rewritten the function some time ago with different input
>>>> parameters as a result. If I then compile the self written function
>>>> manually, everything works.
>
>>> is it a system function?
>>> Do you still have the old one in your path? ... I have found IDL7 to use
>>> the dumbest file it could (like function_backup.pro will be used before
>>> function.pro)
>
>>>> What seems to be the problem here? Am I doing something wrong here,
>>>> apart for rewriting the function.
>
>>>> Also, if I use 'resolve_all' with IDL + ENVI on, i get alot of errors,
>>>> with being the first:
>
>>>> % Attempt to call undefined procedure/function: 'ADAPT_FILT_EVENT'.
>
>>>> What am I doing wrong?
>
>>> Nothing, resolve_all calls all (really all of them?) Envi functions when
>>> Envi is open... nothing to worry about!
>
>>> Jean- Tekst uit oorspronkelijk bericht niet weergeven -
>
>>> - Tekst uit oorspronkelijk bericht weergeven -
>
>> Thanks for the answer, the self written function is called
>> 'read_hdf5'. A function that is not a system function by my knowing.
>> The only thing resembling is the example program 'ex_read_hdf5'.- Tekst uit oorspronkelijk bericht niet weergeven -
>
>> - Tekst uit oorspronkelijk bericht weergeven -
>
> Also, I forgot to say, the old function still exists, I think, but in
> a completely different path (as a backup of some sort).- Tekst uit oorspronkelijk bericht niet weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -
I think Jean has a lead here asking about the old function existing
somewhere. Can You force IDL to look for functions in a certain path.
I made it easy for IDL though putting all needed functions in the
project map.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
