RE: nfbtrans conversion

  • From: "DaShiell, Jude T. CIV NAVAIR 1490, 1, 26" <jude.dashiell@xxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Tue, 5 Jul 2011 09:16:01 -0400

I wish you wouldn't do that.  The intent of nfbtrans was to be as
cross-platform as possible originally.  Why not use #ifdef's for
Windows7-64 and add your drop-in functions if Windows7-64 is what's
running nfbtrans?  Code optimizers exist even for gcc you could use to
optimize executables for Windows7-64 even with the older functions left
in place in that source code.
Doing that would be an update for nfbtrans not just your own special
forked version.



-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Littlefield,
Tyler
Sent: Saturday, July 02, 2011 17:25
To: programmingblind@xxxxxxxxxxxxx
Subject: nfbtrans conversion

Hello all:
Since this isn't something that is a huge issue to keep up to date 
beyond it just working on 64-bit systems, I removed the secure warnings,

and started the conversions. There aren't to many issues I don't think 
so far, except the fact that a lot of the function calls (utime etc) are

no longer in windows. I'm yanking the code with older functions and 
writing drop-in replacements to do exactly (hopefully) what the old 
functions do, so hopefully it will work with minimal modifications. I'll

post later with progress and/or a working copy sometime this week.

-- 

Take care,
Ty
my website:
http://tds-solutions.net
my blog:
http://tds-solutions.net/blog
skype: st8amnd127
My programs don't have bugs; they're randomly added features!

__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind

Other related posts:

  1. Home
  2. programmingblind
  3. Archive
  4. 07-2011