search for: be_

@settings.should allow_publish_ip("127.0.0.1") fails with undefined method `allow_publish_ip'' for #<#<Class:0x2f8fd48>:0x2f5a968> @settings.should_allow_publish_ip("127.0.0.1") works fine This is rspec 0.8.2. http://rspec.rubyforge.org/documentation/expectations.html says that matching arbitrary predicates is deprecated and to see

On Dec 27, 2007 3:18 PM, Shot (Piotr Szotkowski) <shot at hot.pl> wrote: > Shot (Piotr Szotkowski): > > > I happily hand-compiled Ruby 1.9.0-0 into /home/shot/opt/ruby today > > and I''m running into a strange error with RSpec ? all my examples work > > perfectly with Ruby 1.8 but are considered peding on Ruby 1.9. > > FWIW, I get the same result with

...; - } > + offset = obj_idx * class->size; so we already know the `offset' before we call objidx_to_page_and_offset(), thus we can drop `struct size_class *class' and `obj_idx', and pass `long obj_offset' (which is `obj_idx * class->size') instead, right? we also _may be_ can return `cursor' from the function. static struct page *objidx_to_page_and_offset(struct page *first_page, unsigned long obj_offset, unsigned long *offset_in_page); this can save ~20 instructions, which is not so terrible for a hot path like obj_malloc(). what do you think? well...

...; - } > + offset = obj_idx * class->size; so we already know the `offset' before we call objidx_to_page_and_offset(), thus we can drop `struct size_class *class' and `obj_idx', and pass `long obj_offset' (which is `obj_idx * class->size') instead, right? we also _may be_ can return `cursor' from the function. static struct page *objidx_to_page_and_offset(struct page *first_page, unsigned long obj_offset, unsigned long *offset_in_page); this can save ~20 instructions, which is not so terrible for a hot path like obj_malloc(). what do you think? well...

...ldn't define it inline. >> >> > > You must not have written a lot of C++ template then. (Ha!) > You don't have the choice in this case, just check your STL header. I don't think that how standard library or STL headers _are_ written determines how they _should be_ written. (Templates don't force us to write excessive inline functions: Leave off the inline keyword and write a member function outside the class template definition, and it's no longer an inline function.) > >> >> FWIW, I've been involved in a couple of attempts...

David Vandevoorde a écrit : > > I don't think those are _good_ reasons though: If one doesn't want a C+ > + function to be inlined, one shouldn't define it inline. > > You must not have written a lot of C++ template then. You don't have the choice in this case, just check your STL header. > > FWIW, I've been involved in a couple of attempts by

Dear everyone, I posted a similar question to Stack Overflow there: https://stackoverflow.com/questions/46907554/binding-with-libiconv-failed-while-compiling-r-devel-on-ubuntu-17-04 and I was suggested to post my question here. I tried to compile R devel using Dirk Eddelbuettel's recipe (and many variants of it). Regardless of what I do, I have: === [...]/src/main/sysutils.c:794:

Hi all I have been pondering this for a while, but not yet seen a clean way to do it I have a few puppet classes (apache/ntp/mysql/bacula/nagios/etc) I would like to generate part of my bacula and nagios configs for each host based on which other classes that host belongs to (or to put it another way, I would like to export variables from classes which would be used by my bacula and nagios

...s is not an excuse). I just didn't and still don't understand how you do it, but this is probably not the good place to discuses this. please accept my sincere apologies. > > I don't think that how standard library or STL headers _are_ written > determines how they _should be_ written. > > (Templates don't force us to write excessive inline functions: Leave > off the inline keyword and write a member function outside the class > template definition, and it's no longer an inline function.) > What about multiple translation unit then? because...

...> | | int main( int argc, char **argv ) { | iconv_t cd = iconv_open( "UTF-8", "ISO-8859-1" ); | iconv_close( cd ); | return 0; | } | === | So libiconv seems to be indeed usable, but not during the linking. | | Where should I look? Something _must be_ wrong with your machine. We probably need more complete details of the configure and link steps. Do you ever have issues with building other CRAN packages from source? Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

Hi all What is the best strategy to add another storage to an existing virtual mail system ? Move some domains to the new storage and create symlinks ? Switch to dovecot hashing ? But in this case what is the easy-east way to migrate ? Thanks for any suggestions or tips !

>>> > > Aside from potentially needing smaller buffers for config files before > parsing (which seems trivial and unnecessary), what other benefits are > there to this strategy? > At the core, is that Syslinux is a general bootloader which gives access to a virtual filesystem.? It supports multiple open files, but not seeking or writing. <<< Please correct me if

Chris Lattner wrote: >>I don't grok this error message. Of course, -opt-a and -opt-b both work >>fine in isolation. >> >> > >You're right, this error message is terrible. As it turns out, all of >your passes invalidate all of the other passes, so C doesn't get A (which >is invalidated by B). The problem turns out to be a really trivial bug:

I came into this with my eyes wide open. I have read ABSOLUTELY EVERYTHING there is to be found on the net about avoiding echo problems BEFORE I even attempted to create a production system. Since lots of people are apparently using this in production environments now I just assumed that echo IS avoidable. As others have recommended, I created a test system with the proposed production

We''d like to get some feedback on RSpec 0.9 before we start pushing out releases via Rubyforge''s gem server and update the website. We have therefore made the first beta of 0.9 available - both prepackaged and tagged in subversion (see below). RSpec 0.9 introduces a new API for expectations, which essentially means that your underscores go away (there has been other discussions

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.