[cfe-dev] Raising LLVM minimum required, 'dumb question'

[Tim Toomay]

James

Good question.  If you look at the entire thing and tried to evaluate 
how big of a job you might become ill!

I have another dumb question...

How big of a job would it be to SIZE that job?  Maybe you could count 
the errors in one file, then multiply it times the number of files.

One way to size it is look at wxwidgets.  There is a lot more there than 
just fixing the api header stack, but you can see all the system calls, 
how they are wrapped etc, and the product WORKS across mac linux and 
windows, so its a good starting place.  It is not overly concerned with 
the latest c++ however.

On 8/25/2014 11:24 AM, cfe-dev-request at cs.uiuc.edu wrote:
> Message: 1
> Date: Mon, 25 Aug 2014 10:29:46 -0500
> From: James Gregurich<bayoubengal at mac.com>
> To: ?scar Fuentes<ofv at wanadoo.es>
> Cc:"cfe-dev at cs.uiuc.edu"  <cfe-dev at cs.uiuc.edu>
> Subject: Re: [cfe-dev] [LLVMdev] [RFC] Raising LLVM minimum required
> 	MSVC version to 2013 for trunk
> Message-ID:<BD6FBE02-9BA1-4EAE-9EF8-B4A8A1F6B6A6 at mac.com>
> Content-Type: text/plain; charset=utf-8
>
> I have a dumb question...
>
> How many actual known instances of alleged broken lines are there in the entire Microsoft API header stack?
>
> If one had the dream of just fixing the headers, how big of a job would it actually be?
>

-- 
Tim Toomay
Toomay Technologies Inc
www.ToomayTech.com

*****

NOTICE OF CONFIDENTIALITY: The information contained in this e-mail and attachment(s), if any, is legally protected pursuant to the Electronic Communications Privacy Act, 18 U.S.C. 2510, et seq., inter alia, and may contain privileged and confidential information.  This communication is intended only for the use of each individual named above.  If you know, or have any reason to believe, that you are not an intended recipient, you are hereby notified that any dissemination or duplication of this e-mail is prohibited.  There is and shall be no waiver of any privilege or confidence by your receipt of this transmission.  If you know or have any reason to believe that you received this e-mail in error, please immediately notify us by e-mail or collect telephone call.