[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: wrapToPi function
From: |
Mike Miller |
Subject: |
Re: wrapToPi function |
Date: |
Tue, 8 Dec 2015 14:19:21 -0500 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Tue, Dec 08, 2015 at 12:15:55 -0500, Nicholas Jankowski wrote:
> 1 - does anyone generally care about unicode, etc. character sets in
> the source? I only ask because the O in Oscar renders quite
> differently depending on my browser setting, and my default text
> editor sees it as it's saved, which isn't with the accent. I'm
> unfamiliar with whether there's a preferred set to use or if it
> matters.
Files should be UTF-8 encoded (without BOM, and with Unix line endings
while we're at it). Òscar's file looks correct to me.
> 2 - Oscar, seems like there are 2 or three nearly identical functions
> also not implemented:
> wrapTo180, wrapTo2Pi, wrapToP360.
>
> Those seems like minor changes to what you've written for wraptopi.
> Would you be able to post those along with WrapToPi?
I'd also ask if there is a performance reason for writing the function
in C++, m-files make for easier maintenance and installation.
--
mike
- wrapToPi function, Oscar, 2015/12/07
- Re: wrapToPi function, Mike Miller, 2015/12/08
- Re: wrapToPi function, Nicholas Jankowski, 2015/12/08
- Re: wrapToPi function,
Mike Miller <=
- Re: wrapToPi function, Oscar, 2015/12/08
- Re: wrapToPi function, Nicholas Jankowski, 2015/12/08
- file encodings (was: wrapToPi function), Mike Miller, 2015/12/09
- Re: file encodings (was: wrapToPi function), Nicholas Jankowski, 2015/12/09
- Re: file encodings (was: wrapToPi function), Mike Miller, 2015/12/09