Please join us, or watch the replay later.
--
Anders Ohlsson - http://blogs.codegear.com/ao/
CodeGear Developer Relations
"A golf course that does not have a pub after the 18th hole
is like an acupuncturist who does not offer needle removal."
New personal blog: http://myroadtofitness.blogspot.com/
"Anders Ohlsson (CodeGear)" <aohl...@codegear.com> wrote in
message news:46e9364a$1...@newsgroups.borland.com...
>Congrats to Alisdair and CodeGear.
>A great guy to do this job.
>You've got a lot of work ahead of you and we'll miss you at
>the ACCU - unless of course CodeGear will be there next
>year?
Hmm, now that'd be a good idea. An extremely good idea. After all, we
had Microsoft and Google (among others) with us this year, and we used
to include a specific Borland SIG many years ago.
Alan Bellingham
--
Team Browns
ACCU Conference 2008: 2-5 April 2008 - Oxford (probably), UK
Congratulations to Alisdair, and to CodeGear. I only wish it hadn't
taken this long... <G>
David Erbas-White
"David Erbas-White" <der...@arachneering.com> wrote in
message news:46e952ac$1...@newsgroups.borland.com...
-m
"Pete Fraser" <pete.nospam....@frasersoft.nospam.net> wrote in
message news:46e953b3$1...@newsgroups.borland.com...
I'd love to be able to compile and build the Visual C++ compatible open
source libraries that are out there (libpar is a good example of one that
doesn't compoile in C++Builder). I hope he makes that a priority. I'd buy a
new copy of C++ Builder, or CodeGear Dev Dtudio if that was the case.
> Alisdair Meredith - Product Manager C++
I'm very excited to be working with Alisdair. His involvement with
CodeGear is sure to make our C++ products better.
--
-David Dean
CodeGear C++ QA Engineer
<http://blogs.codegear.com/ddean/>
I so agree with you on this. If CodeGear would adopt microsoft format of
lib, obj and debug files things would be so much easier for everybody.
For .DLL's you have import.lib, it works.
Saludos
Sebastian
> I'd love to be able to compile and build the Visual C++ compatible open
> source libraries that are out there (libpar is a good example of one that
> doesn't compoile in C++Builder). I hope he makes that a priority. I'd buy a
> new copy of C++ Builder, or CodeGear Dev Dtudio if that was the case.
>
>
I have no major problems compiling a *lot* of VC++-compatible source.
I've not tried libpar in particular. Issues that I do encounter usually
are VC++ accepting non-conforming code or VC++ -specific keywords/features.
.a
> Congrats to Alisdair and CodeGear.
> A great guy to do this job.
> You've got a lot of work ahead of you and we'll miss you at the ACCU
> - unless of course CodeGear will be there next year? Pete
Thanks Pete.
I'd hate to miss everyone at ACCU again next year too, we'll see if I
can bend enough rules to make it there again!
Yes we certainly have a busy time ahead of us, and an eager team to do
the work. Management have renewed investment in our tools, so now it
is up to me to deliver the fantastic tool we always knew C++Builder
should grow up to be!
Did I say how much I love my new job yet? <g>
--
Alisdair Meredith
C++Builder Product Manager - CodeGear
> Hmm, now that'd be a good idea. An extremely good idea. After all, we
> had Microsoft and Google (among others) with us this year, and we used
> to include a specific Borland SIG many years ago.
Interesting, I didn't know about the SIGs. I always had a soft spot
reviving traditions after all!
> Excellent news! I think we will see good stuff on the compiler front.
Thanks for the vote of confidence <g>
I hope you will actually be seeing a lot of good stuff though, and not
just on the compiler. I hope to have a teaser for our plans out soon,
so you can see the direction for the whole product, although Nick
Hodges has already warned me of the perils of promising road maps ;?)
> I so agree with you on this. If CodeGear would adopt microsoft format
> of lib, obj and debug files things would be so much easier for
> everybody.
In the ideal world I would love all compilers to easily share compiled
libraries. I'm not sure it is practical when our ABI is also
constrained by Delphi/VCL compatibility, which is not something
Microsoft need to consider. Once you throw in different exception
handling strategies, calling conventions, language extensions (and new
features as 0x is implemented) etc. the task becomes quite significant
- and that is assuming Microsoft even license or document their ABI.
I won't say we'll never do something along these lines (never say
never!) but it is not high on my prioirity list for the next 12 months.
> Congratulations to Alisdair, and to CodeGear. I only wish it hadn't
> taken this long... <G>
Thanks <G>
As a customer I would agree with you, we have needed some focus and
direction in the C++ Tools for a while.
Personally I'll be selfish and say I'm glad it took this long, as it
means I was available for the job!
> I'd love to be able to compile and build the Visual C++ compatible
> open source libraries that are out there (libpar is a good example of
> one that doesn't compoile in C++Builder). I hope he makes that a
> priority. I'd buy a new copy of C++ Builder, or CodeGear Dev Dtudio
> if that was the case.
If there are specific libraries you would like to see supported, please
let me know. Top of my list initially for C++ are Boost and ACE/TAO.
Another area where 'field reports' help is knowing where there are 3rd
party Delphi components that aren't compatible with C++Builder.
Thanks again
John Grabner
(Long time ACCU member)
Ah man, awesome dude. C++ Builder has some good times ahead. But, do it
with compiler fixes instead of compiler workarounds.
Well, from the outside it does sound as a perfect match both ways :-)
Congratulations, Alisdair. You've certainly come a long way since we
first met on these newsgroups.
Cheers,
Nicola
--
Nicola Musatti
Team Browns
Home: http://nicola.musatti.googlepages.com/home
Blog: http://wthwdik.wordpress.com/
Yep, congrats from me, too. CG hiring you sounds
like they're /really/ going into the right
direction.
> I hope you will actually be seeing a lot of good stuff though, and not
> just on the compiler. I hope to have a teaser for our plans out soon,
> so you can see the direction for the whole product, although Nick
> Hodges has already warned me of the perils of promising road maps ;?)
Road maps aren't perilious at all, actually. Just
not sticking to them gets you into trouble. :)
Schobi
--
Spam...@gmx.de is never read
I'm HSchober at gmx dot de
"A patched buffer overflow doesn't mean that there's one less way attackers
can get into your system; it means that your design process was so lousy
that it permitted buffer overflows, and there are probably thousands more
lurking in your code."
Bruce Schneier
Ah, but that should not be a matter of bending the rules! I've been
meaning to suggest this for a couple of years, but until now I didn't
know who to address. I don't think there currently is a better focused
event for C++ and CodeGear should seriously consider sending not only
their brand new product manager but also someone from the development
team. And not just to preside the annual BCB dinner!
>http://borland.interwise.com/borland/iSeminar/QM6933/
>
>Please join us, or watch the replay later.
Congratulations Alisdair! High Hopes!
--
-Brion
There's no such thing as 'one, true way;'
- Mercedes Lackey
Google for "libpar". It's a freeware library for decoding/combining PAR
files. I've been wanting to add automatic decoding/combining of PAR files to
my newsreader, but I'd have to put it in a DLL because it only compiles in
VC++, not C++ Builder. Ideally, I would be able to compile libpar to an OBJ
file that Delphi could link directly with. Make that a possibility and I
would be a very happy camper.
Congratulations to Alisdair, and may we all learn to spell your name
correctly.
- Leo
"Leo Siefert" <lIHATESP...@senate.michigan.gov> wrote
in message
news:n39le39j4l68qv63l...@4ax.com...
> Google for "libpar". It's a freeware library for decoding/combining PAR
I did, but there doesn't seem to be a zip/tar or anything - just mail
list posts and libpar-perl stuff.
Then I discovered Alisdair had become C++ Project Manager.
Wow! I am now highly confident that I have made the right decision to
continue with C++Builder...
Congrats, Alisdair... I'm particularly looking forward to better Boost
support.
Andrew
Google suggested looking for libpar2, and brought up this link
http://sourceforge.net/project/showfiles.php?group_id=30568&package_id=171019
libpar2-0.2.tar.gz Mirror 401700 3977 Platform-Independent Source .gz
There are also other orig.tar.gz links in the index-of mirror links in Google results.
> http://sourceforge.net/project/showfiles.php?group_id=30568&package_id=171019
>
Downloaded that, thanks. It requires libsigc++, so I had to get that too.
BCB choked on
template <class T_functor>
struct adaptor_functor : public adaptor_base
{
template <class T_arg1=void,class T_arg2=void,class T_arg3=void,class
T_arg4=void,class T_arg5=void,class T_arg6=void,class T_arg7=void>
struct deduce_result_type
{ typedef typename sigc::deduce_result_type<T_functor,
T_arg1,T_arg2,T_arg3,T_arg4,T_arg5,T_arg6,T_arg7>::type type; };
[BCC32 Error] adaptor_trait.h(61): E2270 > expected
pointing to T_arg1=void.
[BCC32 Error] adaptor_trait.h(61): E2270 > expected
[BCC32 Error] adaptor_trait.h(63): E2321 Declaration does not specify a
tag or an identifier
[BCC32 Error] adaptor_trait.h(251): E2316 'operator
adaptor_functor<T_functor>::()() const' is not a member of
'adaptor_functor<T_functor>'
[BCC32 Error] signal.h(430): E2404 Dependent type qualifier 'nil' has no
member type named 'result_type'
[BCC32 Error] signal.h(448): E2404 Dependent type qualifier 'nil' has no
member type named 'result_type'
[BCC32 Error] signal.h(427): F1004 Internal compiler error at 0x58e747f
with base 0x5860000
Twice now on a curry night out with the big man + others, he's listened
to my winges about BCB and twice he has said he would pop round to my
office and listen to my BCB complaints when I was less intoxicated. Did
he turn up? No! I hope this doesn't set a precedent of broken promises.
Well done mate, they took their time.
Dave
>his parents apparently mixed them up and made a third!
But that's his name now. As long as he spells it that way I will too.
- Leo
$ drink < bottle; opener
bottle: cannot open
opener: not found
> Did I say how much I love my new job yet? <g>
I just sorted by poster name and see this is the first post you've written in this
group with the [CodeGear] in your From.
Well, congrats to both you and CodeGear. I have always appreciated your detailed
knowledge of the C++ standard and its evolution. I'm glad to see someone so dedicated
to C++ working for CodeGear on C++.
Alisdair most definitely is, but the others on the C++ team are very
dedicated to C++ as well, AFAIK.
--
Rudy Velthuis [TeamB]
"If FORTRAN has been called an infantile disorder, then PL/I must
be classified as a fatal disease." -- Edsger Dijkstra
[snip]
>If there are specific libraries you would like to see supported, please
>let me know. Top of my list initially for C++ are Boost and ACE/TAO.
[snip]
I'm sure that many EE will be glad to see the SystemC library
compiling with Codegear tools.
Have a look at http://www.systemc.org/
Regards
Giuliano