Topic: Issues compiling to VLX

[squirreldip]

I have a .cmd script which creates a .lsp file to write .dcl files by reading a folder containing source .dcl files.  I'm getting an error when using VLIDE to create a vlx from the .lsp :

Code: [Select]

; error: too many arguments: (PROGN (SETQ OUTFILE ( ... )) (PRINC "DUALCAR : dialog {\n" OUTFILE) (PRINC "                   label = \"RFL Dual Carriageway 3DPoly Creator\";\n" OUTFILE) ... )
The .lsp loads fine and executes correctly.

If anyone has any ideas it would be greatly appreciated.

[squirreldip]

Is there a limit to how many lines can be contained within a (progn) block?

Edit:

Answer is yes (here)

[MeasureUp]

I have a .cmd script which creates a .lsp file to write .dcl files by reading a folder containing source .dcl files.  I'm getting an error when using VLIDE to create a vlx from the .lsp :

Code: [Select]

; error: too many arguments: (PROGN (SETQ OUTFILE ( ... )) (PRINC "DUALCAR : dialog {\n" OUTFILE) (PRINC "                   label = \"RFL Dual Carriageway 3DPoly Creator\";\n" OUTFILE) ... )
The .lsp loads fine and executes correctly.

If anyone has any ideas it would be greatly appreciated.

I did not look your attached code. But can you replace the portion (princ "label = \"RFL…) with this:

Code: [Select]

(princ (strcat "label = \"RFL Dual Carriageway 3DPoly Creator\""
       "\n"
       OUTFILE
       ); end of strcat
)
(princ)

Note: take care of using ";" in a single line because ";" breaks the rest in the line.
Then you may be able to fix (princ "DUALCAR : dialog {\n" OUTFILE).

Please also have a look "strcat" function in help.

HTH

[squirreldip]

Thanks MeasureUp - the suggestion should work.

I think the big issue for me was just not realizing that there is a limit.  I solved my problem by temporarily storing a list then iterating through that list.  Yours is probably better as no variable needs to be stored.

[roy_043]

See: https://www.theswamp.org/index.php?topic=48883.0

[Grrr1337]

See: https://www.theswamp.org/index.php?topic=48883.0

I've never attempted to compile to VLX, but after reading this I thought would (repeat 1) can be an alternative of a loooong (progn).

[ribarm]

I was about to ask does anyone know limit of (setq var1 value1 var2 value2 ... )? I know this can be simplified by separating setq-es, but just for an info...

[ChrisCarlson]

Could the length of a progn issue be eliminated by creating a sub-function and simply calling it?

[Lee Mac]

IMO, if you start to run up against the argument limits inherent in AutoLISP, you really need to take a step back and restructure your program; in the hundreds of thousands of lines of code I've written, I've never been troubled by the maximum number of arguments afforded by functions such as progn, cond etc.

[Grrr1337]

IMO, if you start to run up against the argument limits inherent in AutoLISP, you really need to take a step back and restructure your program; in the hundreds of thousands of lines of code I've written, I've never been troubled by the maximum number of arguments afforded by functions such as progn, cond etc.

Thats what"the List Manipulator" said. 

[ur_naz]

You can add DCL to your VLX app. Making DCL on the fly is very bad idea. 

[Lee Mac]

You can add DCL to your VLX app. Making DCL on the fly is very bad idea. 

DCL as part of a VLX application is still unencrypted and merely appended as plain text to the VLX file.

[MP]

Making DCL on the fly is very bad idea. 

Support this assertion please.

[ribarm]

I was about to ask does anyone know limit of (setq var1 value1 var2 value2 ... )? I know this can be simplified by separating setq-es, but just for an info...

I've successfully loaded lisp with 10MB size, containing 1000000 variables setq-ed in one line... So if I may conclude (setq) has no such issues with limitations... Note that in lisp that I used to create lisp (10MB) (load) function isn't quite thankful for checking... So as soon as first loop was over I terminated CAD and started it again when I used copy+paste method with lisp (10MB) into CAD interface for loading that setq... It was success and I still had to wait for loading 10MB lisp for a while... Here is my (c:testsetq) for creation of ttt.lsp (10MB), so that you can experiment on your own if you want, but I warn you if you have more important thing to do, please ignore this test...

Code: [Select]

(defun c:testsetq ( / f )
  (setq k 1000000)
  (while t
    (setq f (open "c:/SHARED FOLDER/ttt.lsp" "w"))
    (write-line "(eval (setq" f)
    (repeat (setq k (+ k 1000000))
      (write-line "a 1" f)
    )
    (write-line "))" f)
    (close f)
    (load "c:/SHARED FOLDER/ttt.lsp")
  )
)

P.S. "k" variable is global in order to be checked upon load failure (but this won't happen at least according to my testings)...

[ur_naz]

Making DCL on the fly is very bad idea. 

Support this assertion please.

Ok, if you write dynamic DCL you have to
1) Write more code and read much longer bumf;
2) Check  more errors and every slash around strings;
3) Check if DCL is created/exist/loaded. Some paranoiac antivirus software and latest versions of windows can prevent file I/O operations.
4) Rewrite your code every time then Autodesk fails with codepages...