search for: forseeable

After much delay, I have finally reached the point in my work where I need to implement some kind of exception handling. I understand that "unwind" is currently unimplemented and will remain so for the forseeable future. In the mean time, are there any examples available for implementing Java or Python-style exceptions using __cxa_throw or something similar? I've read and re-read the various docs on exception handling and I'm not attaining understanding. I'm mainly interested in knowing how...

...an simply change ksdevice=eth0? to >> bootdev=eth0, correct? > I believe you can just leave both off (IIRC for CentOS 6 as well) if you > add "ipappend 2" to the pxelinux stanza. > I probably should have clarified that we're not using PXE and probably won't for the forseeable future.? This is just a simple netinstall disc/flash drive boot. -- Mark Haney Network Engineer at NeoNova 919-460-3330 option 1 mark.haney at neonova.net www.neonova.net

...d from using Dovecot over UW when staying with mbox format: http://whizzo.uoregon.edu/public/src/mailperf/results.html I had too much cached for this set of tests, and I am going to re-run some with the recommended cache settings...so stay tuned. Anyway, we are stuck with the mbox format for the forseeable future, and I noticed how hard hitting Dovecot is on initial access to a large mailbox, so we need a way to pre-create some of those indexes. I saw in the docs that such an indexer has been planned, but does anyone have a hack for doing it now? -- Anthony Kay Phone: (541) 3...

...hing that the current gcc front end generates that wouldn't fit an old-style GenericValue? I'm wondering if this might be an interim approach that would avoid me needing to rewrite huge amounts of code, and since we're not likely to be supporting anything other than C and C++ in the forseeable future, it makes some sense. Model checking VHDL and Verilog can come later. :-) >> The new GenericValue seems to have morphed into a struct, >> and looks like it's probably not intended to work in the same way as the >> old GenericValue class. >> > > Right...

Le mercredi 30 ao?t 2017 ? 12:11 +0530, Nigel Babu a ?crit?: > Hello, > > To reduce confusion, we've setup docs.gluster.org pointing to > gluster.readthedocs.org. Both URLs will continue to work for the > forseeable > future. > > Please update any references that you control to point to > docs.gluster.org. At > some point in the distant future, we will switch to hosting > docs.gluster.org on > our own servers. > > RTD will set up a canonical link to docs.gluster.org[1]. Over time,...

...s package isn't listed for download any longer, nor are releases posted to http://downloads.asterisk.org/pub/telephony/ . That said, looks like it's still available in svn, http://svnview.digium.com/svn/asterisk-addons/tags/1.6.1.1/ . So just wondering if addons will be around for the forseeable future? - Chris

Hello, To reduce confusion, we've setup docs.gluster.org pointing to gluster.readthedocs.org. Both URLs will continue to work for the forseeable future. Please update any references that you control to point to docs.gluster.org. At some point in the distant future, we will switch to hosting docs.gluster.org on our own servers. RTD will set up a canonical link to docs.gluster.org[1]. Over time, this will change update the results on search...

...rrent gcc > front end generates that wouldn't fit an old-style GenericValue? I'm > wondering if this might be an interim approach that would avoid me > needing to rewrite huge amounts of code, and since we're not likely to > be supporting anything other than C and C++ in the forseeable future, it > makes some sense. Model checking VHDL and Verilog can come later. :-) Right now, the only interesting thing is 128-bit integers. You can get these on 64-bit targets if you use some funky GCC extensions. Normal code only produces "usual" sized integers. -Chris -- ht...

...ael Scherer a ?crit : >> Le mercredi 30 ao?t 2017 ? 12:11 +0530, Nigel Babu a ?crit : >> > Hello, >> > >> > To reduce confusion, we've setup docs.gluster.org pointing to >> > gluster.readthedocs.org. Both URLs will continue to work for the >> > forseeable >> > future. >> > >> > Please update any references that you control to point to >> > docs.gluster.org. At >> > some point in the distant future, we will switch to hosting >> > docs.gluster.org on >> > our own servers. >> > &gt...

...dovecot. Evolution stores its mail in maildir format (fully standards compatible, I think); I would be using the maildir format in dovecot. Is there anything in the wiki, etc. explaining exactly how to do this? Why do this? Evolution is hopelessly broken, and is not likely to be fixed in the forseeable future, and I would like to keep my mails in maildir form. Reviews of kmail are very bad, and thunderbird uses the mbox format for storage. Thanks in advance - jon

