search for: imper

I''m working on writing features for a wizard. The wizard collects information from a number of different forms, and you can navigate through it in a number of ways. Anyhow one of these forms is a customer form collecting name, and email. In the context of the wizard I feel that the following scenarios Scenario: Given I step to customer And I fill in my customer details

This adds imperative list manipulation functions inspired by Perl. The functions are passed list refs which get updated in place. This allows us to replace some awkward pure functional code like: let xs = ys in let xs = if foo then xs @ zs else xs in with: let xs = ref ys in if foo then append xs zs; -...

On Thursday 07 July 2016 17:30:03 Richard W.M. Jones wrote: > This adds imperative list manipulation functions inspired by Perl. > The functions are passed list refs which get updated in place. > > This allows us to replace some awkward pure functional code like: > > let xs = ys in > let xs = if foo then xs @ zs else xs in > > with: > >...

On Thu, Jul 07, 2016 at 06:08:43PM +0100, Richard W.M. Jones wrote: > On Thu, Jul 07, 2016 at 07:00:46PM +0200, Pino Toscano wrote: > > On Thursday 07 July 2016 17:30:03 Richard W.M. Jones wrote: > > > This adds imperative list manipulation functions inspired by Perl. > > > The functions are passed list refs which get updated in place. > > > > > > This allows us to replace some awkward pure functional code like: > > > > > > let xs = ys in > > > let xs =...

...g good stories and shows gives two examples.. the way not to do it and the way to do it. You can also see the video of the presentation at confreaks (http://goruco2008.confreaks.com/01_helmkamp.html -- jump to 13:24 to see where he talks about the two examples.) The first is what he calls an imperative example: ---------------------------------------------------------------------------- Scenario: Reject duplicate names Given I am on the Developers page When I click the Add Developer button Then I should see the Add Developer page When I enter the first name Zed And I enter the last name...

On Thu, Jul 07, 2016 at 07:00:46PM +0200, Pino Toscano wrote: > On Thursday 07 July 2016 17:30:03 Richard W.M. Jones wrote: > > This adds imperative list manipulation functions inspired by Perl. > > The functions are passed list refs which get updated in place. > > > > This allows us to replace some awkward pure functional code like: > > > > let xs = ys in > > let xs = if foo then xs @ zs else xs i...

...16 at 09:10:51AM +0100, Richard W.M. Jones wrote: > On Thu, Jul 07, 2016 at 06:08:43PM +0100, Richard W.M. Jones wrote: > > On Thu, Jul 07, 2016 at 07:00:46PM +0200, Pino Toscano wrote: > > > On Thursday 07 July 2016 17:30:03 Richard W.M. Jones wrote: > > > > This adds imperative list manipulation functions inspired by Perl. > > > > The functions are passed list refs which get updated in place. > > > > > > > > This allows us to replace some awkward pure functional code like: > > > > > > > > let xs = ys in...

Dear R community, I have one function, it works for small data set, but does not work on large data set, can anyone help me with this? > #creat new variable by dividing each aa dimer by total_length. > imper<-function(x, file) { + round(x/file$length, 5) + } > dim(test) [1] 999 2402 > test[varname[2:2401]]<- apply(as.matrix(test[varname[2:2401]]), 2, function (x) imper(x, test)) > dim(dimer.nn) [1] 999554 2402 > dimer.nn[varname[2:2401]]...

The coding guidelines say: > Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case letter (e.g. openFile() or isFoo()). This means that functions that just compute or access a value (no side-effects) should be named e.g. `getParent()`, rather than `parent()` as they are in e.g. the standard library. This is not a...

Forgive the long post, just looking for input/advice/alternate opinions.. Like many I think that going through the exercise of framing user requests in Cucumber terms(Features, Scenarios..) really helps facilitate necessary conversations and avoid time wasted implementing the wrong thing(e.g. as a requirement/specification tool). However, I''m a bit confused when it comes to

No functional change in this commit. --- builder/downloader.ml | 40 +++++++++++++++++++--------------------- v2v/copy_to_local.ml | 26 +++++++++++--------------- v2v/vCenter.ml | 34 ++++++++++++++++------------------ 3 files changed, 46 insertions(+), 54 deletions(-) diff --git a/builder/downloader.ml b/builder/downloader.ml index 3c9ba18..2a3f76f 100644 --- a/builder/downloader.ml

...nal, though. (Witness the effort to remove systemd > requirements from containers.) An engineer is expected to understand the > component parts rationally to arrive at some sort of professional > conclusion that something is likely to work properly. This is not helped > by a switch from imperative and deterministic to declarative and > dynamic, which underlies many of the changes we've had to deal with in > the past decade. There is a time and place for the latter, and it's good > to have options available... but there are many times and places > (especially in the E...

> On 24 May 2018, at 20:19, Sam McCall via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The coding guidelines say: > > Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case letter (e.g. openFile() or isFoo()). > > This means that functions that just compute or access a value (no side-effects) should be named e.g. `getParent()`, rather than `parent()` as they are in e.g. the standard library. >...

...hael Berris via llvm-dev wrote: > >> On 24 May 2018, at 20:19, Sam McCall via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> The coding guidelines say: >>> Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case letter (e.g. openFile() or isFoo()). >> >> This means that functions that just compute or access a value (no side-effects) should be named e.g. `getParent()`, rather than `parent()` as they are in e.g. the standard library...

...at should I do? The libcall FROUND_F64_F32 is there, but it seems that it cannot be reached without hacking. What should I do to support this? Am I missing something? Thanks, -- Bruno Cardoso Lopes http://www.brunocardoso.cc "When faced with untenable alternatives, you should consider your imperative."

...for identical thunks to have > identical names — just like we do for builtins and other stuff, to avoid > having differences between clang and GCC which just end up seeming > capricious and being hard to work around. Having matching command line > options would be a bonus, but isn't imperative. > After talking to several others (to make sure we don't have to do this whole thing yet again) we'll change the external thunk names to match what GCC is using. Hopefully this doesn't come back to bite us. =] We'll also make sure those patches get backported too so that...

Hi all, I am trying to compile a high-level imperative OOP-like language to the LLVM IR. Do we have any "generic" way of translating a non-SSA form to the LLVM IR's SSA? There are lots of LLVM front-ends now. Do they do such translation individually? or there is some common non-SSA IR that we can translate to, and can be converted to...

So the right way to do it -- it seemed to work when I tried it, at least -- is metaflac --remove-all --dont-use-padding filename.flac ? I guess that these features make it more imperative than ever to watch the timestamps and not to validate a FLAC with an MD5 that is older than the FLAC is.

...'Security'').tail{ |log| p log } #<struct Struct::EventLogStruct record_number=15399, time_generated=Fri May 19 19:54:25 MDT 2006, time_written=Fri May 1 9 19:54:25 MDT 2006, event_id=680, event_type="audit failure", category=9, source="Security", computer="IMPERATOR", user ="SYSTEM", description="Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0\r\n\r\nLogon account: Daniel\r\n\r\nSou rce Workstation: IMPERATOR\r\n\r\nError Code: 0xC000006A\r\n\r\n"> #<struct Struct::EventLogStruct record_number=15064, time_generated...

Basic support for Small bss and data. The rest is implemented with target specific logic and will be commited as soon as it's ok to commit this patch. -- Bruno Cardoso Lopes http://www.brunocardoso.cc "When faced with untenable alternatives, you should consider your imperative." -------------- next part -------------- A non-text attachment was scrubbed... Name: smallsections.patch Type: application/octet-stream Size: 2454 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080721/8c3f9704/attachment.obj>