search for: reusability

On Tue, Dec 13, 2016 at 10:37 AM, Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > ----- Original Message ----- > > From: "Rafael Avila de Espindola via llvm-dev" <llvm-dev at lists.llvm.org> > > To: "Mehdi Amini" <mehdi.amini at apple.com> > > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > > Sent:

Hi All, Is that possible to make tinc as a reusable lib to make it more widely used in IOT world? and make release an official app for IOS、Android and windows possible? Tks.

Is there a development guide for best practices when making reusable components? For example, none of the login generators fit my requirements, and I want to write my own. But after I''m done, I''ll want to share it with multiple applications. Is there documentation for the right way to go about doing this? -- - Adam ** Expert Technical Project and Business Management ****

On Sun, Oct 09, 2016 at 10:18:46PM +0800, Cong Monkey wrote: > Is that possible to make tinc as a reusable lib to make it more widely > used in IOT world? Yes, have a look at MeshLink: https://github.com/meshlink/meshlink > and make release an official app for IOS、Android and windows possible? I would love to, but I have no time myself to do that. There is an unofficial Android app:

Hello, I''m using the scheduler to create several reusable workers of the same type, .e.g., RSSWorker, so I can avoid the overhead of initializing new processes (as suggested by Ezra to my previous question). Creating new workers through the external yaml seems pretty straightforward, but my question is is there a way to call these workers without using the job key? Currently, to use

----- Original Message ----- > From: "Rafael Avila de Espindola via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Mehdi Amini" <mehdi.amini at apple.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Tuesday, December 13, 2016 12:10:08 PM > Subject: Re: [llvm-dev] LLD status update and performance chart > > Mehdi Amini

Hi, Anyone know a way to traverse/query the DOM in a response? I''m trying to write reusable story step implementations and as much as possible want to work with the actual response from a previous GET. As an example, I often have buttons that POST/PUT a hidden value. My goal is a reusable step implementation that takes the button label and works the existing response DOM to make an

----- Original Message ----- > From: "Rui Ueyama" <ruiu at google.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "Rafael Avila de Espindola" <rafael.espindola at gmail.com>, > "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Tuesday, December 13, 2016 12:56:41 PM > Subject: Re: [llvm-dev] LLD status update and

Hi there, I would like to use puppet to configure two networks and one of the first things I''ve tried to do is to describe ntp configuration. Each network has a ntp server that acts as a proxy for internal nodes, so those internal nodes share the same configuration except for the server they use to get the time. Attempting to describe this I''ve thought of several approaches,

Hi All, I'd like to know what is the best way to organize R code in multiple modules= and files. The R code we are writing is too much for a single file. Besides= , there are a lot of reusable functions we'd like to factor out. But writing= a package for that is quite an over-kill and might be too inflexible. So what is the best way to organize R code into multiple files and reusable=

> However, it is not very beginner friendly. There's two thing lacking: > editting the configuration files from the app, and being able to run the > app without root privileges. For the latter, the app and maybe tinc > itself might need to be changed to use the VPN API to create a tun > device and to pass it to the tinc daemon. I don't even know if there is > something

On Sun, Oct 09, 2016 at 10:40:12PM +0800, Cong Monkey wrote: > If release as libtinc possible, will that possible that you relicence > TINC as LGPL to make commercial use possible? Both tinc and MeshLink are licensed under the GPL and will stay that way. However, if you want to use MeshLink in a commercial project, you can buy a commercial license. -- Met vriendelijke groet / with kind

Just wait tinc be more lib style for some future days:) 2016-10-09 22:45 GMT+08:00 Guus Sliepen <guus at tinc-vpn.org>: > On Sun, Oct 09, 2016 at 10:40:12PM +0800, Cong Monkey wrote: > >> If release as libtinc possible, will that possible that you relicence >> TINC as LGPL to make commercial use possible? > > Both tinc and MeshLink are licensed under the GPL and will

I was planning to make an iOS port, but GPL means we can't make an App Store version. Also, the way Network Extension work means only tun mode is available. Sent from my iPhone > On 9 Oct 2016, at 23:55, Cong Monkey <congzhangzh at gmail.com> wrote: > > Just wait tinc be more lib style for some future days:) > > 2016-10-09 22:45 GMT+08:00 Guus Sliepen <guus at

> I was planning to make an iOS port, but GPL means we can't make an App Store version. Also, the way Network Extension work means only tun mode is available. I think GPL just forbidden link from(which need more link exception statement be added) but not link to Ne extension work with link from style? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Network extension apps are just like ordinary apps, only they can utilize the utun interface and create VPN entries. So I think, yes, tinc need to be linked from such apps. Sent from my iPhone > On Oct 10, 28 Heisei, at 9:48, Cong Monkey <congzhangzh at gmail.com> wrote: > > > > I was planning to make an iOS port, but GPL means we can't make an App Store version. Also,

2016-10-11 3:52 GMT+08:00 Mr.X <mrx at hcc.im>: > Network extension apps are just like ordinary apps, only they can utilize > the utun interface and create VPN entries. So I think, yes, tinc need to be > linked from such apps. link to and link from is mark as the main application's view, so, for NE extension it's link to libtinc( if there is a libtinc lib), that's

...e components approach. But clang is not the fastest C/C++ compiler available, and LLVM is not the fastest compiler framework either! So as a project, it seems to me that LLVM has not put the tradeoff on the speed/efficiency historically when it was to the detriment of layering/component/modularity/reusability/… Writing the fastest linker possible is nice goal, I regret that a LLVM subproject is putting this goal above layering/component/modularity/reusability/… though. — Mehdi -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-de...

Maybe I''m slow, but I just noticed that the following code.. When ''I login'' When ''I do something else'' ...will output as... When ''I login'' And ''I do something else'' The same is true for two ''Then'' steps That is really cool! Reusable steps and coherent English output. - Andy -- View this

...h use could be a potential way forward. I don't know enough about LLD or objdump to have any concrete opinion, but I have a feeling that objdump is a much bigger program than it should be. People usually say it's because the code is not really reusable. That may be true, but if we can find reusability on small tools and LLD, that'd at least reduce code a bit. Given that LLD already depends on Clang and LLVM, there's no bad side of the increased dependency. (is there?). But I would personally follow a more pragmatic approach. It should be ok for LLD to have its own infrastructure, as lon...