cygwin vs activestate...

Jason Pyeron jpyeron at pyerotechnics.com
Sun Oct 26 11:08:47 UTC 2003


I am just asking to be flamed here but in light of several ActiveState 
only errors and cygwin now capability to install a tiny perl setup.


Should we look into cygwin?

it uses less disk space. 
 34MB vs 56MB

it does not have activestates quirks bugs for win32
 bugs 129401, 143490, 154601, 183753, 185330, etc...

it is posix compliant and acts like it is on linux
 ActiveState's Perl  functions which act differently:
  "-X", "binmode", "chmod", "chown", "chroot", "crypt", "dbmclose",
  "dbmopen", "dump", "endgrent", "endhostent", "endnetent", "endpro-
  toent", "endpwent", "endservent", "exec", "fcntl", "flock", "fork",
  "getgrent", "getgrgid", "gethostent", "getlogin", "getnetbyaddr", "get-
  netbyname", "getnetent", "getppid", "getprgp", "getpriority", "getpro-
  tobynumber", "getprotoent", "getpwent", "getpwnam", "getpwuid", "get-
  servbyport", "getservent", "getsockopt", "glob", "ioctl", "kill",
  "link", "lstat", "msgctl", "msgget", "msgrcv", "msgsnd", "open",
  "pipe", "readlink", "rename", "select", "semctl", "semget", "semop",
  "setgrent", "sethostent", "setnetent", "setpgrp", "setpriority", "set-
  protoent", "setpwent", "setservent", "setsockopt", "shmctl", "shmget",
  "shmread", "shmwrite", "socket", "socketpair", "stat", "symlink",
  "syscall", "sysopen", "system", "times", "truncate", "umask", "unlink",
  "utime", "wait", "waitpid"






-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                   http://www.pyerotechnics.com   -
- Partner & Sr. Manager         Pyerotechnics Development, Inc. -
-                               500 West University Parkway #1S -
- +1 (410) 808-6646             Baltimore, Maryland  21210-3253 -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

This message is for the designated recipient only and may contain 
privileged, proprietary, or otherwise private information. If you 
have received it in error, purge the message from your system and 
notify the sender immediately.  Any other use of the email by you 
is prohibited.






More information about the developers mailing list