-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let us know if you're using qlibc! Also don't forget to give a Star to this project~ #4
Comments
Hi. I'm using qLibc because of qhashtbl_t is been very useful for me. |
Sorry, I'm little fuzzy on what you said. PS: if this is more of question or bug report, could you please open a separate issue for better handling? Thanks |
Thank you for your quick reply! That is exactly what I'd asked.
I fill "tbl_tipo" with some values and finally I put "tbl_tipo" in "tbl":
I'm going to test your solution. In case of a problem I'll write a bug report. |
Well. I suppose I don't have to pay attention to those errors, because I need the parent hash (and his content) during the all runtime and Valgrind complains about them when the program ends. |
I see. Yes tbl->free() will only free the pointer to tbl_tipo. In order to make the valgrind happy, LOOP subtbl := tbl->next() |
Hello, how can i send a POST using qhttp_client? Thanks in advance for your help Luis JImenez |
Please cut an issue ticket for any questions and bug reports. |
I'm not familiar with Licenses.
I've already started using qlibc. I've got qunit.h file, and I'm trying first assertions. |
@mwlodarski, you can do all of them and whatever you want. |
@wolkykim If I change your source code (not big changes, for example add assertion, change display, or even write comments), what would you suggest
|
@mwlodarski Hi,
I think those examples that you mention are beneficial to qLibc project, those work is not something related to a specific purpose but enhancing qLibc itself in general. Whenever you find better way to improve any part of qLibc codes (that includs comments, code polishing/formatting, better variable names, ...), I highly recommend to work with main line and send pull requests. That's the way we can keep improving qLibc together and why I've published it to public domain. Did I answer your questions? |
Not exactly. |
qLibc is aiming to serve general library areas. Just wondering what would be the application specific changes in what part in your case? Can you tell me that? I'm only asking this question to understand if there's any part of code I can improve in qLibc because as I mentioned, there should be no need to implement user land specific codes inside of qlibc and qlibc should be able to stand alone as an underlying library without any modifications. |
by the way, giving a star to this project helps! :) |
Don't know yet. Just started with a single file and got one idea. |
Looks like qlibc is now a Buildroot package: https://github.com/maximeh/buildroot/tree/master/package/qlibc |
Ohu~ it's been very quiet for long years and just in a night~ Thank you @kirbyfan64 |
I am using the qlibc code in a couple commercial projects. I needed .ini file parsing in C++ and qlibc made it easy. Thanks. |
@ tkelleher Thanks a lot for sharing your experience. I'll make sure the INI file parser to be kept well in good shape for ya. |
Thank you. On Fri, Nov 13, 2015 at 3:43 AM, wolkykim notifications@github.com wrote:
Terry Kelleher |
I use the containers and qdatabase for some internal projects. works great ! Thanks for your efforts |
It's always my great pleasure to know how it gets used.
Please leave your comment if you're using qlibc.
And any change, giving a Star to the project helps!
Many thanks.
The text was updated successfully, but these errors were encountered: