search for: agnosticism

On 27 November 2016 at 16:10, Amara Emerson <amara.emerson at gmail.com> wrote: > No. Let's make one thing clear now: we don't expect the VL to be > changed on the fly, once the process is started it's fixed. Otherwise > things like stack frames with SVE objects will be invalid. This then forbids different lengths on shared objects, which in turn forces all objects in

Hey all -- I''ve been using enumerable char(1)''s with ''y'' and ''n'' values for my Boolean columns in Rails, but it strikes me there should be a better way. How do you setup columns that represent true/false-ness in your schemas on Rails? Wondering what kind of standard approaches there are other than me writing something like class MyEntity

...tter idea would be to generate some sort of metadata from these #ifdef's instead. > * Make sure that the code in the distribution bitcode is endian-agnostic 32-bit code. A sandbox will be needed on 64-bit systems or else a separate 64-bit bitcode package will still be required. > Endian agnosticism without using the preprocessor just seems... burdensome. However, if I'm grabbing the correct information here, you're saying that bitcode for x86 Linux would function on 32-bit ARM, PPC, and SPARC Linux (if endian-agnostic)? > * Make sure all external dependencies including LibC runti...

Hi Nate, I've successfully ported one bitcode from Linux to Mac to Windows.  All were x86 and the program was text-based, but I'd say my LLVM Wrapper would be worth some effort in the future if I could just get some help.  Currently it just wraps StdIO.h with its own functions. Here's some of what it would take to make portable bitcodes in C or LLVM Assembly: * Convert all

...as light as possible, and generation of heavy HTML is avoided. ANSI SQL calls and data types in queries and tables. database specific calls and datatypes are avoided whenever possible, and developers are encouraged to convert existing SQL calls and data types to ANSI SQL where possible. browser agnosticism in HTML and form generation, including cleaning up the HTML output of Bugzilla, and following all applicable Web standards. Bugzilla's notion of a "bug" is very general, and Bugzilla uses the term "bug" to track not only software bugs but also all other user-submitted tra...

...contains special purpose address registers) The strict distinction between pointers and integers is highly problematic because LLVM’s code generator implicitly converts all pointers to integers of the same width ... upon construction of the SelectionDAG. . . . As mentioned above, LLVM’s agnosticism regarding pointers initially makes it impos- sible to comply with the EABI as there is no way to tell whether an integer argument should go into an address register or a data register. However this document is dated circa 2008/2009 and I ask if this situation still remains the same today....

...quot;id"=>"2", "controller"=>"people", "image"=>{"data"=>#<StringIO:0x4c22474>}, "person"=>{"occupation"=>"", "schools"=>"", "religious_preference"=>"Agnosticism", "dislikes"=>"", "birthdate(1i)"=>"1988", "gender"=>"male", "birthdate(2i)"=>"12", "is_smoker"=>"0", "birthdate(3i)"=>"13", "first_name"=>&quo...

Hi, I have a User model, with a validates_uniqueness_of :login The generated SQL for the validation is: SELECT * FROM `users` WHERE (LOWER(users.login) = ''fernando'' AND users.id <> 10001) LIMIT 1; and it takes 0.13s to happen (my table has 10.000 rows) When I use the EXPLAIN instruction on it, it shows that it will use the primary_key as index, but this is not