Linked lists are suitable as a flexible and modular way to implement simple and powerful code with ease.
This library will allow you to leverage the simplicity, power and flexibility of linked lists.
A linked list is a data structure that represents a sequence of nodes (Elements). This library implements a so called "double linked list", which simply means that the list gives each Element pointers to both the next Element and the previous Element. Unlike an array, a linked list does not provide constant time access to a particular “index” within the list. This means that if you’d like to find the K-th element in the list, you will need to iterate through K elements. The benefit of a linked list is that you can add and remove Elements from the list during runtime so this means you can very easily extend your code with new FB's without extra coding since itteration with Elements is always done in FOR and/or WHILE loops. This means that by design your code doesn't need to be rewritten as demonstrated in the example below 👇
Insert the Library Reference in your program's library manager.
Declare a new FB named FB_ExtendedElement
We need to either 1) extend at least one FB_Element since it has been decorated as ABSTRACT.
or 2) implement interface: LinkedList.IElement.
Any new FB that will be a part of the List should preferably use method 2) implement interface. This way FB_ExtendElement will act as a baseclass for your Element without being itself of type "FB_ELEMENT". (EXTENDING means "IS OF", while IMPLEMENTS means "MAKES USE OF"). If you use encapsulation and composition it will provide you with more freedom and flexibility but as a penalty it will demand more programming since all methods and properties need to be implemented.
FUNCTION_BLOCKFB_ExtendedElementEXTENDSElementVAR_itfPrev:IElement;_itfNext:IElement;_itfList:IList;_uiCount:UINT:=0;END_VAR// Body(*Empty,weusecomposition*)METHODIsListMemberOf:BOOL// xMemberVAR_INPUTitfList:IList;END_VAR// BodyIsListMemberOf:=(itfList=THIS^._itfList);METHODRemoveElem:IElement// BodyIF_itfList=0THEN// This element is not a member of a listRemoveElem:=0;RETURN;END_IFRemoveElem:=_itfList.RemoveElem(THIS^);PROPERTYIsLinkedElem:BOOL// Get GetIsLinkedElem:=(_itfList<>0);// Set is not implementedPROPERTYList:IList// GetList:=_itfList;// Set_itfList:=List;PROPERTYNextElem:IElement// GetList:=_itfList;// Set_itfList:=List;PROPERTYPrevElem:IElement// GetPrevElem:=_itfPrev;// Set_itfPrev:=PrevElem;METHODReturnInstance:POINTERTOFB_ExtendedElement// BodyReturnInstance:=THIS;METHODCount:UINT;// Body_uiCount:=uiCount+1;PROPERTYGetCount:UINT// GetGetCount:=_uiCount;
Some usage general information and rules about Elements
Always obtain access to elements via the functionblock instance of List.
Element require more burnerplate-code when compared to array's but are also more flexible.
Array's are always packed together in memory, while Elements usually are scattered throughout the memory. This is the nature of elements.
Use __QueryInterface(,) in order to see whether a epecific interface is implemented
By downloading and using our software you abide by the MIT License