On Aug 13, 2013, at 6:23 PM, Mohit Daga wrote:
> pixrect modified to use icv api. It now no longer supports bytes_per pixel
> option and assumes 3 bytes for .pix files. Also prompting has been removed.
> Supports only command line arguments.
>
> Please check this revision for pixrect. I have r
Dear all,
On Wed, Aug 14, 2013 at 2:55 AM, wrote:
> Revision: 56814
> http://sourceforge.net/p/brlcad/code/56814
> Author: mohitdaga
> Date: 2013-08-13 21:25:08 + (Tue, 13 Aug 2013)
> Log Message:
> ---
> pixrect modified to use icv api. It now no longer supports byte
20'th Annual Tcl/Tk Conference (Tcl'2013)
http://www.tcl.tk/community/tcl2013/
September 23 - 27, 2013
Bourbon Orleans Hotel
New Orleans, Louisiana, USA
http://www.bourbonorleans.com/
Hello all.
This is a general reminder that the offer of reduced rates for rooms
at the conference hotel expires
On Aug 13, 2013, at 11:01 AM, phoenix <284281...@qq.com> wrote:This function is used to sort the array, so I think strict floating point comparison is reasonable. The original implementation is wrong because it just returns the result of minus (implicit conversion to int), which makes two floating
Hi Sean,
> You should also take note of our existing EQUAL(), NEAR_EQUAL(), ZERO(), and
> NEAR_ZERO() macros (as well as vector versions) in include/vmath.h
> To handle floating point fuzz, it may even be necessary to check if values
> are > -TOL, but requires forethought into what the number
Wu,You should also take note of our existing EQUAL(), NEAR_EQUAL(), ZERO(), and NEAR_ZERO() macros (as well as vector versions) in include/vmath.hTo handle floating point fuzz, it may even be necessary to check if values are > -TOL, but requires forethought into what the number means.Cheers!SeanOn
