Angus Leeming <[EMAIL PROTECTED]> writes:
| Attached is a patch that does no more than rename the four header files to
| std_string.h, std_sstream.h, std_istream.h, std_ostream.h, placing them in
| support.
>
| part 2 will be to move the
| using std::stringstream;
| using std::i
Lars Gullik Bjønnes wrote:
> You really need to communicate yoru to-do list...
I do? Well I think that it can be summarised as enhancing LyX's interaction
with the outside world. It covers a range of sins, but boost::filesystem is
probably among them ;-) What I do not want to do is get caught up
src/support/std_string.h
| src/Lsstream.h -> src/support/std_sstream.h
| src/support/LIstream.h -> src/support/std_istream.h
| src/support/LOstream.h -> src/support/std_ostream.h
| It also removes the
| using std::istringstream;
| usi
This has been on my to-do list for about three years. I guess that something
finally snapped ;-)
Attached is a patch which moves
src/LString.h -> src/support/std_string.h
src/Lsstream.h -> src/support/std_sstream.h
src/support/LIst
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>> sstream is not present in gcc 2.95.2 (only 2.95.3).
Andre> I know, but it is easily worked around by simply including the
Andre> sstream header file we are using right now.
The other problem (which forces the .str().c_str() stuff) is
> sstream is not present in gcc 2.95.2 (only 2.95.3).
I know, but it is easily worked around by simply including the sstream
header file we are using right now.
Andre'
--
André Pönitz . [EMAIL PROTECTED]
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>> They are moved in global namespace because if we define our own, we
>> want to define them in global namespace (if only to avoid clashes).
>> Indeed the same should be done for stringstream.
Andre> What are the plans for 1.2.0 anyway?
On Friday 13 July 2001 13:18, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Is there any reason why istringstream and ostringstream are
> Angus> moved into the global namespace. If so, why isn't stringstream
> Angus> as well. Can I not just re
> They are moved in global namespace because if we define our own, we
> want to define them in global namespace (if only to avoid clashes).
> Indeed the same should be done for stringstream.
What are the plans for 1.2.0 anyway?
Didn't somebody (you(?)) mention g++ 2.95 as minimum requirement lat
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Is there any reason why istringstream and ostringstream are
Angus> moved into the global namespace. If so, why isn't stringstream
Angus> as well. Can I not just remove the using directives and put
Angus> them in the .C files?
They
Is there any reason why istringstream and ostringstream are moved into the
global namespace. If so, why isn't stringstream as well. Can I not just
remove the using directives and put them in the .C files?
Angus
#ifndef LSSTREAM_H
#define LSSTREAM_H
// Since we will include a string header a
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| In most of the C++ files incuding Lsstream.h, this file is just after
| config.h, and even before LString.h and the implementation pragmas.
| This makes LString.h output an error with gcc 2.95.3+lyxstring. Is it
| OK if I move it later
In most of the C++ files incuding Lsstream.h, this file is just after
config.h, and even before LString.h and the implementation pragmas.
This makes LString.h output an error with gcc 2.95.3+lyxstring. Is it
OK if I move it later in the include list or is there some subtle
reason I am missing
13 matches
Mail list logo
