From: Laia M. <man...@gm...> - 2007-06-15 22:03:19
|
Thank you all for your answers. Here is a summary of my thoughts: 1) Yes, what I was after was the binary tree search and management functions (tsearch, tfind, tdestroy, and so on). Under glibc, these are defined in the header search.h. To make things a little more confusing, it turns out that MinGW already has a search.h, but it does not contain the same stuff as the glibc one. 2) When it comes to what should be the appropriate course of action, I really have no clue. As a Linux person that needs to maintain some ports of my Linux programs for Windows, what I am most concerned is consistency between libraries (having a straighforward port of the search part of glibc would be nice) and function names (and here I am not very concerned about adherence to standards). I realize, though, that these are MY needs, which may not be consistent with the needs of most other people. 3) I have found a solution to MY problem. It turns out that Cygwin does have a port of the binary tree search functions, which is totally consistent with glibc. Using Cygwin, thus, I can just take my code and compile it for Windows without a change :) I hope this thread will be useful for other people in the future, and I will definitely keep an eye for further developments in MinGW. Laia |