search for: dynamic_

Displaying 5 results from an estimated 5 matches for "dynamic_".

Did you mean: dynamic
2008 May 01
0
[LLVMdev] optimization assumes malloc return is non-null
...: Replaceable: a C++ program may define a function with this function signature that displaces the default version defined by the C++ Standard library. Required behavior: Return a non-null pointer to suitably aligned storage (_basic.stc.dynamic_), or else throw a bad_alloc exception. This requirement is binding on a replacement version of this function. These _are_ the defined semantics. You cannot imagine any other semantic and substitute it. Any program that does, is outside the scope of the standard and has _no_ constr...
2013 Aug 20
0
sf bug 256 - Virtual functions in destructor
...to the extent that it has been constructed or destroyed. This is reflected in the rules for RTTI, exception handling (?14.4.7), and virtual functions. It is extremely unwise to rely on details of the order of construction and destruction, but that order can be observed by calling virtual functions, dynamic_ cast, or typeid (?15.4.4) at a point where the object isn?t complete. For example, if the constructor for Component in the hierarchy from ?15.4.2 calls a virtual function, it will invoke a version defined for Storable or Component, but not one from Receiver, Transmitter, or Radio. At that point of...
2008 Jul 27
2
Rails Cookbook review
Guys: Stuck at the mall today, and just had to crack Rails Cookbook, by O''Reily. It had a recipe for accepting dynamically created forms. The sample output looked like this (reconstructed): p params[:my_form] > ["1-1" => 0, "1-2" => 0, "1-3" => 0, "2-1" => 0, "2-2" => 0, "2-3" => 0,
2008 May 01
3
[LLVMdev] optimization assumes malloc return is non-null
On Apr 30, 2008, at 8:51 PM, David Vandevoorde wrote: >> This isn't safe in general unless you can (tightly) bound "n". You >> don't want to overflow the stack. > > Ah yes, of course. Does LLVM do this for known & small constant n? We don't do this currently, primarily because I haven't seen a case where it is a win yet: it would be very easy to
2008 May 01
3
[LLVMdev] optimization assumes malloc return is non-null
...C++ program may define a function with this function > signature > that displaces the default version defined by the C++ > Standard > library. > Required behavior: > Return a non-null pointer to suitably aligned > storage > (_basic.stc.dynamic_), or else throw a bad_alloc exception. > This > requirement is binding on a replacement version of this function. > > These _are_ the defined semantics. You cannot imagine any other > semantic and substitute it. Any program that does, is outside the > scope of the standard...