search for: mcpp

...a, as well as any required versions of DOS and Windows products will be available on the test network. Other software will depend on the participants bringing versions of their software along. We hope to be able to get a varied mixture of CIFS implementations for testing. My company has signed the MCPP license with Microsoft, are we welcome ? Yes, although of course we would expect that your attendees please respect the MCPP licensing process and not divulge any information you have learned from the MCPP documents. You are especially welcome to bring equipment running your CIFS implementation so...

...a, as well as any required versions of DOS and Windows products will be available on the test network. Other software will depend on the participants bringing versions of their software along. We hope to be able to get a varied mixture of CIFS implementations for testing. My company has signed the MCPP license with Microsoft, are we welcome ? Yes, although of course we would expect that your attendees please respect the MCPP licensing process and not divulge any information you have learned from the MCPP documents. You are especially welcome to bring equipment running your CIFS implementation so...

...has some > features in it that he needs for source to source transformation. I > would like us to all use the same one. > I'd like to clarify my intentions here. I designed the preprocessor integration in such a way that it doesn't depend on the specific preprocessor too much. MCPP is nice in that it's BSD, but it's rather slow, so no need to require people to use it. Users can implement the undo-log preprocessor using libcpp or maybe yank it out of clang which is also BSD. Taras

On 12/21/07, Richard Pennington <rich at pennware.com> wrote: > I'm a little further along now. I've started to put together a simple > driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think > it works). Er. Hm. Can you explain the name? The problem with names like "ellsif" is that it sounds like "else if". I like the

...s in it that he needs for source to source transformation. I > > would like us to all use the same one. > > > I'd like to clarify my intentions here. > I designed the preprocessor integration in such a way that it doesn't > depend on the specific preprocessor too much. MCPP is nice in that it's > BSD, but it's rather slow, so no need to require people to use it. > Users can implement the undo-log preprocessor using libcpp or maybe yank > it out of clang which is also BSD. > > Taras >

...because it does not require this! (plus it provides more consistent performance, it's way easier to debug/enhance/profile within one process etc. etc.) Honestly, old lld is very much like LLVM in that I can freely use it in my environment, whereas new lld reminds me of my experience integrating mcpp (a C preprocessor) a few years ago into an in-engine shader compiler with all the same issues (exit() on error, stdout, etc.) that had to be worked around by modifying the codebase. Arseny On Thu, Jan 21, 2016 at 11:14 AM, Chandler Carruth <chandlerc at gmail.com> wrote: > On Thu, Jan 2...

...this! (plus it provides more consistent performance, it's way easier to >> debug/enhance/profile within one process etc. etc.) Honestly, old lld is >> very much like LLVM in that I can freely use it in my environment, whereas >> new lld reminds me of my experience integrating mcpp (a C preprocessor) a >> few years ago into an in-engine shader compiler with all the same issues >> (exit() on error, stdout, etc.) that had to be worked around by modifying >> the codebase. >> > > I'm not going to argue that we don't want to support the librar...

I'm a little further along now. I've started to put together a simple driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think it works). The file being compiled is a "printf" function. Here are timing results for optimized and unoptimized runs: [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i -time-actions Adding test/ofmt.i as a preprocessed C file

> There are probably others, but this is the gist of it. Now, you could still > design everything with the simplest imaginable API, that is incredibly > narrow and specialized for a *single* user. But there are still fundamentals > of the style of code that are absolutely necessary to build a library. And > the only way to make sure we get this right, is to have the single user of

I am a rank newbie to Linux and wine. I am running Ubuntu Dapper on an AMD 1800 mhz machine, wine 0.9.15 Everything I have read says use the installer to load windows programs. Where is the installer? Thanks, -- Ron Thompson On the Beautiful Florida Space Coast, right beside the Kennedy Space Center, USA http://www.plansandprojects.com My hobby pages are here:

...libical-0.46-2.el5.x86_64 libicu-4.2.1-9.el6.x86_64 libidn-1.18-2.el6.x86_64 libiec61883-1.2.0-4.el6.x86_64 libimobiledevice-0.9.7-4.el6.x86_64 libini_config-0.5.1-28.el6_0.4.x86_64 libiptcdata-1.0.4-2.1.el6.x86_64 libisofs-1.1.2-1.el5.x86_64 libjpeg-6b-46.el6.x86_64 libldb-0.9.10-25.el5.x86_64 libmcpp-2.7.2-4.1.el6.x86_64 libmpcdec-1.2.6-6.1.el6.x86_64 libmtp-1.0.1-2.el6.x86_64 libmusicbrainz3-3.0.2-7.el6.x86_64 libnice-0.0.9-3.el6.x86_64 libnih-1.0.1-6.el6.x86_64 libnl-1.1-12.el6_0.1.x86_64 libnotify-0.5.0-1.el6.x86_64 libogg-1.1.4-2.1.el6.x86_64 liboil-0.3.16-4.1.el6.x86_64 libopenraw-0.0.5-4....