circular-reference

i'm having a problem very similar to this SO question , but my attempts to apply these previous answers isn't going thru and it was suggested i start it as a new question: in the code below i define a couple of getChoices() functions that i thought would defer the circular refs, but no!? what's wrong here, please? # ns.content/ns/content/foo.py from zope import schema from plone.directives import form from z3c.relationfield.schema import Relation, RelationChoice from plone.formwidget.contenttree import ObjPathSourceBinder class IFoo(form.Schema): def getBarChoices(): # avoiding circular refs..

I am trying to solve this, there are similar questions but none are fit for my issue I have .h file with a a @protocol. The @interface needs to have that @protocol definition. But the @protocol needs the class's definition. Circular. How can this be solved? @protocol myProtocol -(void)setupMyClass:(MyClass *)class; @end @inteface MyClass @property (weak, nonatomic) id<myProtocol> delegate; @end If I use different files each needs to import the other, so that doesn't solve it Forward-declare the class: @class MyClass; // Forward declaration @protocol MyProtocol ... @end @interface MyClass ...

See this demo (dependent on selectionchange event which works in Chrome only at this moment): http://jsfiddle.net/fyG3H/ Select some lorem ipsum text and then focus the text input. In the console log you will see that there is a DOMSelection object. It has an anchorNode value of HTMLBodyElement while it should have one of Text . I didn't know why this was happening until I tried stringfying the selection object: http://jsfiddle.net/fyG3H/1/ This gives the following error: Uncaught TypeError: Converting circular structure to JSON Do you know how I can prevent this circular reference caused by

I'm using Spring(xml+annotations), Hibernate(annotations) in this web service project. The database relationship diagram, models, expected and actual output are given below, Database Table relationship Customer.java @Entity @Table(name="customer") public class Customer implements Serializable{ private static final long serialVersionUID = 1L; @Id @GeneratedValue(strategy=GenerationType.IDENTITY) @Column(name="customer_id", unique=true, nullable =false) long customerId; @Column(name="name") String name; @Column(name="secondary_name") String secondaryName; @Column(name="date") Date date; @Column

I have three projects in my .net solution. The main project and two class library projects. I have found out that I need to cross reference the class library projects. Can I do that? Is it safe or there are some considerations? The IDE won't let you when the projects are in one solution. There are subtle ways to confuzzle it. But then the solution cannot be built from scratch (i.e. Build + Rebuild) since the assembly reference isn't available yet. Refactor this, you probably want a 3rd assembly that both can reference. Circular references are possible (via the command-line and some tricks; not

Here's the thing: I'm using the CommonJS way of making my mobile (iPhone/Android) application modular. No surprise there. But there's one thing that I just can't get my head around. CommonJS lets me create STATIC private variables, which lets me create singletons at ease. This, I think at least, is because the contents of a file that gets require() d is read only once and then the exports object (which is initialized only once) is returned every time. But when I create a circular reference as seen below, the code inside the included module is executed every time. Wait... Funny thing is, while