Topic: Store Lots of Data in Text File

[roy_043]

hardcoding variable name into lsp data file is not a good idea
as soon as load returns the last expression evaluated, one can do it this way

what is the difference to say that it is not a good idea? The example I posted is what I use to update a global variable whose value, if it changes, is written to a file lsp and reloaded into new file dwg if opened.

I agree Vovka here. Keeping the variable outside the data file is better for two reasons:
1. It is more flexible: You can attach the same data to multiple variables.
2. You are less likely to end up with unlocalized variables.

[Marc'Antonio Alessi]

...
I agree Vovka here. Keeping the variable outside the data file is better for two reasons:
1. It is more flexible: You can attach the same data to multiple variables.
2. You are less likely to end up with unlocalized variables.

I agree with you... but before you say it's a bad idea...

Code: [Select]

(defun c:test ( / alist)
  (setq alist '((45 63 23)(74 2 52)(45 34 64)))
  (ALE_Utl_WriteData 'alist "z:\\temp\\Ale.lsp")
  (ALE_Utl_LoadData "z:\\temp\\Ale.lsp")
  (princ)
)
Comando: TEST

Comando: !alist
nil
> You can localize the variable alist.

[Kerry]

...
I agree Vovka here. Keeping the variable outside the data file is better for two reasons:
1. It is more flexible: You can attach the same data to multiple variables.
2. You are less likely to end up with unlocalized variables.

I agree with you... but before you say it's a bad idea...

Code: [Select]

(defun c:test ( / alist)
  (setq alist '((45 63 23)(74 2 52)(45 34 64)))
  (ALE_Utl_WriteData 'alist "z:\\temp\\Ale.lsp")
  (ALE_Utl_LoadData "z:\\temp\\Ale.lsp")
  (princ)
)
Comando: TEST

Comando: !alist
nil
> You can localize the variable alist.

I'd do it thusly :

In the function that reads the data make the last statement return the list you've read

and assign the returned value to a variable you have control over ...

<...>
(setq myData (readTheDataFile fileName) )
<... >

[Marc'Antonio Alessi]

...
I'd do it thusly :
In the function that reads the data make the last statement return the list you've read
and assign the returned value to a variable you have control over ...
<...>
(setq myData (readTheDataFile fileName) )
<... >

Okay I agree, but I think it's more important to discuss whether it is best to read the data file or load it as lisp file, also because this suggestion seems to have been ignored...