org.jruby.RubyClass.getGeneration()方法的使用及代码示例

x33g5p2x  于2022-01-29 转载在 其他  
字(4.3k)|赞(0)|评价(0)|浏览(89)

本文整理了Java中org.jruby.RubyClass.getGeneration方法的一些代码示例,展示了RubyClass.getGeneration的具体用法。这些代码示例主要来源于Github/Stackoverflow/Maven等平台,是从一些精选项目中提取出来的代码,具有较强的参考意义,能在一定程度帮忙到你。RubyClass.getGeneration方法的具体详情如下:
包路径:org.jruby.RubyClass
类名称:RubyClass
方法名:getGeneration

RubyClass.getGeneration介绍

暂无

代码示例

代码示例来源:origin: org.jruby/jruby-complete

public final boolean typeOk(RubyClass incomingType) {
  return token == incomingType.getGeneration();
}

代码示例来源:origin: org.kill-bill.billing/killbill-osgi-bundles-jruby

public static final boolean typeOk(CacheEntry entry, RubyClass incomingType) {
    return entry.token == incomingType.getGeneration();
  }
}

代码示例来源:origin: com.ning.billing/killbill-osgi-bundles-jruby

public static final boolean typeOk(CacheEntry entry, RubyClass incomingType) {
    return entry.token == incomingType.getGeneration();
  }
}

代码示例来源:origin: org.jruby/jruby-core

public final boolean typeOk(RubyClass incomingType) {
  return token == incomingType.getGeneration();
}

代码示例来源:origin: org.kill-bill.billing/killbill-osgi-bundles-jruby

public static boolean testGeneration(int token, IRubyObject self) {
  return token == ((RubyBasicObject)self).getMetaClass().getGeneration();
}

代码示例来源:origin: com.ning.billing/killbill-osgi-bundles-jruby

public static boolean testGeneration(int token, IRubyObject self) {
  return token == ((RubyBasicObject)self).getMetaClass().getGeneration();
}

代码示例来源:origin: org.kill-bill.billing/killbill-osgi-bundles-jruby

private boolean versionMatches(ThreadContext context, DynamicScope currDynScope, IRubyObject self, Object[] temp) {
  IRubyObject receiver = (IRubyObject) candidateObj.retrieve(context, self, currDynScope, temp);
  // if (module.getGeneration() != expectedVersion) ... replace this instr with a direct jump
  //
  // SSS FIXME: This is not always correct.  Implementation class is not always receiver.getMetaClass()
  // as we know from how we add instance-methods.  We add it to rubyClass value on the stack.  So, how
  // do we handle this sticky situation?
  return (receiver.getMetaClass().getGeneration() == expectedVersion);
}

代码示例来源:origin: com.ning.billing/killbill-osgi-bundles-jruby

private boolean versionMatches(ThreadContext context, DynamicScope currDynScope, IRubyObject self, Object[] temp) {
  IRubyObject receiver = (IRubyObject) candidateObj.retrieve(context, self, currDynScope, temp);
  // if (module.getGeneration() != expectedVersion) ... replace this instr with a direct jump
  //
  // SSS FIXME: This is not always correct.  Implementation class is not always receiver.getMetaClass()
  // as we know from how we add instance-methods.  We add it to rubyClass value on the stack.  So, how
  // do we handle this sticky situation?
  return (receiver.getMetaClass().getGeneration() == expectedVersion);
}

代码示例来源:origin: com.ning.billing/killbill-osgi-bundles-jruby

public static boolean isGenerationEqual(IRubyObject object, int generation) {
  RubyClass metaClass;
  if (object instanceof RubyBasicObject) {
    metaClass = ((RubyBasicObject)object).getMetaClass();
  } else {
    metaClass = object.getMetaClass();
  }
  return metaClass.getGeneration() == generation;
}

代码示例来源:origin: org.kill-bill.billing/killbill-osgi-bundles-jruby

public static boolean isGenerationEqual(IRubyObject object, int generation) {
  RubyClass metaClass;
  if (object instanceof RubyBasicObject) {
    metaClass = ((RubyBasicObject)object).getMetaClass();
  } else {
    metaClass = object.getMetaClass();
  }
  return metaClass.getGeneration() == generation;
}

代码示例来源:origin: org.jruby/jruby-complete

private boolean versionMatches(ThreadContext context, StaticScope currScope, DynamicScope currDynScope, IRubyObject self, Object[] temp) {
  IRubyObject receiver = (IRubyObject) getCandidateObject().retrieve(context, self, currScope, currDynScope, temp);
  // if (module.getGeneration() != expectedVersion) ... replace this instr with a direct jump
  //
  // SSS FIXME: This is not always correct.  Implementation class is not always receiver.getMetaClass()
  // as we know from how we add instance-methods.  We add it to rubyClass value on the stack.  So, how
  // do we handle this sticky situation?
  return (receiver.getMetaClass().getGeneration() == getExpectedVersion());
}

代码示例来源:origin: org.jruby/jruby-core

private boolean versionMatches(ThreadContext context, StaticScope currScope, DynamicScope currDynScope, IRubyObject self, Object[] temp) {
  IRubyObject receiver = (IRubyObject) getCandidateObject().retrieve(context, self, currScope, currDynScope, temp);
  // if (module.getGeneration() != expectedVersion) ... replace this instr with a direct jump
  //
  // SSS FIXME: This is not always correct.  Implementation class is not always receiver.getMetaClass()
  // as we know from how we add instance-methods.  We add it to rubyClass value on the stack.  So, how
  // do we handle this sticky situation?
  return (receiver.getMetaClass().getGeneration() == getExpectedVersion());
}

相关文章

微信公众号

最新文章

更多

RubyClass类方法