Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List in signal parameter is not handled correctly #84

Open
bohonghuang opened this issue Nov 29, 2022 · 0 comments
Open

List in signal parameter is not handled correctly #84

bohonghuang opened this issue Nov 29, 2022 · 0 comments

Comments

@bohonghuang
Copy link

Take Gio.Application for example, (gir:list-signals-desc (gir:nget-desc gio:*ns* "Application")) will produce:

(#F<activate(): (#V<RETURN-VALUE: VOID>)>
 #F<command-line(#V<command_line: INTEGER>): (#V<RETURN-VALUE: INTEGER>)>
 #F<handle-local-options(#V<options: #S<VariantDict>>): (#V<RETURN-VALUE: INTEGER>)>
 #F<name-lost(): (#V<RETURN-VALUE: BOOLEAN>)>
 #F<open(#V<files: (SEQUENCE I<File>)> #V<hint: STRING>): (#V<RETURN-VALUE: VOID>)>
 #F<shutdown(): (#V<RETURN-VALUE: VOID>)>
 #F<startup(): (#V<RETURN-VALUE: VOID>)>)

where the parameters of signal open contain a list of GFile. However, the pointer to the list and the size of the list are passed to Lisp function directly like this:

(connect app "open"
  (lambda (app files n-files hint)
    (format T "~a~%" files)))
    ;; This prints "#.(SB-SYS:INT-SAP #X56334FB51140)"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant