Author Topic: Cui - LISP Load Question  (Read 711 times)

0 Members and 1 Guest are viewing this topic.

MSTG007

  • Water Moccasin
  • Posts: 2397
  • I can't remeber what I already asked! I need help!
Re: Cui - LISP Load Question
« Reply #15 on: May 21, 2019, 10:32:08 AM »
lol.... I think I need make sure you guys do not think I am crazy. I agree 85 'routines' for plotted is nuts. The ribbon I have created is not just for plotting but other tools as well. I just need those to load in. I have a lot of commands on the ribbon. lol.

But again, like you guys are suggesting, I would definitely use Lees Steal routine, it is awesome.
Autodesk Infrastructure Design Suite 2019

MP

  • Seagull
  • Posts: 17439
Re: Cui - LISP Load Question
« Reply #16 on: May 21, 2019, 10:52:47 AM »
Casual observation suggests 2 functions that take 85+ arguments between them would be more efficient.
\|// Set goal. Experiment tirelessly until
|Oo| practice has become expertise.  Loop.
|- | LinkedIn | Dropbox

dgorsman

  • Water Moccasin
  • Posts: 2394
Re: Cui - LISP Load Question
« Reply #17 on: May 21, 2019, 11:01:35 AM »
Casual observation suggests 2 functions that take 85+ arguments between them would be more efficient.

"Change the data, not the code."
If you are going to fly by the seat of your pants, expect friction burns.

try {GreatPower;}
   catch (notResponsible)
      {NextTime(PlanAhead);}
   finally
      {MasterBasics;}

MSTG007

  • Water Moccasin
  • Posts: 2397
  • I can't remeber what I already asked! I need help!
Re: Cui - LISP Load Question
« Reply #18 on: May 21, 2019, 11:03:43 AM »
Just curious. Is it bad practice to combined multiple routines into one file, rather than a file for each routine?
Autodesk Infrastructure Design Suite 2019

MP

  • Seagull
  • Posts: 17439
Re: Cui - LISP Load Question
« Reply #19 on: May 21, 2019, 11:25:48 AM »
IME what's "bad practice" is duplicated / copied logic -- it's unnecessarily maintenance and trouble shooting heavy. Regarding one file or multiple files -- per my previous post -- it would appear 2 functions taking multiple arguments would suffice. If said functions are ambitious (doesn't appear so) or significantly different (i.e. prone to independent update / maintenance) 2 files might be the better option.
\|// Set goal. Experiment tirelessly until
|Oo| practice has become expertise.  Loop.
|- | LinkedIn | Dropbox

MP

  • Seagull
  • Posts: 17439
Re: Cui - LISP Load Question
« Reply #20 on: May 21, 2019, 11:49:01 AM »
"Change the data, not the code."

this
\|// Set goal. Experiment tirelessly until
|Oo| practice has become expertise.  Loop.
|- | LinkedIn | Dropbox