Displaying 20 results from an estimated 1508 matches for "destructs".
Did you mean:
destruct
2002 Feb 23
3
Non-destructive channel reversal
I'd like to know if there's a way to non-destructively reverse L-R channels
in an ogg vorbis file?
I've been recording live classical sources, but until tonight haven't
listened to them on anything with even approaching decent stereo separation.
Well, you guessed it. Why the hell are the violins on the right and the
brass on the left? Checked my equipment and sure enough, cable
2009 Mar 10
1
surprising behaviour of names<-
playing with 'names<-', i observed the following:
x = 1
names(x)
# NULL
'names<-'(x, 'foo')
# c(foo=1)
names(x)
# NULL
where 'names<-' has a functional flavour (does not change x), but:
x = 1:2
names(x)
# NULL
'names<-'(x, 'foo')
# c(foo=1, 2)
names(x)
# "foo" NA
2010 Mar 19
1
[LLVMdev] Checker for destruction-needing classes allocated in BumpPtrAllocators?
Hi Ted,
Doug said you might have a clang-based checker that would detect when
people allocate memory with a BumpPtrAllocator and then construct a
class into it that needs destruction. In killing valgrind-found memory
leaks in LLVM, I've found several instances of this mistake. They
often involve SmallVectors, which only show up as leaks in valgrind if
they happen to overflow their static
2006 Apr 12
1
Doing destructive actions with a GET request
I know that you should always use a POST to perform actions that are
destructive. I intend to break this rule and use a GET, but before I do,
I''d like to know if there is a better way of doing this:-
I have an account edit form for the user to make changes to their profile.
They have to be logged-in to do this. The problem is I have a
file_column field within the form which is storing
2019 Jan 16
2
Skipping construction/destruction of stack allocated objects
Hello,
For performance reasons, I would like to provide a way to skip
construction/destruction of objects that are stack allocated. Typically,
C-style arrays of std::complex create an initialization loops that is
almost always unnecessary.
I am thinking of providing an __attribute__((uninitialized)) that can be
applied to an object declaration:
{
std::complex<float> foo[64][64]
2007 Mar 21
4
Problem with PaintDC(MSW)
...nt passed to EVT_PAINT
handler, while setting
Wx::BG_STYLE_CUSTOM as a background style for the window.
Maybe alternative solution could be created, i.e hand crafting swig''ged
''paint'' function taking a ruby block,
which creates the PaintDC, yields it to the block, and destructs it
before leaving the function?
A.K.
2004 Jul 05
3
Randy Bush is a destructive force with a hidden professional agenda
. Monday, July 5, 2004
15:50:06 (-08:00hrs UTC)
Hello asterisk-users,
From the following post:
On Mon, 5 Jul 2004, Joe Baptista wrote:
> On Mon, 5 Jul 2004, Randy Bush wrote:
>> i did not criticize the protocol. remember, my question started
>> with
>>
>> >> i am looking at iax to
2013 Feb 14
5
using @releaseDomain to subscribe for domain destruction
Hello!. How can i use @releaseDomain from dom0 to subscribe for domain
destruction?
I''m try to add watch for @releaseDomain path with token equal of
needed domain id. But when another domain dies, i get domain that i
provide via token to xs_watch.
Is that possible to get id of domain what released from xenstore?
--
Vasiliy Tolstov,
Clodo.ru
e-mail: v.tolstov@selfip.ru
jabber:
2009 Mar 24
1
Is the net rpc vampire at all destructive to a NT4 PDC?
Reading through the Samba3 -By Example guide and I'm confused with the
statement section 9.2
http://www.samba.org/samba/docs/man/Samba-Guide/ntmigration.html#id2594565
about accessing the SAM and Security sections of the registry will render
the PDC non operable.
Its clear from the text if you go and edit the registry(regedit etc..) so
you can read the entries your PDC will not work.
2009 Mar 24
0
Is the net rpc vampire at all destructive to a NT4 PD C?
"net rpc vampire ..." does NOT set the SAM or SECURITY hives of the
registry to "readable", which is what renders the PDC non-operable.
"net rpc vampire ..." is safe to use as many times as it takes to get
comfortable with the process. I did it my self when I was converting
our "labs" NT4 domain to Samba.
--
2009 Nov 04
0
channel destruction after a transfer call
Hi,
we're using Asterisk 1.6.1.1.
We've got a problem during a transfer call concerning the destroying of
the unused channel.
At the beginning we have a call A -> B (A and B being two user).
With the AMI interface we ask the redirection of:
- case 1: the caller (user A)
- case 2: the called (user B)
to the extension C (not a user but a simple "Park()" dialplan
application).
2009 Nov 12
0
Scheduling destruction of SIP dialog
Hello,
I got situation which is unclear for me, hope somebody could explain this.
A calls to B
INVITE sent from A to B
B responds with 100 Trying
B responds with 183 Progress
After 10 seconds: Asterisk CLI: Scheduling destruction of SIP dialog '..' in
32000 ms (Method: INVITE)
Asterisk sends CANCEL _instantly_
B responds with 200 OK and 487 Request Terminated
Asterisk confirms 102 ACK
2014 Apr 29
0
Destruction of SIP dialog for OPTIONS requests
Hi all,
I'd like to verify whether an Asterisk behaviour is expected or not, and
ask for advice for the best solution.
I have Asterisk 1.8.17.0 on debian wheezy, listening on UDP and TCP 5060,
and TLS 5061.
Asterisk is part of a dispatcher set in Kamailio (4.1.3), and is marked as
AP (Active Probing): this means that Kamailio sends an OPTIONS request
every N seconds to verify Asterisk is
2015 Jul 28
0
[LLVMdev] Clang devirtualization proposal
Having read through the proposal, I feel like I missing some of the
background to understand the problem you're trying to solve.
My mental model is that construction of an object creates a new abstract
location in an infinite heap with each object infinitely far apart.
Destruction of the object destroys the abstract location. As a result,
destructing one object and constructing another
2013 Feb 09
3
[LLVMdev] ManagedStatic and order of destruction
I'm curious about the design rationale for how ManagedStatic instances are
cleaned up, and I'm hoping someone can shed some light on it.
Currently, ManagedStatic objects are cleaned up when llvm_shutdown()
traverses the global list of initialized objects and calls destroy() on
each. This leads to two questions:
1. An assertion enforces that the objects are deleted in reverse order of
2015 Jul 29
2
[LLVMdev] [cfe-dev] Clang devirtualization proposal
On Tue, Jul 28, 2015 at 10:58 AM, Philip Reames <listmail at philipreames.com>
wrote:
> Having read through the proposal, I feel like I missing some of the
> background to understand the problem you're trying to solve.
>
> My mental model is that construction of an object creates a new abstract
> location in an infinite heap with each object infinitely far apart.
>
2013 Feb 13
0
[LLVMdev] ManagedStatic and order of destruction
Right, I'm suggesting we keep llvm_shutdown() for users who want this
control, but also destroy still-live ManagedStatic instances if
llvm_shutdown() is not called. This helps in the case where there is not a
clear time when llvm_shutdown() can be called, especially given that LLVM
cannot be resurrected in the same process due to current limitations in the
pass registry, and perhaps
2006 Nov 22
1
Zombies?
Hey all,
Quick question about handling completed workers...
Most of my workers are one-offs that just let me spin off a long-running
file transfer process and then they just need to self-destruct when
completed. Thus, at the end of my do_work, I just call self.delete to (in
theory) self-destruct.
However, while checking the jobs.size from the console, I''ve noticed that
this
2007 May 22
0
[1029] trunk/wxruby2/swig/classes/MenuBar.i: Add special GC protection for Wx::Menu to prevent premature destruction
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2019 Oct 23
0
[PATCH net-next 13/14] vsock: prevent transport modules unloading
This patch adds 'module' member in the 'struct vsock_transport'
in order to get/put the transport module. This prevents the
module unloading while sockets are assigned to it.
We increase the module refcnt when a socket is assigned to a
transport, and we decrease the module refcnt when the socket
is destructed.
Reviewed-by: Stefan Hajnoczi <stefanha at redhat.com>