Re: [Boost-bugs] [Boost C++ Libraries] #2534: Removing gcc warning

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2534: Removing gcc warning
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-04-29 03:25:40

#2534: Removing gcc warning
  Reporter: richard_at_[hidden] | Owner: chris_kohlhoff
      Type: Bugs | Status: closed
 Milestone: Boost 1.38.0 | Component: asio
   Version: Boost 1.37.0 | Severity: Cosmetic
Resolution: fixed | Keywords: gcc warning

Comment(by anonymous):

 Replying to [comment:2 anonymous]:
> Is the workaround suggested here safe? The warning is there for a good
 reason, I presume.

 AFAIK, the result of a write() should always be checked: the socket or NFS
 may have gone down, the drive could be full, etc. If this case is just
 debugging information, or some kind of optional output, ignoring the
 status might be fine, but IMHO it needs comments to explicitly explain why
 it is safe.

Ticket URL: <>
Boost C++ Libraries <>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:00 UTC