Warning when calling dbLayerEnclose in SKILL++.

This is a bit of an oddity - I can't see why dbLayerEnclose is an nlambda - none of the other layer functions are. So I filed CCR 891034 to get this changed (if possible).

You can workaround it by doing this:

(defmacro MYdbLayerEnclose (cv layer dbList1 dbList2)
  `(inSkill
     (let ((nullPort (outfile "/dev/null")))
       (prog1
         (let ((woport nullPort))
           (dbLayerEnclose (inScheme ,cv) (inScheme ,layer)
                           (inScheme ,dbList1) (inScheme ,dbList2))
           )
         (close nullPort)
         )
       )
     )
  )

It's a bit convoluted, in order to swallow the warning in all releases, but you should then be able to use MYdbLayerEnclose() instead of dbLayerEnclose in SKILL++ code.

Regards,

Andrew.

A rather belated append - but it came up today in a discussion with a customer. My suggested workaround above doesn't work very well:

1. There's no real need to swallow the warnings, because the warnings wouldn't appear because it's evaluated in SKILL mode because of the inSkill.
2. It doesn't properly handle arguments being passed which are lexically scoped rather than global

Instead, this can be simply worked around by creating:

(inSkill
  (defun MYdbLayerEnclose (cv layer dbList1 dbList2)
    (dbLayerEnclose cv layer dbList1 dbList2)
  )
)

not sure why I didn't do it that way in the first place! A macro is completely unnecessary in this case. Of course, it's a shame that we haven't fixed this after 11 years, so I chased that too.

Andrew

A rather belated append - but it came up today in a discussion with a customer. My suggested workaround above doesn't work very well:

1. There's no real need to swallow the warnings, because the warnings wouldn't appear because it's evaluated in SKILL mode because of the inSkill.
2. It doesn't properly handle arguments being passed which are lexically scoped rather than global

Instead, this can be simply worked around by creating:

(inSkill
  (defun MYdbLayerEnclose (cv layer dbList1 dbList2)
    (dbLayerEnclose cv layer dbList1 dbList2)
  )
)

not sure why I didn't do it that way in the first place! A macro is completely unnecessary in this case. Of course, it's a shame that we haven't fixed this after 11 years, so I chased that too.

Andrew