EVOLUTION-MANAGER
Edit File: list.merge.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>R: Merge a number of named lists in sequential order</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <link rel="stylesheet" type="text/css" href="R.css" /> </head><body> <table width="100%" summary="page for list.merge {rlist}"><tr><td>list.merge {rlist}</td><td style="text-align: right;">R Documentation</td></tr></table> <h2>Merge a number of named lists in sequential order</h2> <h3>Description</h3> <p>The function merges a number of lists in sequential order by <code>modifyList</code>, that is, the later list always modifies the former list and form a merged list, and the resulted list is again being merged with the next list. The process is repeated until all lists in <code>...</code> or <code>list</code> are exausted. </p> <h3>Usage</h3> <pre> list.merge(...) </pre> <h3>Arguments</h3> <table summary="R argblock"> <tr valign="top"><td><code>...</code></td> <td> <p>named lists</p> </td></tr> </table> <h3>Details</h3> <p>List merging is usually useful in the merging of program settings or configuraion with multiple versions across time, or multiple administrative levels. For example, a program settings may have an initial version in which most keys are defined and specified. In later versions, partial modifications are recorded. In this case, list merging can be useful to merge all versions of settings in release order of these versions. The result is an fully updated settings with all later modifications applied. </p> <h3>Examples</h3> <pre> l1 <- list(a=1,b=list(x=1,y=1)) l2 <- list(a=2,b=list(z=2)) l3 <- list(a=2,b=list(x=3)) list.merge(l1,l2,l3) </pre> <hr /><div style="text-align: center;">[Package <em>rlist</em> version 0.4.6.2 <a href="00Index.html">Index</a>]</div> </body></html>