Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 13097
  • 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

How to create #N Field is OK by skill ?

Charley Chen

Dear All,

I want to create a #11    hiCreateStringField(...) , as below :

   MyField1 = hiCreateStringField(?name   concat("strfield" 1)

                                                           ?value  sprintf(nil "%d" i)

                                                            ?prompt sprintf(nil "Field %d" i)

                      )

   MyField2 = hiCreateStringField(?name   concat("strfield" 2)

                                                           ?value  sprintf(nil "%d" 2)

                                                            ?prompt sprintf(nil "Field %d" 2)

                      )

.

.

   MyField10= hiCreateStringField(?name   concat("strfield" 10)

                                                           ?value  sprintf(nil "%d" 10)

                                                            ?prompt sprintf(nil "Field %d" 10)

                      )

But the #  field is dynamic , and it's hard to write . So i change the code ,

It has error  if the code is below

  => Error  MyField%d ^ = hiCreateStringField(?name   concat("strfield" i)

SYNTAX ERROR found at ...

for(i  0   10

   MyField%d = hiCreateStringField(?name   concat("strfield" i)

                                                           ?value  sprintf(nil "%d" i)

                                                            ?prompt sprintf(nil "Field %d" i)

                      )

 );for

Thank you ,

Charley

Parents

  • That's hardly surprising - don't know why you thought you could use %d in a variable name? It's a string formatting code in the various printf functions - you can't just use it arbitrarily elsewhere.

    You could do this (although I doubt it's the right way to do it in practice):

    set(concat('MyField i) hiCreateStringField(...))

    However, then presumably you're going to have to access this variable with a created name - which you could do with symeval(concat('MyField i)) but all you're doing here is effectively creating a poor implementation of an array. So why not either put all these fields in a list:

    for(i 0 10
      newField=hiCreateStringField(...)
      listOfFields=cons(newFields listOfFields)
    )

    If the order matters, you could reverse the list at the end, or use tconc to construct it in the right order in the first place.

    Or you could use an array:

    declare(MyFields[11])
    for(i 0 10
      MyFields[i]=hiCreateStringField(...)
    )

    Regards,

    Andrew.

Reply

  • That's hardly surprising - don't know why you thought you could use %d in a variable name? It's a string formatting code in the various printf functions - you can't just use it arbitrarily elsewhere.

    You could do this (although I doubt it's the right way to do it in practice):

    set(concat('MyField i) hiCreateStringField(...))

    However, then presumably you're going to have to access this variable with a created name - which you could do with symeval(concat('MyField i)) but all you're doing here is effectively creating a poor implementation of an array. So why not either put all these fields in a list:

    for(i 0 10
      newField=hiCreateStringField(...)
      listOfFields=cons(newFields listOfFields)
    )

    If the order matters, you could reverse the list at the end, or use tconc to construct it in the right order in the first place.

    Or you could use an array:

    declare(MyFields[11])
    for(i 0 10
      MyFields[i]=hiCreateStringField(...)
    )

    Regards,

    Andrew.

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.