Re: load recursively

Hi Jon, > Thanks for the extensive explanation! I'll work a bit on this later to > make sure I understand every part of it. ;-) OK, perhaps I should also elaborate a little on the background: As you know, if you start picoLisp with ./p or ./dbg, it 'load's all arguments in sequence, then display

Re: load recursively

Hi Alex, Thanks for the extensive explanation! I'll work a bit on this later to make sure I understand every part of it. ;-) /Jon > Hi Jon, > >> I still don't get the difference this T makes. If I want to load two >> files >> with one 'load' call, when should I include the T? > > To load two fil

Re: load recursively

Hi Jon, > I still don't get the difference this T makes. If I want to load two files > with one 'load' call, when should I include the T? To load two files, you can simply write (load "file1" "file2"). The T is there to get access to the remaining command line arguments. This is typically needed

Re: load recursively

Hi Alex, > Hi Jon, > >> In the docs on the 'load' function I read that, "When any is T, all >> remaining command line arguments are loaded recursively." Can somebody >> explain what this recursive loading is? > > There is nothing special about the word "recursive" here. It could as > well say "Whe

Re: load recursively

Hi Jon, > In the docs on the 'load' function I read that, "When any is T, all > remaining command line arguments are loaded recursively." Can somebody > explain what this recursive loading is? There is nothing special about the word "recursive" here. It could as well say "When any is T, all remai

load recursively

Hi, In the docs on the 'load' function I read that, "When any is T, all remaining command line arguments are loaded recursively." Can somebody explain what this recursive loading is? /Jon -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe