| 6 |
|
* redistribute this software in source and binary code form, provided |
| 7 |
|
* that the following conditions are met: |
| 8 |
|
* |
| 9 |
< |
* 1. Acknowledgement of the program authors must be made in any |
| 10 |
< |
* publication of scientific results based in part on use of the |
| 11 |
< |
* program. An acceptable form of acknowledgement is citation of |
| 12 |
< |
* the article in which the program was described (Matthew |
| 13 |
< |
* A. Meineke, Charles F. Vardeman II, Teng Lin, Christopher |
| 14 |
< |
* J. Fennell and J. Daniel Gezelter, "OOPSE: An Object-Oriented |
| 15 |
< |
* Parallel Simulation Engine for Molecular Dynamics," |
| 16 |
< |
* J. Comput. Chem. 26, pp. 252-271 (2005)) |
| 17 |
< |
* |
| 18 |
< |
* 2. Redistributions of source code must retain the above copyright |
| 9 |
> |
* 1. Redistributions of source code must retain the above copyright |
| 10 |
|
* notice, this list of conditions and the following disclaimer. |
| 11 |
|
* |
| 12 |
< |
* 3. Redistributions in binary form must reproduce the above copyright |
| 12 |
> |
* 2. Redistributions in binary form must reproduce the above copyright |
| 13 |
|
* notice, this list of conditions and the following disclaimer in the |
| 14 |
|
* documentation and/or other materials provided with the |
| 15 |
|
* distribution. |
| 28 |
|
* arising out of the use of or inability to use software, even if the |
| 29 |
|
* University of Notre Dame has been advised of the possibility of |
| 30 |
|
* such damages. |
| 31 |
+ |
* |
| 32 |
+ |
* SUPPORT OPEN SCIENCE! If you use OpenMD or its source code in your |
| 33 |
+ |
* research, please cite the appropriate papers when you publish your |
| 34 |
+ |
* work. Good starting points are: |
| 35 |
+ |
* |
| 36 |
+ |
* [1] Meineke, et al., J. Comp. Chem. 26, 252-271 (2005). |
| 37 |
+ |
* [2] Fennell & Gezelter, J. Chem. Phys. 124, 234104 (2006). |
| 38 |
+ |
* [3] Sun, Lin & Gezelter, J. Chem. Phys. 128, 234107 (2008). |
| 39 |
+ |
* [4] Kuang & Gezelter, J. Chem. Phys. 133, 164101 (2010). |
| 40 |
+ |
* [5] Vardeman, Stocker & Gezelter, J. Chem. Theory Comput. 7, 834 (2011). |
| 41 |
|
*/ |
| 42 |
|
|
| 43 |
|
/** |
| 44 |
|
* @file StringTokenizer.hpp |
| 45 |
|
* @author tlin |
| 46 |
|
* @date 09/20/2004 |
| 46 |
– |
* @time 11:30am |
| 47 |
|
* @version 1.0 |
| 48 |
|
*/ |
| 49 |
|
|
| 54 |
|
#include <stdlib.h> |
| 55 |
|
#include <vector> |
| 56 |
|
#include "config.h" |
| 57 |
< |
namespace oopse { |
| 57 |
> |
namespace OpenMD { |
| 58 |
|
|
| 59 |
|
/** |
| 60 |
< |
* @class StringTokenizer.hpp "util/StringTokenizer.hpp" |
| 60 |
> |
* @class StringTokenizer |
| 61 |
|
* @brief The string tokenizer class allows an application to break a string into tokens |
| 62 |
|
* The set of delimiters (the characters that separate tokens) may be specified either |
| 63 |
|
* at creation time or on a per-token basis. |
| 89 |
|
* @note this is still a little bit java like implementation. Pure c++ one should use TokenIterator. |
| 90 |
|
* Boost's tokenizer class is one of them |
| 91 |
|
*/ |
| 92 |
< |
StringTokenizer(std::string::const_iterator& first, std::string::const_iterator& last, |
| 92 |
> |
StringTokenizer(std::string::const_iterator& first, |
| 93 |
> |
std::string::const_iterator& last, |
| 94 |
|
const std::string & delim = " ;\t\n\r"); |
| 95 |
|
|
| 96 |
|
/** |
| 181 |
|
* @return all of the tokens |
| 182 |
|
*/ |
| 183 |
|
std::vector<std::string> getAllTokens(); |
| 184 |
+ |
/** |
| 185 |
+ |
* Returns the remaining unparsed string |
| 186 |
+ |
* @return the remaining unparsed string |
| 187 |
+ |
*/ |
| 188 |
+ |
std::string getRemainingString(); |
| 189 |
|
private: |
| 190 |
|
|
| 191 |
|
/** |
| 209 |
|
std::string::const_iterator end_; |
| 210 |
|
}; |
| 211 |
|
|
| 212 |
< |
} //namespace oopse |
| 212 |
> |
} //namespace OpenMD |
| 213 |
|
|
| 214 |
|
#endif //UTIL_STRINGTOKENIZER_HPP |