...017 ? 14:02 +0100, Michael Scherer a ?crit?: > Le mercredi 30 ao?t 2017 ? 12:11 +0530, Nigel Babu a ?crit?: > > Hello, > > > > To reduce confusion, we've setup docs.gluster.org pointing to > > gluster.readthedocs.org. Both URLs will continue to work for the > > forseeable > > future. > > > > Please update any references that you control to point to > > docs.gluster.org. At > > some point in the distant future, we will switch to hosting > > docs.gluster.org on > > our own servers. > > > > RTD will set up a canon...

Hi Talin, Talin wrote: > After much delay, I have finally reached the point in my work where I > need to implement some kind of exception handling. I understand that > "unwind" is currently unimplemented and will remain so for the > forseeable future. > > In the mean time, are there any examples available for implementing Java > or Python-style exceptions using __cxa_throw or something similar? I've > read and re-read the various docs on exception handling and I'm not > attaining understanding. > > VMK...

.... (C) Some other > option. (C) Some other option. I recommend that you stick with the release_19 branch of both llvm and llvm-poolalloc. I and others are actively using these branches, so llvm-poolalloc bug fixes will most likely be made to this branch in addition to mainline CVS for the forseeable future. The release_19 branch of llvm-poolalloc is designed to always work with the release_19 branch of LLVM, which has a fixed API and bytecode format. Someday, the CVS HEAD llvm-poolalloc will compile against CVS HEAD llvm, but it doesn't at the moment. LLVM has undergone major changes...

...t; front end generates that wouldn't fit an old-style GenericValue? I'm >> wondering if this might be an interim approach that would avoid me >> needing to rewrite huge amounts of code, and since we're not likely to >> be supporting anything other than C and C++ in the forseeable future, it >> makes some sense. Model checking VHDL and Verilog can come later. :-) >> > > Right now, the only interesting thing is 128-bit integers. You can get > these on 64-bit targets if you use some funky GCC extensions. Normal code > only produces "usual&...

...;> Le mercredi 30 ao?t 2017 ? 12:11 +0530, Nigel Babu a ?crit : > >> > Hello, > >> > > >> > To reduce confusion, we've setup docs.gluster.org pointing to > >> > gluster.readthedocs.org. Both URLs will continue to work for the > >> > forseeable > >> > future. > >> > > >> > Please update any references that you control to point to > >> > docs.gluster.org. At > >> > some point in the distant future, we will switch to hosting > >> > docs.gluster.org on > >> >...

...wrote: >>> I recommend that you stick with the release_19 branch of both llvm and >>> llvm-poolalloc. I and others are actively using these branches, so >>> llvm-poolalloc bug fixes will most likely be made to this branch in >>> addition to mainline CVS for the forseeable future. The release_19 >>> branch of llvm-poolalloc is designed to always work with the release_19 >>> branch of LLVM, which has a fixed API and bytecode format. >> I did not realize that you guys were checking in changes to the release_19 >> branch. I have to disagr...

> I recommend that you stick with the release_19 branch of both llvm and > llvm-poolalloc. I and others are actively using these branches, so > llvm-poolalloc bug fixes will most likely be made to this branch in > addition to mainline CVS for the forseeable future. The release_19 > branch of llvm-poolalloc is designed to always work with the release_19 > branch of LLVM, which has a fixed API and bytecode format. I did not realize that you guys were checking in changes to the release_19 branch. I have to disagree with this as release_19 is sup...

ANR is a international news station we were testing on icecast over the weekend the quality great we chose mp3 because anyone can hear it. linux, mac. or windblows. also wanted to use a linux server, which is far more reliable than a windows machine ( always dropping out for some reason ) If the ogg only rule is permanent we will have to talk very nicely to our system admin to switch to ogg with a

I have a few questions on using dsa now that it has been moved out of llvm. I have llvm -r release_19 checked out from cvs, and llvm-poolalloc -r release_19 checked out from cvs into the projects directory, as John Criswell previously suggested. 1) I have some compiler transforms that I'm writing that use DSA. They can no longer find the header files for DSA. My transforms are located

Hello everyone, A new project I''m starting on has a "database" consisting of many 10s of thousands of XML documents. They all conform to a common schema. The project consists pretty much exclusively of searching and presenting existing data - there''s no need (for the forseeable future) to be able to input or update XML documents in the database. Unlike (say) blog data, where there''s typically a date, name and a bunch of text, each document is fairly highly structured - there''s quite a few separate XML attributes and entities within each doc - and the fo...