example input-file.py does offer --infile option, but does not use it
python __skip_whitespace binary read issue
Added building with CMake and packaging with CPack
Fixed error in unidentified_flags: the default value for an arg must be in the header.
Split this repo into multiple repos (each one for each language) and use git instead of svn
GetPot cannot be included multiple times in C++
Are you talking about GetPot? How did you get this idea? As for Quex, I will be working on migrating in the near future.
Seems reasonable on the surface, I'll have a deeper poke about soon. Looks like you decided to go with the LGPL instead of MIT?
Ok, done. Would you mind to have a look. The Unit Tests for C++ are all working. Java, Python, and Ruby have some examples coming along. However, they might need some more Unit Tests.
Prepare Release 2.0
Progress fixing Bug28
I am currently working on it. While doing so, I found may places where 'c_str()' has been used in a problematic manner. This might take some more time.
c_str() is used without caution
Documentation improved
Yes indeed!
I will take some time in the next couple of days. Would the content of the repository comply to your requirements?
I'll look into it once I'm able. When are you planning on rolling a new GetPot release with the license changes?
Thanks, someone contributed the Debian packaging. However, I never initiated the submission out of fear that I might not have the time for much discussions. I would be happy to get some support from someone who has experience with the process. Could you take the debian package as a basis?
I'm happy to help, although it looks like you're already building a deb. What issues have you run into?
Once, this is done, would you mind supporting me getting Quex into the distributions? This is still something I have been putting on the long finger ...
Once, this is done, would you mind supporting me getting Quex into the distributions? This is still something I am putting on the long finger ...
As far as the issues that started this discussion, your modifications look great, thank you! Note that several examples are still licensed under the LGPL, but there's really no issue with that. Just wanted to make sure you were aware given the move to MIT.
I finally setup something under MIT License, so it would be the least intrusive. https://sourceforge.net/p/getpot/trunk/HEAD/tree/ Would you mind reviewing the content. Only Python, C++ and Ruby are supposed to be functional. I must admit that it has been quite some time, that I was working on that piece of software ...
Minor Fix
Clean up
Initial commit
I alteady did dome prep to publish under MIT. Just need to sit down an hour for finishing up.
Hey there Frank, just wanted to check on this one. Any progress? Can I help?
Thanks Frank, I appreciate that! If it helps, here's my suggested patch (applied to v1.1.18), updating the header as well to conform with https://www.gnu.org/licenses/gpl-howto.en.html: diff -ru getpot-c++-backup/examples/nominus_followers.cpp getpot-c++/examples/nominus_followers.cpp --- getpot-c++-backup/examples/nominus_followers.cpp 2017-10-26 12:54:40.233756391 -0700 +++ getpot-c++/examples/nominus_followers.cpp 2017-10-26 13:12:43.760490217 -0700 @@ -3,24 +3,19 @@ // // (C) 2006 Frank R. Schaefer...
Thanks Frank, I appreciate that! If it helps, here's my suggested patch (applied to v1.1.18): diff -ru getpot-c++-backup/examples/nominus_followers.cpp getpot-c++/examples/nominus_followers.cpp --- getpot-c++-backup/examples/nominus_followers.cpp 2017-10-26 12:54:40.233756391 -0700 +++ getpot-c++/examples/nominus_followers.cpp 2017-10-26 13:12:43.760490217 -0700 @@ -3,24 +3,19 @@ // // (C) 2006 Frank R. Schaefer // -// NOTE: The LPGL License for this library is only valid in case that -// it is not...
I hope, I will find a time slot on the weekend. I will do the change. Thanks.
My humble apologies for the delay, Frank, I didn't realize that SF didn't subscribe you to your own posts! I am, now. I appreciate the waiver, however, there are still a few issues. While I might be able to convince the NEW queue reviewers that "this thread over here means this is okay" (that queue is not small, I don't want to go through it more than necessary), I essentially have to maintain a getpot fork just for license headers, which isn't ideal. The waiver is ambiguous. Does it only apply to...
My humble apologies for the delay, Frank, I didn't realize that SF didn't subscribe you to your own posts! I am, now. I appreciate the waiver, however, there are still a few issues. While I might be able to convince the NEW queue reviewers that "this thread over here means this is okay," I essentially have to maintain a getpot fork just for license headers, which isn't ideal. That queue is not small, I don't want to go through it more than necessary. The waiver is ambiguous. Does it only apply to...
My humble apologies for the delay, Frank, I didn't realize that SF didn't subscribe you to your own posts! I am, now. I appreciate the waiver, however, there are still a few issues. While I might be able to convince the NEW queue reviewers that "this thread over here means this is okay," I essentially have to maintain a getpot fork just for license headers, which isn't ideal. The waiver is ambiguous. Does it only apply to Debian? What about Debian derivatives? What about Fedora? These difficulties...
My humble apologies for the delay, Frank, I didn't realize that SF didn't subscribe you to your own posts! I am, now. I appreciate the waiver, however, there are a few issues. While I might be able to convince the NEW queue reviewers that "this thread over here means this is okay," I essentially have to maintain a getpot fork just for license headers, which isn't ideal. The waiver is ambiguous. Does it only apply to Debian? What about Debian derivatives? What about Fedora? These difficulties would...
My humble apologies for the delay, Frank, I didn't realize that SF didn't subscribe you to your own posts! I am, now. I appreciate the waiver, however, there are a few issues. While I might be able to convince the NEW queue reviewers that "this thread over here means this is okay," I essentially have to maintain a getpot fork just for license headers, which isn't ideal. The waiver is ambiguous. Does it only apply to Debian? What about Debian derivatives? What about Fedora? These difficulties would...
My humble apologies for the delay, Frank, I didn't realize that SF didn't subscribe you to your own posts! I am, now. I appreciate the waiver, however, there are a few issues. While I might be able to convince the NEW queue reviewers that "this thread over here means this is okay," I essentially have to maintain a getpot fork just for license headers, which isn't ideal. The waiver is ambiguous. Does it only apply to Debian? What about Debian derivatives? What about Fedora? These difficulties would...
By the way, thanks for your efforts! I was wondering if you could give me a hand getting the quex project submitted into debian. Best Regards, Frank
you may quote this posting as reference where I allow the removal of the non- military clause and replacement of "please do not use it for military purposes".
I was hoping to get GetPot into Debian, but its "no military" text violates the Debian Free Software Guidelines. Would you consider removing that text to allow for wider distribution and usage?
Please, provide an example. Do you mean, you want to have the token-ids sorted by...
Ticket moved from /p/quex/bugs/295/
Section selectivity in unidentified_variables()
Sorry, didn't mean to be rude. I wrote this bug report. Also, thanks for this tool,...
GetPot::absorb() doesn't work with sections.