> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> No screams of protest heard so I'm sending this off in about an
Allan> hour -- I should have cleaned it up and got the various email
Allan> addresses by then.
Allan> So scream now before it's too late
It looks good, Allan. Go for
No screams of protest heard so I'm sending this off in about an hour
-- I should have cleaned it up and got the various email addresses by
then.
So scream now before it's too late
Allan.
[hopefully the final draft... I would like to get this to lwn this week]
On Thu, 13 Jan 2000, Allan Rae wrote:
> On Tue, 11 Jan 2000, Allan Rae wrote:
>
> > NOT FOR RELEASE
> > DO NOT REMOVE THE ABOVE LINE
> >
> > Target audience: freshmeat, linuxdev.net, slashdot, icewalkers, c.o.l.a.
> >
>
> Why don't we - as a kind of publicity gag and to attract more users and
> developers - prepare some blurb/project in this field and claim
> compliance?
I surely do not want to claim anything I can't deliver. Even as a 'kind
of publicity gag'.
Andre'
--
André Pönitz .
"Arnd Hanses" <[EMAIL PROTECTED]> writes:
| Hey, I've just found the most simple and most radical solution: Compile
| with
|
| cxx -ansi -pedantic -terroristic -D__ULTRA_STRICT_ANSI__
| -D_KALASHNIKOW
|
| and let the compiler shoot everybody who introduces a non-standard
| function.
Mmm, li
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> The problem seems to be that to compile system specifics with
| Lars> C++ you have to include the C headers... not a very good
| Lars> solution.
|
| How far can we go wit
"Arnd Hanses" <[EMAIL PROTECTED]> writes:
| separate library. Rethinking this, I would even propose:
|
| Put all low-level stuff into a separate opaque C library !
A C lib is not needed, but we might need a C++ lib that does this.
I have moved a couple of "UNIX" functions out of the lyx
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> The problem seems to be that to compile system specifics with
Lars> C++ you have to include the C headers... not a very good
Lars> solution.
How far can we go with C++ only stuff? Is it possible to do signals for
example in pu
>
> Hey, I've just found the most simple and most radical solution: Compile
> with
>
> cxx -ansi -pedantic -terroristic -D__ULTRA_STRICT_ANSI__
> -D_KALASHNIKOW
>
> and let the compiler shoot everybody who introduces a non-standard
> function.
>
I guess then we won't have a lot developers
On 13 Jan 2000 17:43:29 +0100, Lars Gullik Bj°nnes wrote:
>Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
>| > "Lars" == Lars Gullik Bj°nnes <[EMAIL PROTECTED]> writes:
>|
>| Lars> The problem is not C library functions, but "UNIX" functions
>| Lars> declared in C headers. (IMHO a mistak
On 13 Jan 2000 16:58:30 +0100, Lars Gullik Bj°nnes wrote:
>Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
>|
>| If we want to have CC compile lyx easily, we have to settle the
>| question of adding 'usingstd::foo' where foo is a C library function.
>| The problem is that cxx does not like th
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> The problem is not C library functions, but "UNIX" functions
| Lars> declared in C headers. (IMHO a mistake, but now we have to cary
| Lars> the inheritance garbage.)
|
|
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> The problem is not C library functions, but "UNIX" functions
Lars> declared in C headers. (IMHO a mistake, but now we have to cary
Lars> the inheritance garbage.)
I have to admit that I do not really understand the difference,
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| - the reserve() problem, since the out of memory as reported by Jose'
| did not allow to get something under gdb.
I have remvoed the reserves from paragraph.C since this is already
done in the constructor. I have also added a resize after the
On Thu, 13 Jan 2000 12:33:40 +1000 (GMT+1000), Allan Rae wrote:
>
>[ here's my slightly modified version of Martin's PR]
>[Don't want to much otherwise we won't have anything new to say for the
> 1.2.0 release PR]
>
>LyX is an advanced open-source document processor running on many Unix
>platform
> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
I am very frustrated to see that I do not have much negative stuff to
say about your PR 8-]
I'll try anyway.
>> These changes include: * Use of std::streams (istream, ostream,
>> fstream, strstream) * Use of std::string * Use of the Standa
On Tue, 11 Jan 2000, Allan Rae wrote:
> NOT FOR RELEASE
> DO NOT REMOVE THE ABOVE LINE
>
> Target audience: freshmeat, linuxdev.net, slashdot, icewalkers, c.o.l.a.
>
>
> [We need a brief introductory paragraph of what and who LyX and The LyX
> Team are. We should be able to pinch that fro
On 12 Jan 2000, Jean-Marc Lasgouttes wrote:
> > "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
>
> Michael> Hmmm, looks like Lyx 1.1.4 is almost finished.
Not yet.
> Michael> As you know I have experienced a lot of problems when
> Michael> compiling Lyx with Sun CC (which IMHO ar
> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
Michael> Hmmm, looks like Lyx 1.1.4 is almost finished.
Michael> As you know I have experienced a lot of problems when
Michael> compiling Lyx with Sun CC (which IMHO are no problems of Sun
Michael> CC). I also uncovered a lot of runt
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Purify does not nessiccarily detect runtime erros, it more like
Lars> constructs to be wary about.
Well, the error logs given by Michael have allowed me to find
- a mismatched new/free() pair allocation in figinset, which may
Michael Schmitt <[EMAIL PROTECTED]> writes:
| Hmmm,
|
| looks like Lyx 1.1.4 is almost finished.
|
| As you know I have experienced a lot of problems when compiling Lyx with
| Sun CC (which IMHO are no problems of Sun CC). I also uncovered a lot of
| runtime errors when running Lyx with Purify
Hmmm,
looks like Lyx 1.1.4 is almost finished.
As you know I have experienced a lot of problems when compiling Lyx with
Sun CC (which IMHO are no problems of Sun CC). I also uncovered a lot of
runtime errors when running Lyx with Purify
(it just takes me a few minutes to find some new bugs).
T
NOT FOR RELEASE
DO NOT REMOVE THE ABOVE LINE
Target audience: freshmeat, linuxdev.net, slashdot, icewalkers, c.o.l.a.
[We need a brief introductory paragraph of what and who LyX and The LyX
Team are. We should be able to pinch that from our previous PR]
In September 1999 the LyX Team deci
23 matches
Mail list logo
