similar to: Action being called multiple times from weak connection?

I''m trying to add an application enabled/disabled flag in my application.. This is my code. [code=] # application.rb ... before_filter :check_enabled_flag private def check_enabled_flag application_flag = ApplicationFlag.find(:first) if application_flag.application_enabled redirect_to application_disabled_path and return end end[/code] and for some reason

Hi everyone, I''m looking for a shortcut to finding and updating or creating record depending on the results of the find. So, is there a shorter way to do it than this? @stuff = Stuff.find_by_foo_and_bar("yay","hooray") if @stuff: Stuff.update(@stuff.id, {:foo => "boo", :bar => "hoo"}) else Stuff.create({:foo => "boo",

Hello Has anyone else run into a problem with dovecot pop3 and sonicwall? A week after switching to dovecot we had two local customers call and report they could no longer download emails with attachments. It turned out to be the email macro filter on the router. After the first report I thought maybe the customer had just changed something or it was a fluke, but then a day later we had the

Last month I saw something funny which I can't reproduce anymore: A 0500 number in .au is a service phone number and are forwarded on exchange level to a real phonenumber. So if A calls B it gets forwarded to C. Very simple. Now the funny thing, on the phone of C, I saw both A and B as the "caller id". I've been asking around and trying to get it again with a private 0500

Hi, Sorry to bother, but I checked around and did not succed creating a bundle from six existing packages (which are checkable, installable, etc. individually). I carefully followed the procedure given in ch. 1.1.5 Package bundles. However, I am getting hoffmann at fluke:~/R/Sources >R CMD check cwhmisc * checking for working latex ... OK * using log directory

Hi, sorry for this lengthy post. I am using R-2.0.0 on Unix, compiled. Overview: A) R CMD check: Unaccounted top-level text B) In which sections of *.Rd is LaTeX notation allowed, where *not*? C) Codoc mismatches and polyvalent parameters D) Successful R CMD INSTALL and R CMD build E) cp ../Rd.sty . is copy necessary? F) latex ./CWHstat-manual.tex runs into trouble When running >R CMD

Hi, sorry for this lengthy post. I am using R-2.0.0 on Unix, compiled. Overview: A) R CMD check: Unaccounted top-level text B) In which sections of *.Rd is LaTeX notation allowed, where *not*? C) Codoc mismatches and polyvalent parameters D) Successful R CMD INSTALL and R CMD build E) cp ../Rd.sty . is copy necessary? F) latex ./CWHstat-manual.tex runs into trouble When running >R CMD

Hi, i have a dovecot setup with virtual users. Each user has 2 entries for his mailbox. One is with the username formatted as %username%@%default_realm% , the other %username%@%domain% I've done some tests with it, but I don't complete understand how it works - I've emptied all document in solr so it empty. Doveadm is instructed to do the same with 'doveadm -D -v fts rescan

Hi everyone, recently I've been fiddling with callgrind to profile the performance of clang and other llvm tools. Turns out that a lot of CPU time is spent on startup in _dl_lookup_symbol_x which is invoked a few thousands times to resolve all the weak object symbols which comes from LLVM code. Most of the symbols are virtual table definitions. Most probably there is a good reason why the

I am using Action Mailer as stated in RoR book... the mail seems to be correctly setup.. and I get the following log.. Sent mail: Date: Wed, 9 Aug 2006 19:54:04 +0200 From: support@alemat.com To: myself@mac.com Subject: Your password is ... Mime-Version: 1.0 Content-Type: text/html; charset=utf-8 _____________ Your username is barbare. Your new password is tDRvfzNvDF. Please login and change

> I'm not sure this is right. C code like this: > > int X; > > should compile to a .comm directive, not a .weak directive, right? right. According to GCC, "int x" should compile to ".comm x", but "int x __attribute__((weak))" should compile to --------------- .weak x x: .zero 4 --------------- It looks like we have a bug in

The attached patches makes all backends print a .weak directive for zero initialized variables. GCC does it on x86-64 and ARM. I assume that it should be done on all architectures. The patch also adds a test to the ARM backend? Should I copy it to all backends? Comments? Thanks, Rafael P.S.: I find the doFinalization code a bit confusing. Would you welcome a cleanup patch? -------------- next

On Sat, 9 Dec 2006, [UTF-8] Rafael Esp?ndola wrote: > The attached patches makes all backends print a .weak directive for > zero initialized variables. GCC does it on x86-64 and ARM. I assume > that it should be done on all architectures. > > The patch also adds a test to the ARM backend? Should I copy it to all > backends? I'm not sure this is right. C code like this:

On Mon, 18 Dec 2006, [UTF-8] Rafael Esp?ndola wrote: >> I'm not sure this is right. C code like this: >> >> int X; >> >> should compile to a .comm directive, not a .weak directive, right? > > right. > > According to GCC, "int x" should compile to ".comm x", but "int x > __attribute__((weak))" should compile to >

> Is there a semantic difference between the two? Just because GCC compiles > them to different things, it doesn't mean they do different things... Sorry for the long delay... On a x86 box I am able to use both declarations interchangeably. There is a problem if we have both a declaration and an use on the same file: We must print a ".weak" because of the use, but if we

moving to llvmdev. It always amused me that we have @a = weak global ... but @b = alias weak ... I decided to dig why that is. The best I could find was http://llvm.org/bugs/show_bug.cgi?id=1017#c15 Looking at some really old cold then suggests that the reason was that the old bison based parser hard a reduction for alias linkages and another one for global variable linkages. Putting the

>> The days of the old .ll parser are long gone, but is it too late to >> change? In case it is not, the attached patches implement just that >> :-) > I'm afraid you need to provide syntax autoupgrade until 4.0 Why, we moved to doing autoupgrade via bitcode quiet some time ago. There were quiet a few format changes to the .ll in the process. Cheers, Rafael

I am implementing weak linkage support on the ARM backend and I noticed this code on the X86 and PPC backends: ------------------------------------------------ // If the initializer is a extern weak symbol, remember to emit the weak // reference! if (const GlobalValue *GV = dyn_cast<GlobalValue>(C)) if (GV->hasExternalWeakLinkage()) ExtWeakSymbols.insert(Mang->getValueName(GV));

On Thu, 7 Dec 2006, [UTF-8] Rafael Esp?ndola wrote: > The attached patch makes the ASM printer print the ".weak" directive > when a weak symbol is added to a constant pool. > > I need something similar to it in order to bootstrap gcc on ARM. --- lib/CodeGen/AsmPrinter.cpp 7 Dec 2006 01:30:31 -0000 1.120 +++ lib/CodeGen/AsmPrinter.cpp 7 Dec 2006 13:00:17 -0000 @@

The attached patch makes the ASM printer print the ".weak" directive when a weak symbol is added to a constant pool. I need something similar to it in order to bootstrap gcc on ARM. Any comments? Best Regards, Rafael -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm.patch Type: text/x-patch Size: 1816 bytes Desc: not available URL: