On Mon, 5 Jan 2004, Lars Gullik Bjønnes wrote:
If you want obfuscation have a look at this.
(no, I won't actually admit that this is obfuscated.)
(I find especially the logical_and usage a bit funny :-) )
Ok... I read about half of it before I got tired... My conclusion is that
Lars is
Christian Ridderström wrote:
On Mon, 5 Jan 2004, Lars Gullik Bjønnes wrote:
If you want obfuscation have a look at this.
(no, I won't actually admit that this is obfuscated.)
(I find especially the logical_and usage a bit funny :-) )
Ok... I read about half of it before I got tired... My
Christian Ridderström [EMAIL PROTECTED] writes:
| On Sun, 4 Jan 2004, Lars Gullik Bjønnes wrote:
Where is the obfuscation?
| I found
| list.remove_if(bind2nd(match(), s));
| easier to understand on a high level compared to
| list.remove_if(bind(equal_tostring(),
|
Christian Ridderström [EMAIL PROTECTED] writes:
| On Mon, 5 Jan 2004, Lars Gullik Bjønnes wrote:
If you want obfuscation have a look at this.
(no, I won't actually admit that this is obfuscated.)
(I find especially the logical_and usage a bit funny :-) )
| Ok... I read about half of it
Angus Leeming [EMAIL PROTECTED] writes:
| Finally, I agree that Lars would carry all before him if he used
| code like this.
I am not quite sure what this sentence means, can you spell it out for
me?
| The intent is transparent and it is the intent that I'm
| interested in when reading
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| | Just guessing from the name 'lambda'... isn't it like the lambda
| | operator in lisp etc?
| A little bit.
| I am not sure of the lambda syntax, but it might look like:
| _1-getBranch() == name
Ah... I didn't see that you had created a
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| that is of course also my goal. and a lot of intent is hidden in bad
| nameing. (match() anyone..., ok we are matching... but _what_. Just
| naming the functor EqualBranchNames() would make things a lot nicer.)
Did you see there there were two
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Angus Leeming [EMAIL PROTECTED] writes:
| | Finally, I agree that Lars would carry all before him if he used
| | code like this.
| I am not quite sure what this sentence means, can you spell it out for
| me?
|
| | The intent is transparent and
Lars Gullik Bjønnes wrote:
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| that is of course also my goal. and a lot of intent is hidden in
| bad nameing. (match() anyone..., ok we are matching... but _what_.
| Just naming the functor EqualBranchNames() would make things a lot
| nicer.)
Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| Finally, I agree that Lars would carry all before him if he used
| code like this.
I am not quite sure what this sentence means, can you spell it out
for me?
Nobody could possibly complain if you introduced code such
Angus Leeming [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| that is of course also my goal. and a lot of intent is hidden in
| bad nameing. (match() anyone..., ok we are matching... but _what_.
| Just naming the functor
Lars Gullik Bjønnes wrote:
Also the reason why I did all this was a direct result of reading
Effective STL by Scott Meyers.
Main recommandations about functors:
- operator() should always be const
(functors might be copied around by standard
On Fri, Jan 02, 2004 at 08:06:06PM +0100, Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| On Wed, Dec 10, 2003 at 11:16:16AM +0100, Michael Schmitt wrote:
Hi Andre,
I have seen that you removed method insertInset. Could you please tell
me where the magic code is
On Fri, Jan 02, 2004 at 08:11:05PM +0100, Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| Andre Poenitz wrote:
Have you considered changing that params2string interface to
| ...
(or when we are at it even
ostream InsetBranchMailer::operator(ostream os,
Angus Leeming [EMAIL PROTECTED] writes:
| Yes, it's a good book.
yes it is.
| I note a couple of functors in your patch where the operator() is
| const but the variables have become mutable. That seems to me to be
| a total cheat ;-)
Yes. I am not happy about it. (except for the RegEx one).
On Sat, Jan 03, 2004 at 12:36:17AM +0100, Lars Gullik Bjønnes wrote:
Is this really an iterator... or an container with some iterator
properties?
It is an iterator.
_If_ it is an iterator it should inherit from std::iterator.
(to make it work when needed with std algorithms.)
What feature
Angus Leeming [EMAIL PROTECTED] writes:
that is of course also my goal. and a lot of intent is hidden in bad
nameing. (match() anyone..., ok we are matching... but _what_. Just
naming the functor EqualBranchNames() would make things a lot
nicer.)
| Agree whole-hearedly.
So this is what my
Andre Poenitz [EMAIL PROTECTED] writes:
| On Fri, Jan 02, 2004 at 08:06:06PM +0100, Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| On Wed, Dec 10, 2003 at 11:16:16AM +0100, Michael Schmitt wrote:
Hi Andre,
I have seen that you removed method insertInset. Could you
Andre Poenitz [EMAIL PROTECTED] writes:
| On Sat, Jan 03, 2004 at 12:36:17AM +0100, Lars Gullik Bjønnes wrote:
Is this really an iterator... or an container with some iterator
properties?
| It is an iterator.
_If_ it is an iterator it should inherit from std::iterator.
(to make it work
Lars Gullik Bjønnes wrote:
So this is what my new version of BranchList.C looks like:
I have no complaints about this at all.
Do I understand things correctly if I say that you now think that
nested binds are not an improvement?
An aside: you said in an earlier mail something about only
On Sat, Jan 03, 2004 at 03:24:49PM +0100, Lars Gullik Bjønnes wrote:
I know that I am the one who began introducing pimpls to lyx. After
that I have become quite wary of them... and feel more and more that
you should have a good reason to use them.
This boils down to: (right now) What is
Lars Gullik Bjønnes wrote:
| My question is whether we can avoid these arbitrarily-named
| functors and have code which is understandable at-a-glance. If the
| code above could be replaced with
| return (from == lambda::_1.from() to ==
| lambda::_2.to());
| then I'd be very
On Mon, Jan 05, 2004 at 10:16:39AM +0100, Lars Gullik Bjønnes wrote:
Christian Ridderström [EMAIL PROTECTED] writes:
| On Sun, 4 Jan 2004, Lars Gullik Bjønnes wrote:
Where is the obfuscation?
| I found
| list.remove_if(bind2nd(match(), s));
| easier to understand on a high
Bo Peng wrote:
By wrong formula, I mean things like $\text{\alpha}$ entered by C-M
C-M \alpha etc. I have discussed this problem in the user list.
Currently, with instant preview turned on,
1. If a wrong formula is entered, instant preview will fail and do
nothing.
2. If a file with
On Mon, Jan 05, 2004 at 11:34:14AM +0100, Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
that is of course also my goal. and a lot of intent is hidden in bad
nameing. (match() anyone..., ok we are matching... but _what_. Just
naming the functor EqualBranchNames() would
On Mon, Jan 05, 2004 at 11:39:56AM +0100, Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| On Sat, Jan 03, 2004 at 12:36:17AM +0100, Lars Gullik Bjønnes wrote:
Is this really an iterator... or an container with some iterator
properties?
| It is an iterator.
Here is the template file for AGU XML. Ok to check it in (it won't
bite :-)?
- Martin
--
Martin Vermeer [EMAIL PROTECTED]
Helsinki University of Technology
Dept. of Surveying, Inst. of Geodesy
P.O. Box 1200, FIN-02015 HUT, Finland
:wq
#LyX 1.4.0cvs created this file. For more info see
Is there a safe way of initialising a c-struct? I have this:
vectorstring const glob(string const pattern, int flags)
{
glob_t glob_buffer = {0, 0, 0, 0, 0, 0, 0, 0, 0};
glob(pattern.c_str(), flags, 0, glob_buffer);
vectorstring const matches(glob_buffer.gl_pathv,
Angus Leeming [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
So this is what my new version of BranchList.C looks like:
| I have no complaints about this at all.
| Do I understand things correctly if I say that you now think that
| nested binds are not an improvement?
Let's say: not
On Mon, Jan 05, 2004 at 02:01:03PM +, Angus Leeming wrote:
Is there a safe way of initialising a c-struct? I have this:
vectorstring const glob(string const pattern, int flags)
{
glob_t glob_buffer = {0, 0, 0, 0, 0, 0, 0, 0, 0};
This is safe.
Andre'
Lars Gullik Bjønnes wrote:
I thought not... let me check... I can not see it here:
http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2003/n1540.pdf
My misunderstanding then. Thanks.
(I do keep reading of Joel de Guzmann's on-going Fusion of bind,
lambda and mpl and that lambda and bind cannot
On Monday 05 January 2004 2:20 pm, Andre Poenitz wrote:
On Mon, Jan 05, 2004 at 02:01:03PM +, Angus Leeming wrote:
Is there a safe way of initialising a c-struct? I have this:
vectorstring const glob(string const pattern, int flags)
{
glob_t glob_buffer = {0, 0, 0, 0, 0, 0,
On Friday 02 January 2004 19:29, Angus Leeming wrote:
Does it work with compressed postscript files?
Yes. The original file is already converted (of necessary).
--
José Abílio
LyX and docbook, a perfect match. :-)
On Monday 05 January 2004 13:35, Martin Vermeer wrote:
Here is the template file for AGU XML. Ok to check it in (it won't
bite :-)?
Yes, long due also. ;-)
- Martin
--
José Abílio
Jean-Marc Lasgouttes wrote:
spitz Log message: Fix Minipage.lyx example file. Jean-Marc, should I
spitz apply this to 1.3.x too?
Could you tell me again why this is needed?
Some time in the past, we had LyX units like c%, t% etc. Eventually, they have
been changed to col%, text% etc., but
Attached are the changes I've made to enable us to define the
FileFilter in external_templates as a conformant globbing pattern and
for this to be useful in both the Qt and xforms frontends.
--
Angus
glob.diff.gz
Description: GNU Zip compressed data
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Attached are the changes I've made to enable us to define the
Angus FileFilter in external_templates as a conformant globbing
Angus pattern and for this to be useful in both the Qt and xforms
Angus frontends.
Looks good...
JMarc
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:
Juergen Jean-Marc Lasgouttes wrote:
spitz Log message: Fix Minipage.lyx example file. Jean-Marc, should I
spitz apply this to 1.3.x too?
Could you tell me again why this is needed?
Juergen Some time in the past, we had LyX units like
sorry for the PM to Leeming.
Loading an existing document containing such an inset results in no
previews being generated at all, as now.
Locating a wrong formula among others is extremely difficult (may have
to compile all formulas one by one.) so there is no good solution yet.
In
Bo Peng wrote:
sorry for the PM to Leeming.
Not a problem.
Loading an existing document containing such an inset results in no
previews being generated at all, as now.
Locating a wrong formula among others is extremely difficult (may
have to compile all formulas one by one.) so there
On Mon, 5 Jan 2004, Lars Gullik Bjønnes wrote:
If you as a not so experienced C++ STL programmer can grasp the use of
bind this quickly I am not worried about obfuscation.
I was experienced in C++ a decade ago but haven't really used it since...
In those days there was no bind, and templates
I've been mulling over how best to handle compressed postscript files
with InsetExternal.
ramble
insetgraphics.C has some special-casing code to handle compressed
files (which latex can handle in their compressed state). Rather than
retain this special-casing code in insetexternal.C, I wonder
The information is present in the latex log file. I'm not saying that
it is easy to manipulate, but it is certainly possible.
Great. I will mess with the log file and try to identify the wrong
formula when a file is loaded. This will certainly make this patch more
useful.
--
Bo Peng
Christian Ridderström wrote:
You're welcome... btw, you have referred to 'tr1' in some of the
mails, what is that?
The extensions to the C++ standard library are collectively know as
Technical Report #1 and have beed tentatively grouped together in
sub-namespace std::tr1. See
Christian Ridderström [EMAIL PROTECTED] writes:
No I don't agree.
| You don't find the first form easier to read?
I think I agree after all :-) I just had to disagree at first go.
| You're welcome... btw, you have referred to 'tr1' in some of the mails,
| what is that?
The upcomming
Lars Gullik Bjønnes wrote:
Some stuff are different in this patch (but not that much...), most
notably is the use of boost::indirect_iterator to get rid of the
bind(Format::name, bind(operator-, _1))
construct.
Once I found the code... very nice.
btw. AFAIK the boost iterator adaptors
Angus Leeming [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
Some stuff are different in this patch (but not that much...), most
notably is the use of boost::indirect_iterator to get rid of the
bind(Format::name, bind(operator-, _1))
construct.
| Once I found the code... very nice.
On Sunday 04 January 2004 01:17, Christian Ridderström wrote:
In order to not lose the thoughts in the mails, I put some notes here:
http://wiki.lyx.org/pmwiki.php/Devel/SpellCheckAsYouType
but I guess it needs a bit of structuring. And I might have missed
important things etc. (I've
Lars Gullik Bjønnes wrote:
| Sorry to drop a spanner in your well-oiled machine, but I really
| must point out that boost::function introduces an indirection
| equivalent to a virtual function call. Thus a change like this
| which affects the inner loop is likely to introduce a significant
|
Configuration
Host type: sparc-sun-solaris2.8
Special build flags:warnings assertions xforms-image-loader compression
C Compiler: gcc
C Compiler flags: -g -O2
C++ Compiler: g++ (3.2.3)
C++ Compiler
Angus Leeming [EMAIL PROTECTED] writes:
| H. I don't know what I'm talking about in detail, but boost::bind
| is not the same as boost::function. Specifically, I believe that
| there is no performance hit at all in using boost::bind.
Hmm... I was pretty sure that since Foo::bar is used
I have updated my previous patch. It now can:
1. If a wrong formula is entered, a 'formula does not compile' box will
be displayed rather than the orginal lyx math box.
2. If a file with wrong formula(s) is opened, the perl script will
locate the wrong formula(s) and replace them with
On Mon, 5 Jan 2004, Lars Gullik Bjønnes wrote:
> If you want obfuscation have a look at this.
> (no, I won't actually admit that this is obfuscated.)
> (I find especially the logical_and usage a bit funny :-) )
Ok... I read about half of it before I got tired... My conclusion is that
Lars is
Christian Ridderström wrote:
> On Mon, 5 Jan 2004, Lars Gullik Bjønnes wrote:
>
>> If you want obfuscation have a look at this.
>> (no, I won't actually admit that this is obfuscated.)
>> (I find especially the logical_and usage a bit funny :-) )
>
> Ok... I read about half of it before I got
Christian Ridderström <[EMAIL PROTECTED]> writes:
| On Sun, 4 Jan 2004, Lars Gullik Bjønnes wrote:
>
>> >> Where is the obfuscation?
>
| I found
>
| list.remove_if(bind2nd(match(), s));
>
| easier to understand on a high level compared to
>
| list.remove_if(bind(equal_to(),
|
Christian Ridderström <[EMAIL PROTECTED]> writes:
| On Mon, 5 Jan 2004, Lars Gullik Bjønnes wrote:
>
>> If you want obfuscation have a look at this.
>> (no, I won't actually admit that this is obfuscated.)
>> (I find especially the logical_and usage a bit funny :-) )
>
| Ok... I read about half
Angus Leeming <[EMAIL PROTECTED]> writes:
| Finally, I agree that Lars would carry all before him if he used
| code like this.
I am not quite sure what this sentence means, can you spell it out for
me?
| The intent is transparent and it is the intent that I'm
| interested in when reading
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| | Just guessing from the name 'lambda'... isn't it like the lambda
| | operator in lisp etc?
>
| A little bit.
>
| I am not sure of the lambda syntax, but it might look like:
>
| _1->getBranch() == name
Ah... I didn't see that you had created
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| that is of course also my goal. and a lot of intent is hidden in bad
| nameing. (match() anyone..., ok we are matching... but _what_. Just
| naming the functor EqualBranchNames() would make things a lot nicer.)
Did you see there there were two
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Angus Leeming <[EMAIL PROTECTED]> writes:
>
| | Finally, I agree that Lars would carry all before him if he used
| | code like this.
>
| I am not quite sure what this sentence means, can you spell it out for
| me?
|
| | The intent is transparent
Lars Gullik Bjønnes wrote:
> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>
> | that is of course also my goal. and a lot of intent is hidden in
> | bad nameing. (match() anyone..., ok we are matching... but _what_.
> | Just naming the functor EqualBranchNames() would make things a lot
> |
Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | Finally, I agree that Lars would carry all before him if he used
> | code like this.
>
> I am not quite sure what this sentence means, can you spell it out
> for me?
Nobody could possibly complain if you introduced
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>
>> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>>
>> | that is of course also my goal. and a lot of intent is hidden in
>> | bad nameing. (match() anyone..., ok we are matching... but _what_.
>> | Just naming the
Lars Gullik Bjønnes wrote:
> Also the reason why I did all this was a direct result of reading
> "Effective STL" by Scott Meyers.
>
> Main recommandations about functors:
>
> - operator() should always be const
> (functors might be copied around by standard
>
On Fri, Jan 02, 2004 at 08:06:06PM +0100, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | On Wed, Dec 10, 2003 at 11:16:16AM +0100, Michael Schmitt wrote:
> >> Hi Andre,
> >>
> >> I have seen that you removed method "insertInset". Could you please tell
> >> me where
On Fri, Jan 02, 2004 at 08:11:05PM +0100, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | Andre Poenitz wrote:
> >> Have you considered changing that params2string interface to
> | ...
> >> (or when we are at it even
> >>
> >> ostream &
Angus Leeming <[EMAIL PROTECTED]> writes:
| Yes, it's a good book.
yes it is.
| I note a couple of functors in your patch where the operator() is
| const but the variables have become mutable. That seems to me to be
| a total cheat ;-)
Yes. I am not happy about it. (except for the RegEx
On Sat, Jan 03, 2004 at 12:36:17AM +0100, Lars Gullik Bjønnes wrote:
>
> Is this really an iterator... or an container with some iterator
> properties?
It is an iterator.
> _If_ it is an iterator it should inherit from std::iterator.
> (to make it work when needed with std algorithms.)
What
Angus Leeming <[EMAIL PROTECTED]> writes:
>> that is of course also my goal. and a lot of intent is hidden in bad
>> nameing. (match() anyone..., ok we are matching... but _what_. Just
>> naming the functor EqualBranchNames() would make things a lot
>> nicer.)
>
| Agree whole-hearedly.
So this
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Fri, Jan 02, 2004 at 08:06:06PM +0100, Lars Gullik Bjønnes wrote:
>> Andre Poenitz <[EMAIL PROTECTED]> writes:
>>
>> | On Wed, Dec 10, 2003 at 11:16:16AM +0100, Michael Schmitt wrote:
>> >> Hi Andre,
>> >>
>> >> I have seen that you removed method
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Sat, Jan 03, 2004 at 12:36:17AM +0100, Lars Gullik Bjønnes wrote:
>>
>> Is this really an iterator... or an container with some iterator
>> properties?
>
| It is an iterator.
>
>> _If_ it is an iterator it should inherit from std::iterator.
>> (to
Lars Gullik Bjønnes wrote:
> So this is what my new version of BranchList.C looks like:
I have no complaints about this at all.
Do I understand things correctly if I say that you now think that
nested binds are not an improvement?
An aside: you said in an earlier mail something about only
On Sat, Jan 03, 2004 at 03:24:49PM +0100, Lars Gullik Bjønnes wrote:
>
> I know that I am the one who began introducing pimpls to lyx. After
> that I have become quite wary of them... and feel more and more that
> you should have a good reason to use them.
>
> This boils down to: (right now)
Lars Gullik Bjønnes wrote:
> | My question is whether we can avoid these arbitrarily-named
> | functors and have code which is understandable at-a-glance. If the
> | code above could be replaced with
> | return (from == lambda::_1.from() && to ==
> | lambda::_2.to());
> | then I'd
On Mon, Jan 05, 2004 at 10:16:39AM +0100, Lars Gullik Bjønnes wrote:
> Christian Ridderström <[EMAIL PROTECTED]> writes:
>
> | On Sun, 4 Jan 2004, Lars Gullik Bjønnes wrote:
> >
> >> >> Where is the obfuscation?
> >
> | I found
> >
> | list.remove_if(bind2nd(match(), s));
> >
> | easier to
Bo Peng wrote:
> By wrong formula, I mean things like $\text{\alpha}$ entered by C-M
> C-M \alpha etc. I have discussed this problem in the user list.
>
> Currently, with instant preview turned on,
> 1. If a wrong formula is entered, instant preview will fail and do
>nothing.
> 2. If a file
On Mon, Jan 05, 2004 at 11:34:14AM +0100, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> >> that is of course also my goal. and a lot of intent is hidden in bad
> >> nameing. (match() anyone..., ok we are matching... but _what_. Just
> >> naming the functor
On Mon, Jan 05, 2004 at 11:39:56AM +0100, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | On Sat, Jan 03, 2004 at 12:36:17AM +0100, Lars Gullik Bjønnes wrote:
> >>
> >> Is this really an iterator... or an container with some iterator
> >> properties?
> >
> | It is an
Here is the template file for AGU XML. Ok to check it in (it won't
bite :-)?
- Martin
--
Martin Vermeer [EMAIL PROTECTED]
Helsinki University of Technology
Dept. of Surveying, Inst. of Geodesy
P.O. Box 1200, FIN-02015 HUT, Finland
:wq
#LyX 1.4.0cvs created this file. For more info see
Is there a safe way of initialising a c-struct? I have this:
vector const glob(string const & pattern, int flags)
{
glob_t glob_buffer = {0, 0, 0, 0, 0, 0, 0, 0, 0};
glob(pattern.c_str(), flags, 0, _buffer);
vector const matches(glob_buffer.gl_pathv,
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> So this is what my new version of BranchList.C looks like:
>
| I have no complaints about this at all.
>
| Do I understand things correctly if I say that you now think that
| nested binds are not an improvement?
Let's
On Mon, Jan 05, 2004 at 02:01:03PM +, Angus Leeming wrote:
> Is there a safe way of initialising a c-struct? I have this:
>
> vector const glob(string const & pattern, int flags)
> {
> glob_t glob_buffer = {0, 0, 0, 0, 0, 0, 0, 0, 0};
This is safe.
Andre'
Lars Gullik Bjønnes wrote:
> I thought not... let me check... I can not see it here:
>
> http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2003/n1540.pdf
My misunderstanding then. Thanks.
(I do keep reading of Joel de Guzmann's on-going Fusion of bind,
lambda and mpl and that lambda and bind
On Monday 05 January 2004 2:20 pm, Andre Poenitz wrote:
> On Mon, Jan 05, 2004 at 02:01:03PM +, Angus Leeming wrote:
> > Is there a safe way of initialising a c-struct? I have this:
> >
> > vector const glob(string const & pattern, int flags)
> > {
> > glob_t glob_buffer = {0, 0, 0, 0,
On Friday 02 January 2004 19:29, Angus Leeming wrote:
>
> Does it work with compressed postscript files?
Yes. The original file is already converted (of necessary).
--
José Abílio
LyX and docbook, a perfect match. :-)
On Monday 05 January 2004 13:35, Martin Vermeer wrote:
> Here is the template file for AGU XML. Ok to check it in (it won't
> bite :-)?
Yes, long due also. ;-)
> - Martin
--
José Abílio
Jean-Marc Lasgouttes wrote:
> spitz> Log message: Fix Minipage.lyx example file. Jean-Marc, should I
> spitz> apply this to 1.3.x too?
>
> Could you tell me again why this is needed?
Some time in the past, we had LyX units like c%, t% etc. Eventually, they have
been changed to col%, text% etc.,
Attached are the changes I've made to enable us to define the
FileFilter in external_templates as a conformant globbing pattern and
for this to be useful in both the Qt and xforms frontends.
--
Angus
glob.diff.gz
Description: GNU Zip compressed data
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Attached are the changes I've made to enable us to define the
Angus> FileFilter in external_templates as a conformant globbing
Angus> pattern and for this to be useful in both the Qt and xforms
Angus> frontends.
Looks good...
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
spitz> Log message: Fix Minipage.lyx example file. Jean-Marc, should I
spitz> apply this to 1.3.x too?
>> Could you tell me again why this is needed?
Juergen> Some time in the past, we had
< sorry for the PM to Leeming. >
> Loading an existing document containing such an inset results in no
> previews being generated at all, as now.
Locating a wrong formula among others is extremely difficult (may have
to compile all formulas one by one.) so there is no good solution yet.
> In
Bo Peng wrote:
> < sorry for the PM to Leeming. >
Not a problem.
>> Loading an existing document containing such an inset results in no
>> previews being generated at all, as now.
>
> Locating a wrong formula among others is extremely difficult (may
> have to compile all formulas one by one.)
On Mon, 5 Jan 2004, Lars Gullik Bjønnes wrote:
> If you as a not so experienced C++ STL programmer can grasp the use of
> bind this quickly I am not worried about obfuscation.
I was experienced in C++ a decade ago but haven't really used it since...
In those days there was no bind, and templates
I've been mulling over how best to handle compressed postscript files
with InsetExternal.
insetgraphics.C has some special-casing code to handle compressed
files (which latex can handle in their compressed state). Rather than
retain this special-casing code in insetexternal.C, I wonder if it
> The information is present in the latex log file. I'm not saying that
> it is easy to manipulate, but it is certainly possible.
Great. I will mess with the log file and try to identify the wrong
formula when a file is loaded. This will certainly make this patch more
useful.
--
Bo Peng
Christian Ridderström wrote:
> You're welcome... btw, you have referred to 'tr1' in some of the
> mails, what is that?
The extensions to the C++ standard library are collectively know as
Technical Report #1 and have beed tentatively grouped together in
sub-namespace std::tr1. See
Christian Ridderström <[EMAIL PROTECTED]> writes:
>> No I don't agree.
>
| You don't find the first form easier to read?
I think I agree after all :-) I just had to disagree at first go.
| You're welcome... btw, you have referred to 'tr1' in some of the mails,
| what is that?
The upcomming
Lars Gullik Bjønnes wrote:
> Some stuff are different in this patch (but not that much...), most
> notably is the use of boost::indirect_iterator to get rid of the
> bind(::name, bind(operator->, _1))
> construct.
Once I found the code... very nice.
> btw. AFAIK the boost iterator adaptors
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>
>> Some stuff are different in this patch (but not that much...), most
>> notably is the use of boost::indirect_iterator to get rid of the
>> bind(::name, bind(operator->, _1))
>> construct.
>
| Once I found the code... very
On Sunday 04 January 2004 01:17, Christian Ridderström wrote:
> In order to not lose the thoughts in the mails, I put some notes here:
>
> http://wiki.lyx.org/pmwiki.php/Devel/SpellCheckAsYouType
>
> but I guess it needs a bit of structuring. And I might have missed
> important things etc.
1 - 100 of 104 matches
Mail list logo
