view src/main/gov/nasa/jpf/vm/ThreadInfoSet.java @ 2:b920e6b1be83

second part of the jpf-statechart motivated event interface overhaul, providing dynamic (context specific) expansion of EventTrees from within EventChoiceGenerators. This adds a EventContext mechanism that can replace events on-the-fly during advance() (e.g. expand wildcard patterns) this also included the refined 'vm.extend.transitions' property, which is now a list of TypeSpecs (glob notation plus bounds) for CG types that should be subject to transition extension. We also support CheckExtendTransition attrs for CGs, which can be used to dynamically mark CGs. Note that each matching CG is still tested for non-rescheduling single choices small Type/FeatureSpec extension to make it applicable to java.lang.Class instances. There is no reason why we can't make use of this for native types
author Peter Mehlitz <Peter.C.Mehlitz@nasa.gov>
date Sat, 24 Jan 2015 18:19:08 -0800
parents 61d41facf527
children
line wrap: on
line source

/*
 * Copyright (C) 2014, United States Government, as represented by the
 * Administrator of the National Aeronautics and Space Administration.
 * All rights reserved.
 *
 * The Java Pathfinder core (jpf-core) platform is licensed under the
 * Apache License, Version 2.0 (the "License"); you may not use this file except
 * in compliance with the License. You may obtain a copy of the License at
 * 
 *        http://www.apache.org/licenses/LICENSE-2.0. 
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and 
 * limitations under the License.
 */

package gov.nasa.jpf.vm;

/**
 * interface to abstract the referencing set of threadinfos per object/class
 * Used to detect shared objects/classes 
 * Instances are created through a configured factory (SharedObjectPolicy)
 * 
 * We abstract the container so that the way we identify threads is not exposed
 * to the client, and implementations can use either ThreadInfo references or
 * global ids.
 */
public interface ThreadInfoSet extends Cloneable {

  /**
   * @return true if the thread wasn't in the set yet and was added
   */
  ThreadInfoSet add (ThreadInfo ti);
  
  ThreadInfoSet remove (ThreadInfo ti);
  
  boolean contains (ThreadInfo ti);
  
  boolean isShared (ThreadInfo ti, ElementInfo ei);
  
  
  boolean hasMultipleLiveThreads ();
  boolean hasMultipleRunnableThreads ();
  
  Memento<ThreadInfoSet> getMemento();
  
  int size();
}