Stats

  • Locked Locked
  • Replies 18
  • Subscribers 144
  • Views 22620
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Scheme vs Common Lisp style in SKILL++

tweeks

 While you can write your SKILL++ code like it is C, Maclisp, Scheme, or Common Lisp (or none of the above...), I've been experimenting with Common Lisp style lately.

Trying to write Common Lisp style code in SKILL++ can lead to curious situations like this:

(defvar first car)

The intention is to define FIRST as another name for CAR, as in Common Lisp.  In Scheme, we would write

(define first car)

which seems pretty natural, but using DEFVAR to define a function just feels.... wrong... somehow... :)

I guess I should use ALIAS:

 (alias second cadr)

 except ALIAS has weird limitations:

ILS-> (foo = first)
primop:car
ILS-> (foo '(1 2 3))
1
ILS-> (foo = second)
macro:evalalias
ILS-> (foo '(1 2 3))
*Error* evalalias: unknown alias - foo

Parents

  •  You dangle a bone over the fence and when we go to the docs, the cupboard is bare.

    Can you supply us with an example of unwindProtect? Can you show the forms as blocks of code?

    Does the cleanup code get evaluated regardless of the error status of the protected form?

    What is the return value of the unwindProtect function if:
    A: If the protected form runs without error
    B: If the protected form has an error

    Sorry to ask but I'm not at a client with Virtuoso access.

    Ted

Reply

  •  You dangle a bone over the fence and when we go to the docs, the cupboard is bare.

    Can you supply us with an example of unwindProtect? Can you show the forms as blocks of code?

    Does the cleanup code get evaluated regardless of the error status of the protected form?

    What is the return value of the unwindProtect function if:
    A: If the protected form runs without error
    B: If the protected form has an error

    Sorry to ask but I'm not at a client with Virtuoso access.

    Ted

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.