similar to: questions about extend

Is it possible to call the super class''s version of a function from a subclass? SuperClass = Class.create(); SuperClass.prototype = { initialize: function(){ this.varA = ''''; this.varB = ''''; } } SubClass = Class.create(); SubClass.prototype = (new SuperClass()).extend({ initialize: function(somevar) { this.somevar = somevar; }

I''ve got a question about how variables are made available to templates. We have a test that looks something like this: def test_variable_assigned xhr :get, :do_stuff, :id => 1 assert_not_nil assigns(:thing) end And our app code looks like this: class SuperClass < ActionController def do_stuff @parent_model = ParentModel.find(params[:id]) render :template

Can someone explain what the problem is when I use the generating function? And how to get debug() to stop in the Superclass initialize method? ---- source ----- setClass("Superclass", representation(id = "character"), contains = "VIRTUAL") setMethod("initialize", signature(.Object = "Superclass"),

Dear all, apart from my previous question, I would also like to ask one more question here, which is as follows: #let me 1st define a class and a subclass setClass("a", representation=list(x="numeric", y="numeric"), prototype=list(x=rep(1,3),y=rep(2,3))) setClass("b", representation=list(x1="character", y1="character"),

Dear list, I have a reference class which should act as a "generic" superclass for other classes. I've read the respective section at ?setRefClass and put the name of the superclass to the 'contains' argument of an example subclass (see class defs below). Classnames are set in a way that shouldn't result in collation issues (virtual def sourced before superclass def

On 01/31/2018 02:37 AM, David Chisnall via llvm-dev wrote: > On 30 Jan 2018, at 19:56, Alex Bradbury via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> Is this bad style? It seems the current codebase is inconsistent on >> this point. The upside of such duplication is that it reduces the need >> to cross-reference to other files when using a dumb editor. > I

On 30 Jan 2018, at 19:56, Alex Bradbury via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Is this bad style? It seems the current codebase is inconsistent on > this point. The upside of such duplication is that it reduces the need > to cross-reference to other files when using a dumb editor. I generally use the rendered docs on the LLVM web site when using a dumb editor, so

Hi, I''m teaching myself to use wxRuby and DialogBlocks to create a front end for a Ruby program I wrote. And I''m hopelessly stuck! In DialogBlocks (or indeed wxFormBuilder, which gives me the same problem) I can create a widget, give that widget a new id and class name (in the example I created below, text_box1 and CaseChangeTextCtrl1, respectively), and then add a module which

Try putting !!! (three exclamation symbols) in front of which(...)==.... The non-standard evaluation in the tidyverse can cause confusion. Bill Dunlap TIBCO Software wdunlap tibco.com On Thu, Aug 24, 2017 at 4:32 AM, Eugeny Melamud < Eugeny.Melamud at lanit-tercom.com> wrote: > Hi all! > > The following code (executed in console)... > somevar <- data.frame(v1 = 1:5,

Hi all! The following code (executed in console)... somevar <- data.frame(v1 = 1:5, somestring = 6:10, v3 = 11:15, v4 = 16:20); somevar %>% gather(key = var, value = val, which(names(somevar) == "somestring"):length(somevar)) %>% head(2); throws... Error in which(names(somevar) == "somestring") : could not find function "which" if I change

Ah, I've got it now. >From `?base:bindenv` comes > " The namespace environments of packages with namespaces are locked when loaded." A locked environment > " prevents adding or removing variable bindings from the environment. Changing the value of a variable is still possible unless the binding has been locked" A bit of experimentation shows that as well as

I don't see what's missing in my statements to add rows to a data frame and someone else will probably see what needs to be added to the statements. The data frame has this structure (without any data): $ PHYLUM : chr $ SUBPHYLUM : chr $ SUPERCLASS : chr $ CLASS : chr $ SUBCLASS : chr $ INFRACLASS : chr $ SUPERORDER : chr $ ORDER : chr $ SUBORDER :

On 1 February 2018 at 03:44, Philip Reames <listmail at philipreames.com> wrote: > > > On 01/31/2018 02:37 AM, David Chisnall via llvm-dev wrote: >> >> On 30 Jan 2018, at 19:56, Alex Bradbury via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> >>> Is this bad style? It seems the current codebase is inconsistent on >>> this

I''m getting some weirdness trying to use a select widget to choose the type from a collection of three objects sharing a database table via single-table inheritance (STI). I''d be grateful for any advice on whether it''s a bug or a feature, if a feature why and how I can more easily do what I''m trying to do. So I have the usual STI setup, with a

libswfdec/swfdec_as_array.c | 2 - libswfdec/swfdec_as_context.c | 1 libswfdec/swfdec_as_function.c | 13 ++---- libswfdec/swfdec_as_interpret.c | 5 +- libswfdec/swfdec_as_native_function.c | 1 libswfdec/swfdec_as_number.c | 2 - libswfdec/swfdec_as_object.c | 20 +++++++--- libswfdec/swfdec_as_object.h | 6 ++-

On Tue, 12 Jun 2007, Fernando Magno Quintao Pereira wrote: > Imagine that I have a virtual v stored in register AL, and I am about > to cross a function call, that effectively overwrites AL. Well, I have, > say, register ESI free, but as it happens, ESI is bigger than AL. It > should be technically possible to move the contents of AL into ESI, to > avoid spilling 'v',

I have to confess that I did not know about facets before reading Ashley Moran''s post: http://aviewfromafar.net/2007/10/21/quick-and-dirty-facets-in-rspec-trunk Not knowing about the facets solution, I made a couple of feature requests for nested describes: http://rubyforge.org/tracker/index.php?func=detail&aid=14980&group_id=797&atid=3152

context probably won't give you any insight into what it actually means, namely that because of X limitations, Wine can't actually change the screen depth and lies to the application instead. Usually this is fine; in fact I've never heard of it causing a problem. We really have no business printing that scary useless thing IMO. It should never be necessary to document these things.

Hi, the attached patch splits the loop unroll pass into a LoopUnroll superclass that implements the unrolling mechanism, and a SimpleLoopUnroll subclass implementing the current policy. This split is modeled after the split between Inliner and SimpleInliner. The superclass currently still finds out the TripCount and TripMultiple, and passes those, together with the Loop in question, to a policy

Does this depend on vreg subreg support? It sounds as if it could be vaguely related, but I'm not sure it's necessary. -- Chris On Jun 14, 2007, at 12:27 PM, Evan Cheng wrote: > The short answer is this is not currently done. LLVM register > allocator does not currently use a move to a different register class > in lieu of spills. This is definitely something we should do in