I found some data structure related units in LCL (AvgLvlTree, DynamicArray, DynHashArray, DynQueue, etc.). To be consistent (LCL: visual components, FCL: non-visual), wouldn't it be better to move them to FCL?
Mailing lists / fpc-pascal / 2009-03
Should data structures part in LCL be moved to FCL?
6 messages · 3 people · –
- Lleledumbo 4
- FFrancisco Reyes 1
- MMarco van de Voort 1
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
In our previous episode, leledumbo said:
I found some data structure related units in LCL (AvgLvlTree, DynamicArray, DynHashArray, DynQueue, etc.). To be consistent (LCL: visual components, FCL: non-visual), wouldn't it be better to move them to FCL?
What is there that is not already in FPC ? Are these not simply leftovers of older times when Lazarus still had to compile with 1.0.x?
AvgLvlTree, DynamicArray,
DynHashArray, DynQueue
Marco van de Voort wrote 5 lines
Oh, I didn't know about it. The first time I use Lazarus FPC was already 2.0.4. Well, some of them has FCL counterparts and some don't: AvgLvlTree = AVL_Tree
DynamicArray = ??? (object wrapper of normal dynamic array?) DynQueue = TObjectQueue or TQueue
DynHashArray = ???
LazLinkedList = ???
I miss these data structures in FCL: linked list, graph, and tree (not AVL one).
Found a new one on the net: http://redbeesoft.com/
Good news:
- FPC compatible
- Both open source and proprietary editions available
leledumbo wroteFound a new one on the net: http://redbeesoft.com/
Looks interesting. They specifically mention it is FPC compatible and cross platform.
Tried the examples with -glh, there seems to be a LOT of mem leaks. I'll try to report (if possible).
