search for: obsolescent

...tran.dg/assumed_charlen_function_3.f90 -O -pedantic-errors -S -o assumed_charlen_function_3.s (timeout = 300) /sw/src/fink.build/llvm-gcc42-2.4-1/llvm-gcc4.2-2.4.source/gcc/testsuite/gfortran.dg/assumed_charlen_function_3.f90:8.14: function is_OK (ch) ! { dg-warning "is obsolescent in fortran 95 1 Warning: CHARACTER(*) function 'is_ok' at (1) is obsolescent in fortran 95 /sw/src/fink.build/llvm-gcc42-2.4-1/llvm-gcc4.2-2.4.source/gcc/testsuite/gfortran.dg/assumed_charlen_function_3.f90:14.16: function more_OK (ch, fcn) ! { dg-warning "is obso...

AFAICs Simo's patch for bug 5535 was only applied to the 3.3 series. Does the closing comment in https://bugzilla.samba.org/show_bug.cgi?id=5535 mean that the inconsistencies about RID calculation won't be addressed in the 3.0 and 3.2 series? Does the fact that 3.3.2 always uses sambaNextRid mean that algorithmic RID allocation is doomed to obsolescence? Regards, Thierry

...rd, see e.g. <http://www.open-std.org/JTC1/SC22/WG14/www/standards.html>: > 6.11 Future language directions ... > 6.11.5 Storage-class specifiers > > The placement of a storage-class specifier other than at the beginning > of the declaration specifiers in a declaration is an obsolescent > feature. The attached patch (against SVN revision 72220) is a suggestion of how to eliminate the sources of such obsolescence warnings from the R source tree, including the example in the R-exts manual. The patch was originally made for r72218, and against that version it was tested succe...

...001 Free Software Foundation, Inc. Written by John Gilmore and Jay Fenlason. /notcygwin[508] gunzip R-2.2.1.tar.gz R-2.2.1.tar.gz: 0.2% -- replaced with R-2.2.1.tar /notcygwin[509] tar xf R-2.2.1.tar tar: This does not look like a tar archive tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: Error exit delayed from previous errors

There appear to be three acts_as_taggable implementations and I''m looking for a recommendation on which to use. - Gem - DHH plugin - Dema mixin The Gem implementation appears to be obsolescent, from what I can read on the lists and Google search. I like that the DHH plugin uses polymorphic associations because there will be lots of different taggable items in my application; however, adding and removing tags is a bolt-on, not designed-in feature. The Dema mixin (dema.ruby.com.br/articl...

On 03/11/03 00:25, Mark Spencer wrote: > As a side note, I strongly would like to see someone implement a > client using libiax2 which implements IAX2 instead of the (now > obsolescent) IAX version 1. I'm implementing a Java-based IVR server (and yes, I know Asterisk does IVR, and no, it's not flexible enough to do what I want and no, it doesn't integrate well with the Java systems we have, etc. hence my doing this). Currently it uses SIP (using the NIST JAIN-SIP st...

...ome guidance about how to | > prioritize my repairs. There are basically 4 categories of warnings from | > gfortran?s pedantic critique of my packages: | > | > 1. Some errant tab characters it doesn?t like, | > 2. Too many or too few continue statements | > 3. Horrible (and obsolescent) arithmetic and computed gotos | > 4. undeclared doubles and dubious conversions | > | > The last category seems relatively easy to fix and is potentially | > important, but the others seem more difficult to fix and altogether | > less important. The goto issues are all in code th...

So I had this crazy idea to put together a cheap video wall<https://lh6.googleusercontent.com/-GNJ97iKoU3Y/UumgZ62KESI/AAAAAAAAa8Y/t07wL1D7Tmk/w931-h698-no/IMG_20140125_210754.jpg> in my local hackerspace using a lot of screens suffering from planned obsolescence or at least a poor choice in their used caps and cheap - used Nvidia NVS 440 cards. During evaluation of Win 7/8 I noticed there

...e started to look into this, and I need some guidance about how to prioritize my repairs. There are basically 4 categories of warnings from gfortran?s pedantic critique of my packages: 1. Some errant tab characters it doesn?t like, 2. Too many or too few continue statements 3. Horrible (and obsolescent) arithmetic and computed gotos 4. undeclared doubles and dubious conversions The last category seems relatively easy to fix and is potentially important, but the others seem more difficult to fix and altogether less important. The goto issues are all in code that has been written long ago by o...

...`/d0/home/fgibbons/tmp/R2.1.0/R-2.1.0/src/library/Recommended' make[2]: Entering directory `/d0/home/fgibbons/tmp/R2.1.0/R-2.1.0/src/library/Recommended' begin installing recommended package VR WARNING: ignoring environment value of R_HOME tar: Skipping to next header tar: Archive contains obsolescent base-64 headers incomplete literal tree gzip: VR.tgz: invalid compressed data--format violated tar: Error exit delayed from previous errors ERROR: cannot extract package from 'VR.tgz' make[2]: *** [VR.ts] Error 1 make[2]: Leaving directory `/d0/home/fgibbons/tmp/R2.1.0/R-2.1.0/src/libra...

Dear all, We are excited to announce that the our CELLAR working group charter for the standardization of FFV1, Matroska, and FLAC has been made available for external review. What this means is that it is now under review and available for comment to the wider IETF community. Please send any comments you might have(including statement of support)to the IESG mailing list by November 9, 2015.

Hi Dmitry, Where were you expecting notice to have been given? If I recall correctly, the obsolescence of the C backend was mentioned many times on this mailing list, and as Owen notes, in the release notes since 2.8. I'm not trying to be snarky. You were obviously genuinely surprised by its removal, and that makes me wonder if where the core open source devs are expecting people to look for

Sorry if this is too "OT", but there is a particular relevance to postings to R-help. Of recent times, I have received several postings via R-help (and some other mailing-lists) in which the "_" character is inserted where, presumably, a space, " ", was intended. An example (received this morning) is below, which (from the headers) was originally sent through Yahoo

...eee-fp', that icc and ifc dont't understand. This flag is hard coded in the configure.ac file, and it seems that one cannot avoid it easily. That's bad, the configure script should be totally independent from any compiler, I think. * Many warnings refer to Fortran code that is obsolescent in Fortran 95 and/or in Fortran 90. Some code (like "ASSIGN") is even deleted in Fortran 95 * More serious things: (even dangerous?): ########################################## Comment 12 at (1592:blas.f) : This statement is obsolescent in Fortran 90 and deleted in Fortran 95...

...ion. I am admittedly somewhat concerned about the overall direction of the RHEL product. I fundamentally disagree with their Frozen Chosen approach to key software components. And with the lock-step forced upgrades that are the result. I am not at all certain that back-porting security fixes to obsolescent software is a profitable activity when often for much the same effort, if not less, the most recent software could be made to run on the older release without adverse effects elsewhere. However, I offer no answers and promote no particular course of action, saving only reflection of what is happen...

Dear Jim and Owen, Thanks for replies, I only kindly suggest some discussion on the maillist in such cases. Just in general, nasty precedents sometimes happen, for example on IRC I've recently seen some commits to Objective C were requested to be reverted, because they were commited without any discussion. Here things are certainly not that hard, but the point is the same: it is always nice

Dear all, I've also noticed C backend was removed a little bit... silently. In the end of March I only got open bugs closed by Benjamin Kramer in bugzilla, but they sounded like "decision is made". So the question is: it such silent removal a normal practice? In times of 3.0 release there were long discussions on what to drop and what to preserve, e.g. sparc backend, if I remember

Hello, My name is Sean Gilligan (wikiname: SeanGilligan) and I'd like to contribute to the CentOS wiki. Initially I'd like to do some documentation for Java (OpenJDK) on CentOS 5.3. I've used Fedora for years, but am getting tired of the obsolescence that keeps happening. I'm also very excited about having an integrated Java that I can use for actual server deployments. I

Hello, Does Xen support IA64 ? If not, is there a project to port Xen on IA64. Best Regards. Valerie. ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3

I have released a patch for klibc which changes off_t to 64 bits, and hopefully deals with most of the rest of the fallout. We shouldn't be using any obsolescent types anymore, except for struct statfs (I intend to hack that next so we use statfs64() and fstatfs64()). We're still using some older system calls, like sigaction() instead of rt_sigaction() where available, but that's a pure convenience. -hpa