Reverted chances from commit cee31ae, which intercepted parsing of network()

constructor calls; this seems to have caused havoc with many packages,
unfortunately in ways that were not caught(!) by revdepcheck.  I believe that
this change had been made with the intent of improving handling of certain
complex assignment calls involving NAs, but it changes dispatching in
a manner that turns out not to work well.

Author: CarterButts

DESCRIPTION

@@ -1,6 +1,6 @@
 Package: network
 Version: 1.19.0
-Date: 2024-12-06
+Date: 2024-12-07
 Title: Classes for Relational Data
 Authors@R: c(
     person("Carter T.", "Butts", role=c("aut","cre"), email="buttsc@uci.edu"),

R/constructors.R

@@ -6,7 +6,7 @@
 # David Hunter <dhunter@stat.psu.edu> and Mark S. Handcock
 # <handcock@u.washington.edu>.
 #
-# Last Modified 06/08/21
+# Last Modified 12/07/24
 # Licensed under the GNU General Public License version 2 (June, 1991)
 # or greater
 #
@@ -43,11 +43,9 @@ network<-function(x, vertex.attr=NULL, vertex.attrnames=NULL,
                 multiple=FALSE, bipartite=FALSE, ...)
 {
   #Initialize the network object
-  mc <- match.call()
-  mc$vertex.attr <- NULL
-  mc[[1]] <- as.name("as.network")
-  g <- eval.parent(mc)
-
+  g<-as.network(x,directed=directed,hyper=hyper,loops=loops,
+              multiple=multiple,bipartite=bipartite,...)
+	      
   #Add vertex attributes, if needed
   if(!is.null(vertex.attr)){
     #Create vertex attribute names, if needed