General development notes (was: [Saga-devel] saga SVN commit 3373: /trunk/adaptors/aws/aws_job/)

['Andre Merzky']

Quoting [Hartmut Kaiser] (Jan 24 2009):
> 
> Actually, the job adaptor is the mess I'm referring to. Everything else is
> just a follow-up on this. And you _did_ rewrite that. The time you spent
> writing the other job adaptor easily tops what you spent so far on
> understanding Boost.Process. 

Sorry, Hartmut - you are really underestimating the time it
did cost me try to understand boost.  I am not as C++ savvy
as you are...

For example, I still have no clue how the iostreams are
supposed to work which we did for the local job adaptor, and
there you were _helping_ me, and explaining things!  It took
me several weeks, full time, back then when I tried to
implement that alone!  Literally!  And one would need to do
that for boost::process, too (I/O is another thing that was
broken there, too).

Sorry, it is simply not my priority to support the boost
project.  I know boost would be a better if everybody did (I
am not trying to kid you, I mean it), but one has to face
the reality that not everybody want's to do that, or is able
to.  Please accept it.


> It's not that you are not able to fix what's
> there. My impression is that you don't WANT to do it. I can't stand this
> 'c++/boost/you_name_it is evil' prejudice anymore. This is just a
> manifestation of the NIH (not invented here) syndrome. LMGTFY:
> http://tinyurl.com/ctfdxj. Period. 

Look, I spend some time last week to have a cleaner
integration of boost::process into saga, so that we don't
need to replicate code between adaptors.  I did that so that
it is _easier_ for us to use boost process.  Why do you
think I did that?  Come on!

It is simply broken for the things I need - so I use
something else.  The stuff I have in place is interface
compatible with the boost::process wrapper in
saga::adaptors::utils: you literally just need to swap the
namespace.  So, once boost process is fixed, I am happy to
switch back.  I would have used a tighter integration, but
hesitated to call SAGA from within the saga engine tree...
If you want it to have the same abstract interface, I can do
that, too.  Let me know.


> But I'll stop here. Go ahead rewriting stuff and messing with the existing
> code base making it less portable and deteriorating the existing
> functionality. I published it under the Boost License after all. 

Again: I did not rewrite anything over the last weeks.  I
did not break portability as far as I know: as I ultimately
use the local job adaptor beneath, it works just as well on
Windows - using boost::process there.  I did not deteriorate
functionality I hope, but _fixed_ things.  Hey, Hartmut,
whats up???

Cheers, Andre.

PS.: yes yes, I have seen the buildbot.  :-P

> 
> I don't care anymore.
> 
> Regards Hartmut
> 
> PS: Shantenu, we need to talk.
> PS2: I took that off the mailing list for obvious reasons. Please feel free
> to post it there, if you want.
> 
> 



-- 
Nothing is ever easy.