Thanks, I understand the benefit. And already add this explanation to my notes.
https://github.com/HaveF/ASFL/blob/master/README.md#export-to-external-files On Sat, Oct 20, 2012 at 7:19 PM, Edward K. Ream <[email protected]> wrote: > On Fri, Oct 19, 2012 at 11:18 AM, HaveF <[email protected]> wrote: > > >> Leo handles scripts differently. It is valid for a script not to > include descendant nodes. That is, you won't get an error if a script > has descendants but does not include them with @others. This is so > descendant nodes can contain data. > > > > > > Can contain data? but why I contain data there? If the data is big, it > should be at a separate file. Smaller data? Belonging to script? > > Good questions. > > > Could you give me a *real data example* which you are using? > > There are many examples in unitTest.leo. There are several advantages > to using separate nodes for small (or not-so-small) data: > > 1. The data is associated with the script (possibly in an @test node). > 2. There is no need for putting the data in a separate file. > 3. Putting the data in a node often simplifies the script. > > Take a look at unitTest.leo. In general I do not like auxiliary > files, especially those connected with unit tests. > > Edward > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/leo-editor?hl=en. > > -- -- Sincerely, HaveF -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
