[dylan-foundry/posix-sockets] 87d3fe: [posix-sockets] send has start:/end:, not offset:.

GitHub <[email protected]> Thu, 03 Dec 2015 08:06:32 -0800

Newsgroups	gmane.comp.lang.dylan.gwydion.cvs
Message-ID	<566068885fc9e_57573ff4ef0712b8112114@hookshot-fe5-cp1-prd.iad.github.net.mail>

  Branch: refs/heads/master
  Home:   https://github.com/dylan-foundry/posix-sockets
  Commit: 87d3fe4c3b86600c40b2500e51d73eb87a7e559a
      https://github.com/dylan-foundry/posix-sockets/commit/87d3fe4c3b86600c40b2500e51d73eb87a7e559a
  Author: Bruce Mitchener <[email protected]>
  Date:   2015-12-03 (Thu, 03 Dec 2015)

  Changed paths:
    M posix-sockets/bindings.dylan

  Log Message:
  -----------
  [posix-sockets] send has start:/end:, not offset:.

* posix-sockets/bindings.dylan
  (send): Use start: and end: to control what is written rather
   than just offset:. This makes it closer to other APIs in
   Dylan that deal with subsequences.


  Commit: 8c562548956fee73fca5390e8ef1a64ac152193d
      https://github.com/dylan-foundry/posix-sockets/commit/8c562548956fee73fca5390e8ef1a64ac152193d
  Author: Bruce Mitchener <[email protected]>
  Date:   2015-12-03 (Thu, 03 Dec 2015)

  Changed paths:
    M posix-sockets/bindings.dylan

  Log Message:
  -----------
  [posix-sockets] <byte-vector-like> -> <byte-sequence>.

* posix-sockets/bindings.dylan
  (<byte-vector-like>): Rename to <byte-sequence> as this seems more
   typical for Dylan.
  (recv): Update name of the type of data parameter.
  (send): Likewise.


Compare: https://github.com/dylan-foundry/posix-sockets/compare/805b7a81c304...8c562548956f

_______________________________________________
chatter mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/chatter