issue-#123 *Hook proc. not seen in extension interface

User avatar
DGDanforth
Posts: 1061
Joined: Tue Sep 17, 2013 1:16 am
Location: Palo Alto, California, USA
Contact:

issue-#123 *Hook proc. not seen in extension interface

Post by DGDanforth »

Folks,

Kernel has a procedure SetLoaderHook that is marked for export "*" and yet when one
does Ctrl-D on Kernel one does not see that procedure.

That procedure is known to StdLoader which calls Kernel.SetLoaderHook so the procedure is there but it is invisible. Why?

I don't understand that behavior.

-Doug
cfbsoftware
Posts: 204
Joined: Wed Sep 18, 2013 10:06 pm
Contact:

Re: Exported but not seen procedures

Post by cfbsoftware »

Run the DevBrowser.ShowInterface command with the "&" option included.

In the DevBrowser Docu this is described as:
PROCEDURE ShowInterface (opts: ARRAY OF CHAR)
...
...
opts = "&" creates an output which also shows hooks in the interface.
User avatar
DGDanforth
Posts: 1061
Joined: Tue Sep 17, 2013 1:16 am
Location: Palo Alto, California, USA
Contact:

Re: Exported but not seen procedures

Post by DGDanforth »

cfbsoftware wrote:Run the DevBrowser.ShowInterface command with the "&" option included.

In the DevBrowser Docu this is described as:
PROCEDURE ShowInterface (opts: ARRAY OF CHAR)
...
...
opts = "&" creates an output which also shows hooks in the interface.
Thank you Chris.
I was unaware of those browser options.
Its somewhat awkward to actually do that since it entails creating a menu

Code: Select all

MENU "Browser"
	"Show hooks"	""	"DevBrowser.ShowInterface('&')"	""
END
and putting that some where, but it works.
Thanks again.
-Doug
User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

Re: Exported but not seen procedures

Post by Josef Templ »

Doug, you can use the dialog Info->Interface...
and execute "Show Extension Interface".
This gives you information about the hooks as well.
Unfortunately, this does not show the procedure Kernel.SetLoaderHook
but only the related hook types and variables.
This seems to be a bug indeed.

The fix would be simple. In DevBrowser.Proc replace the second line by

Code: Select all

IF global.extensioninterface & ~((obj.link # NIL) & (obj.link.link = NIL) & IsHook(obj.link.typ)) THEN RETURN END;
- Josef
Zinn
Posts: 476
Joined: Tue Mar 25, 2014 5:56 pm
Location: Frankfurt am Main
Contact:

Re: Exported but not seen procedures

Post by Zinn »

I miss this change in the last link of the Center Edition (506).
Do we add this change to the Center Edition or not ???
- Helmut
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: Exported but not seen procedures

Post by Ivan Denisov »

Zinn wrote:I miss this change in the last link of the Center Edition (506).
Do we add this change to the Center Edition or not ???
I think, not. There should be issue and voting for this fix.
User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

Re: Exported but not seen procedures

Post by Josef Templ »

I think it is a bug indeed and a separate issue should be created for that.
It is simple to fix as I have already pointed out.

- Josef
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: Exported but not seen procedures

Post by Ivan Denisov »

Josef Templ wrote: The fix would be simple. In DevBrowser.Proc replace the second line by

Code: Select all

IF global.extensioninterface & ~((obj.link # NIL) & (obj.link.link = NIL) & IsHook(obj.link.typ)) THEN RETURN END;[/quote]

We are still not include this fix. Can it be classified as a bug?
User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

Re: Exported but not seen procedures

Post by Josef Templ »

To me it is a bug and it should be fixed.
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: Exported but not seen procedures

Post by Ivan Denisov »

Post Reply