About loop constructs

Seems a slightly odd requirement, but you could do it with this:

defmacro(LP (Total Cycle @rest code)
  if(cdr(Cycle) then
    `for(,car(Cycle) 1 ,car(Total) LP(,cdr(Total) ,cdr(Cycle) ,@code))
  else
    `for(,car(Cycle) 1 ,(car Total) ,@code)
  )
)

; example:
procedure(foobar()
  LP((3 2 1) (A B C)
    println(list(A B C))
  )
)

Run foobar() once, and then you can do pp(foobar) to see the function - it will have then had the macro expanded. If you do the pp before running it, you'll see just the macro calls.

Note the functions should really have sensible prefixes; calling them LP and foobar in the example above is not a good idea as they could clash with other poorly named functions. Also, if the requirement is that the arguments to LP are dynamic - i.e. they are variables which could change throughout the program, the above approach won't work because macros are done at compile time. If they're dynamic though, you might want to explain precisely what it is you're trying to do?

Regards,

Andrew.

Thank you! I will try this later. 

Regards,

Bobby

... I had found that before you answered me.  So I deleted it.
Now I want to know outside defmacro is there anyway to use its local variable.
For example, after input
LP((3 2 ) (Process Bat) println(list(Process Bat) ) )
I also want to variable Process for other use.

Regards,

Bobby.

Bobby,

Well, there's no reason why you can't use the variable Process outside the LP() function. The Process is local to the for() loop. If you're asking to access the for() loop's local variable outside the loop, then you can't (it wouldn't be local then, would it?), and even if you could, what would you expect it to contain?

The main issue is that I don't understand what you're trying to achieve - so your question doesn't make sense to me.

Regards,

Andrew.

Andrew,

I'm sorry, in fact I want to design some basis ocean for circuit design. So I want to achieve some function which makes other fresh man easier to understand and can be reused.But now I have never fully thought how to do it.
The function discussed above is just one of them. It contains uncertain loops, each cycle corresponding to the different variables
For example, there are variables A B C D E ... Every time I combine some of them  and see their impact on the circuit, the other variables remain typical value.
Perhaps I may write analysis() in @rest code. But when analysis finishes I get some circuit result such as Id and I want to know its worst condition. Then combine these worst-case conditions to get the top worst condition.
For example I want to get max value of Id.
Loop is like this:
A   B   Id       
1   1   1u
      2   3u
2   1    5u
      2   6u
3   1    4u
      2   2u

C   D  E   Id       
1   1  1    1u
          2   1.5u
     2  1    3u
          2   3.5u
     3  1    5u
          2   4u
2   1  1    2u
          2   6u
     2  1    2.5u
          2   3.5u
    3   1   1u
          2   0.5u

To achieve above I may write
LP((3 2) (A B) analysis()....) 
LP((2 3 2) (C D E) analysis()....)    
and get  worst condition from it:A=2 B=2 C=2 D=1 E=2
And I will do simulation in this case.

I know its easier if I use for(for (for .....))) to construct the ocean. But when combination need to change the code may be rewritten.
May be my idea is too complicated. I hope you can help me.

Regards,

Bobby.

You could do:

resultTab=makeTable('results nil)
LP((2 3 2) (C D E)
  analysis(...)
  resultTab[list(C D E)]=someCalculation
)

Then you have an association table with all the results in. You could then process this outside the loop once things have finished?

In general, I would have expected foreach() to be more useful than for loops - because usually you will have a set of values or a set of corners, etc that need to be iterated over, rather than a for loop (which usually means you are using the wrong data structure in SKILL).

I still don't quite get your overall aim - I'm not sure this disguising of the loops is really making life easier for the user.

Regards,

Andrew.

Hello Andrew,

    Wow, "makeTable" is something new to me. I think I need some time to learn it.

    Moreover, I will accept your advice that use "foreach" instead of "for"

Regards,

Bobby.