search for: controvertial

Hi, I would like to be able to create new environments from package C code. AFAICT, this isn't allowed since both NewEnvironment and R_NewHashedEnv are declared in Defn.R. If exposing this isn't controvertial, I would submit a patch. However, I'm not sure where the declarations should go (Rdefines.h?) and whether they need to change to Rf_*. + seth

I downloaded current version of FLAC sources and compiled it with: * GCC 4.8.1 (MSYS from http://xhmikosr.1f0.de/tools/) * Intel C++ Composer XE 2013 update 5 * MSVS 2010 SP1 * MSVS 2012 update 3 (SSSE3 and SSE4.1 code was disabled for all compilers) Stereo 24-bit WAV file was encoded with -8 preset. Encoding time, in seconds: GCC 32-bit: 209 ICC 32-bit: 130 VS10 32-bit: 116 VS12 32-bit: 114

Hi all, I've just grabbed a copy of SVN head for libogg and 'make check' is failing: ./test_framing testing single page encoding... 0, (0), granule:0 ok. testing basic page encoding... 0, (0), granule:0 1, (1), granule:6151 ok. testing basic nil packets... 0, (0), granule:0 1, (1), granule:10247 ok. testing initial-packet lacing > 4k... 0, (0), granule:0

...ns on life times. Now, when we add a plain old pass, we CAN say, add a pass with traversal strategy A or B or C, or it'll default to run on module/whatever. Passmanager, would require a couple of extra methods to expose this new traversal management flexibility. Traversal strategies, this is controvertial, here I want to have all analysis we wish to use as traversal strategies to inherit from some class, which provides an accessor to get a simple forward iterator, or something in that vein. Now, unless I'm not seeing the difficulty in this, it shouldn't be TOO bad to implement the logic. I...

...just grabbed a copy of SVN head for libogg and 'make check' >> is failing: >The breakage happened in this commit: > > r17098 | gmaxwell | 2010-03-29 16:35:11 +1100 (Mon, 29 Mar 2010) | 1 line > Firstly, is gmaxwell on this list? [snip] > Secondly should be be trying controvertial changes in HEAD? Surely thats > what separate branches are for, so that the trunk never breaks like this. Nothing is broken. The libogg test-cases are especially particular checks on exact (non-normative) aspects of the library behaviour. This is fine for their intended use: catching compiler/...