Why the S?
On Wednesday, Aug 6, 2003, at 16:37 America/Denver, E. Gladyshev wrote:
--- Brock Peabody <[EMAIL PROTECTED]>
wrote:
That sounds good. What if we called the lower layer
boost::gui and the
upper layer boost::sgtl?
Agreed.
__
Do you Yahoo!?
Yahoo! Site
you missed the point, it runs completely correctly on my system
I don't need to "work around" anything, nor does boost.
IMO, the problem has been fixed
At Wednesday 2003-08-06 05:12, you wrote:
"Victor A. Wagner, Jr." <[EMAIL PROTECTED]> writes:
>>Test case (note that WinXP doesn't complain when p
--- Brock Peabody <[EMAIL PROTECTED]>
wrote:
> It stands for 'standard'. Maybe that's a little
> pretentious for us at
> this early stage :) gtl would probably be better.
> I suspect that if we
> get to a review some people may request something
> more verbose.
>
Since GTL is already taken,
At 09:53 AM 8/6/2003, Russell Hind wrote:
>John Maddock wrote:
>>
>> #ifdef __BORLANDC__
>> # pragma option push -a8 -b -Vx -Ve -pc -w-8027
>> #endif
>>
>> // code here
>>
>> #ifdef __BORLANDC__
>> # pragma option pop
>> #endif
>>
>> We should standardize this boost-wide really in some kind o
Brock Peabody wrote:
> I realize that this scheme won't solve all the world's problems, but
> it
> comes close :) You can imagine that one could come up with more
> composition functions, I just haven't needed any yet.
I've experimented with a similar system in the past. I feel that its
biggest
Philippe A. Bouchard wrote:
[...]
> I convertion function would be great also in the standards to have
> type
> names in a official way:
> demangle(typeid().name());
>
> C++ will then be able to communicate with external languages &
> vice-versa
Sorry, forget this idea I am getting tired.
Phi
--- Brock Peabody <[EMAIL PROTECTED]>
wrote:
> I wonder how much we will have to redo when we add
> in support for say
> Mac Os X or another *nix API. Is it going to be too
> complex to develop
> a single underlying code base that works on all of
> them? Would we be
> better off developing separ
- Original Message -
From: "Brian Simpson" <[EMAIL PROTECTED]>
> The general case devolves into an else-if-then:
> Let us assume that we have specializations up to a certain number,
> 'max_specialization_count'. Then we know that we can get switch-based
> runtime type selection ("rtts") o
"Aleksey Gurtovoy" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
FWIW, I've used a similar technique in MPL to do recursion unrolling
for the 'advance' algorithm:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/boost/boost/
boost/mpl/aux_/preprocessed/plain/advance_f
Why are we using such a cryptic namespace name? I mean, I can
understand wanting to abbreviate "template_metaprogramming", but
"filesystem" doesn't seem too bad and you could use "filesys"; people
will use namespace aliases anyway. Sorry to complain, but "fs" has
been rubbing me the wrong way si
Brock Peabody <[EMAIL PROTECTED]> wrote:
>> Have you invented universal algorithm for window size/position ?
>
> It works surprisingly well. I know I described it in detail in an
> earlier post, I can sum it up again if you like. It works well
> especially if you need complete resizability.
Pl
--- Brock Peabody <[EMAIL PROTECTED]>
wrote:
> That sounds good. What if we called the lower layer
> boost::gui and the
> upper layer boost::sgtl?
Agreed.
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yah
--- Brock Peabody <[EMAIL PROTECTED]>
> We can get a simple sub-language running on top of
> those few controls
> quickly enough.
I agree. I was thinking about setting up a sourcesafe
project. What do you think about the name, boost::SGTL
(Standrad GUI Template Library)?
Eugene
> 1) Since only 1 object can be passed to the iterator adaptor
> constructor, I
> had to pass a pair.
Use object generators.
> 2) Distance uses only one of the base iterators.
Use minimal distance.
> 3) iterator_category uses only 1 of the iterators.
Use most restrictive category.
Gennad
- Original Message -
From: "Philippe A. Bouchard" <[EMAIL PROTECTED]>
> Joe Gottman wrote:
> > They are considering a language solution. See this link:
> > http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/2003/n1483.pdf
>
> Wow, that is good. I like the new syntax...
>
> 0,01$: But
What is the problem adapting pair of iterators to scalar vectors to produce
an iterator with complex value type?
I am sure both old and new iterator adaptor easily allows it.
Gennadiy.
> -Original Message-
> From: Neal D. Becker [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 06, 20
Beman:
>I'd like to be sure that some Booster signs up for this beta and starts
>running the Boost regression tests against it. And then follows up with bug
>reports to Borland as needed. Any bugs fixed in the compiler before it
>ships are bugs Boosters don't have to cope with later.
To the be
I think this is a badly-chosen name. Both POSIX and Python have a
basename function which does roughly what our leaf() function does.
Python:
>>> import os.path
>>> help(os.path.basename)
Help on function basename:
basename(p)
Returns the final component of a pathname
Thanks Alisdair, but these aren't patches. Patches are made with the
diff program (preferably with the -du flags) and show the precise
lines and files of changes. Could you post one as an attachment?
Otherwise, we have to try to figure out which lines are changing.
Thanks,
Alisdair Meredith <[
"Brock Peabody" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> > On Behalf Of Bronek Kozicki:
> > Please, do NOT use MFC. Just native Win32 API as a starting point. MFC
> > is 1) not available on mingw 2) big and full of traps.
>
> If we can do Win32 I guess there isn't any point in
At 10:04 AM 8/4/2003, David Abrahams wrote:
>Pascal Bleser <[EMAIL PROTECTED]> writes:
>
>> aCC tells me that it's the same function... yuck...
>> Agreed, it's a sick compiler
>
>You've hit the nail on the head.
>
>> , but nevertheless...
>> I will try once more using STLport, but it's not about t
> Does regex address the issue of alignment and calling convention etc and
> other options (in BCB, treat enums as ints is a good one to screw up
> libraries) by wrapping the headers in push/pop option statements?
Yes:
#ifdef __BORLANDC__
# pragma option push -a8 -b -Vx -Ve -pc -w-8027
#endif
/
- Original Message -
From: "E. Gladyshev" <[EMAIL PROTECTED]>
> > > IMHO, boost needs to get rid of any possibility of
> > > this to happen. Why does boost::signal() need a
> > > DLL/LIB in the first place? Would not be just the
> > .h
> > > file enough?
> > >
> >
> > It could be put in
Beman Dawes wrote:
> What is the status of the Borland compiler as far as fixes and updates go?
> Have they announced any plans?
Borland tend not to announce anything until they are actually shipping
the product. It's an annoying habit, but as the customers have lived
with it all this time I dou
Pavel Vozenilek wrote:
> "Edward Diener" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>> Beman Dawes wrote:
>>> At 09:58 PM 8/4/2003, Alisdair Meredith wrote:
>>>
>>> >There is a problem with the Borland BCB6 compiler...
>>>
>>> What is the status of the Borland compiler as far as
Looks like a copy/paste error:
--
native_directory_string
const std::string native_file_string() const;
Returns: The contents of m_name, formatted in the system-specific
representation of a directory path.
...
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
Douglas Gregor wrote:
[...]
>> foo(1, 2, 3);
>> foo<1, 2, 3, 4, 5>();
>> foo();
>
> You can always write a forwarding 'foo' that checks the argument
> types, but
> I understand the reason you'd like this feature. My only question is
> whether it is worth the additional machinery that it would tak
>
> I might not have followed the discussion to deeply, but it does look to me
> like John is entirely right. Traits can fundamentally do one customization
> per type. That's not going to be enough if you have the same type
> representing multiple handles, as is the case with many C APIs. For
examp
28 matches
Mail list logo