search for: eventlistener

With Asterisk-Java the proposed solution to connect to multiple Asterisk servers is to create multiple AsteriskManagerConnection obeject. Each ManagerConnection handles its own thread so there is no need for custom thread handing code. All you have to do is to make sure is the EventListener objects you pass to these connections synchronize access to shared data (if there are such accesses). I think this approach is rather simple for the user and don't see a benefit in adding a proxy to that picture. =Stefan -- reuter network consulting Neusser Str. 110 50760 Koeln Germany Telef...

I work on the LLILC team, and we are trying to send debug line info through to the CoreCLR EE without using an EventListener because we need to send extra info (more than just available in DebugLoc) like if it’s a call instruction, a call site, etc. We thought extending AsmPrinterHandler would be useful since it seems to have information about debug locations, label offsets, and instruction specific information. From:...

Catching up on post-holiday emails. I may have comments on the more general stuff later, but wanted to respond to this bit more quickly. On Nov 22, 2012, at 3:05 AM, Chandler Carruth <chandlerc at google.com> wrote: > On Thu, Nov 22, 2012 at 1:53 AM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: >> s/ExecutionEngine/EE/ (or something like buzzword!) > > I don't

On Thu, Nov 22, 2012 at 1:53 AM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > s/ExecutionEngine/EE/ (or something like buzzword!) I don't really know the best bikeshed color here. Jim? My lame idea would be: ExecutionEngine -> JIT ExecutionEngine -> JIT/Legacy ExecutionEngine/MCJIT -> JIT/MC ExecutionEngine/OProfileJIT -> JIT/OProfile

Hi Andres, I also want to highlight the necessity of some form of C API, that others > already have. > <snip> > It's fine if the set of "somewhat stable" C APIs doesn't provide all the > possible features, though. Ok. This got me thinking about what a simple LLJIT API should look like. I have posted a sketch of a possible API on http://llvm.org/PR31103 . I

...registrations is NOT coming from RTDyldObjectLinkingLayer.cpp. I found this first by adding an additional debug statement (highlighted) thinking the `reinterpret_cast` may be at fault for the key mismatch. I never saw this print and I then realized my “Adding” vs. “Registering” mistake. // Run EventListener notifyLoaded callbacks. { std::lock_guard<std::mutex> Lock(RTDyldLayerMutex); dbgs() << "Registering MemMgr " << MemMgr << "\n"; auto LOIItr = LoadedObjInfos.find(MemMgr); assert(LOIItr != LoadedObjInfos.end() && "LoadedObjI...

...a lot of event listeners to handle this well, but there does not appear to be a ton of doc on draggable/dropable events, and how to use them. I understand onDrop, but I really really need a form of onPickUp event. Does anything like this exist? Is there any good documentation on events/eventListeners? I understand the concept (and I am using the onDrop event in the demo thingy below) I just do not know which events are available, etc? I think the general idea is to do this flow: Make a javascript map of the pieces (multi-dimensional array?) Make the active players pieces draggable...

...#39;m not sure which additional questions to ask :) -eric On Wed, May 13, 2015 at 2:45 PM Michelle McDaniel <michelm at microsoft.com<mailto:michelm at microsoft.com>> wrote: I work on the LLILC team, and we are trying to send debug line info through to the CoreCLR EE without using an EventListener because we need to send extra info (more than just available in DebugLoc) like if it’s a call instruction, a call site, etc. We thought extending AsmPrinterHandler would be useful since it seems to have information about debug locations, label offsets, and instruction specific information. From:...

I''ve noticed that the update method of every Draggable is called for each mousemove event while nothing is dragging. I''m wondering what the reasoning behind this is (vs. attaching the mousemove handler after a mousedown event). Does it have a noticeable performance impact when there are lots of draggables (say 400)? Disclaimer: I''m really new to JavaScript and may have

Hey everyone, I'm looking into extending AsmPrinterHandler out of tree, to communicate information back to the CoreCLR EE, but all of the headers are in the lib directory. Is there any way to extend it out of tree, or is that not supported? The reason I'd like to do this out of tree is because we want to include clr headers as well, and we don't want to introduce that into llvm

...namespace)::GDBJITRegistrationListener::notifyObjectLoaded(unsigned long, >> llvm::object::ObjectFile const&, llvm::RuntimeDyld::LoadedObjectInfo >> const&)::__PRETTY_FUNCTION__> "virtual void >> {anonymous}::GDBJITRegistrationListener::notifyObjectLoaded(llvm::JITEventListener::ObjectKey, >> const llvm::object::ObjectFile&, const >> llvm::RuntimeDyld::LoadedObjectInfo&)") >> >> at assert.c:101 >> >> #4 0x00007ffff01ed4d3 in (anonymous >> namespace)::GDBJITRegistrationListener::notifyObjectLoaded >> (this=0...

Hi folks, Rather by accident than on purpose I looked at the release notes and found the following: http://releases.llvm.org/8.0.0/docs/ReleaseNotes.html#changes-to-the-jit-apis TL;DR: Orc v1 is deprecated and will be removed in the next release. I have several questions in this regard: 1. Is there a migration guide I can use to update my code to the new version? 2. Is there any development

Quick question.. I often crash my Safari when using ''Enter'' on InPlaceEditor''s for submitting. Works fine on firefox(win & Mac) - no javascript errors. Anyone else seen this behavior? (Maybe it is just my alterings of InPlaceEditor :-) Best Regards Michael Krog

I have a page where I am replacing a table element after the page has loaded. I get an error (on ie 6) when prototype.js calls cumulativeOffset. For the new table element, requesting the element.offsetParent property results in an "unspecified error" that brings my whole page to a crashing halt. Does anyone have any ideas or suggestions? Thanks, Cathy -------------- next part