Re: CONS specs update?

This is a multipart message in MIME format.
--===============0599417621==
Content-Type: multipart/alternative;
	boundary="=_alternative 006E58D488257235_="

This is a multipart message in MIME format.
--=_alternative 006E58D488257235_=
Content-Type: text/plain; charset="US-ASCII"

Glad to see there is at least someone still out there.  Here at Philips 
Medical the latest Cons 2.3.0 is and has been in heavy use now for years 
and has been very helpful.  There is a push to go to SCons, but the cost 
of the new language, Python, is prohibitive for us in the that all of our 
infrastructure is in Perl.  We are converting a lot of infrastructure to 
C# and that is a big enough job, so we are not willing to take on Python 
and add to the confusion.  I also do not see C# as being able to do what 
Perl can do, such as eval(), so I see Perl sticking around for a very long 
time when it comes to builds.

As for Perl OO, it is very easy, just keep it simple.  I hate to say it, 
but Cons did it the hard way and I would like to see a rewrite throwing 
out most of the functionality and keep it just a simple dependency scan 
and build engine with some better plug and play build specific features. 
It should be totally version control dumb.  One of these days I'm going to 
do it!! 
I cannot say enough about how great Cons is, even if I hate going into the 
source, it performs very fast, beyond my expectations and very accurately. 
 One big draw is the SCons multiple process building, and pcons attempted 
that, I do not know how well, but if I rewrite Cons it will have that for 
sure.  Oh, and I should mention that we are using Cons with Visual Studio 
on a Windows environment, using ClearCase for version control.  Our source 
is several million lines of code using multiple brands of compilers. 
Definitely a better need for plug-in modules for different types of tools, 
as the scanning requirements are all different.



---
Rick Croote
Software Engineer
Environment and Tools Team
Philips Medical Systems
Bothell, WA
[email protected]
Phone: 425-487-7834









Pierre THIERRY <[email protected]> 
Sent by:
[email protected]
2006-11-28 06:07 PM

To
[email protected]
cc

Subject
Re: CONS specs update?
Classification







Scribit Pierre THIERRY dies 27/10/2004 hora 03:05:
> > I'd hate to see yet another effort to revive Cons drop flat. 
> So do I. Sorry for the very long silence, I didn't find time to sit on
> a table with a notepad, and think about how everything the discussed
> about could fit together. I think I was lacking inspiration to do the
> synthesis of that...

Well, sorry for the next long silence. I must tell that I finally won't
try to make cons evolve. Mainly because I see pretty clearly in my head
how to do much of the work in an object-oriented way, and because I
never really understood Perl's object oriented mechanisms.

I still plan to develop a build management tool with the design I
sketched previously, but probably in Common Lisp. When it works, I'll
probably write the Construct module anyway, so it should be possible to
use existing Construct files with that tool, and use Perl around it's
Lisp core.

If I have any success in my attempt, I'll post some note here.

Alternatively,
Pierre
-- 
[email protected]
OpenPGP 0xD9D50D8A
[attachment "signature.asc" deleted by Rick Croote/ATL-BTL/MS/PHILIPS] 
_______________________________________________
[email protected]
http://lists.gnu.org/mailman/listinfo/cons-discuss
Cons URL: http://www.dsmit.com/cons/

--=_alternative 006E58D488257235_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Glad to see there is at least someone
still out there. &nbsp;Here at Philips Medical the latest Cons 2.3.0 is
and has been in heavy use now for years and has been very helpful. &nbsp;There
is a push to go to SCons, but the cost of the new language, Python, is
prohibitive for us in the that all of our infrastructure is in Perl. &nbsp;We
are converting a lot of infrastructure to C# and that is a big enough job,
so we are not willing to take on Python and add to the confusion. &nbsp;I
also do not see C# as being able to do what Perl can do, such as eval(),
so I see Perl sticking around for a very long time when it comes to builds.</font>
<br>
<br><font size=2 face="sans-serif">As for Perl OO, it is very easy, just
keep it simple. &nbsp;I hate to say it, but Cons did it the hard way and
I would like to see a rewrite throwing out most of the functionality and
keep it just a simple dependency scan and build engine with some better
plug and play build specific features. &nbsp;It should be totally version
control dumb. &nbsp;One of these days I'm going to do it!! &nbsp;</font>
<br><font size=2 face="sans-serif">I cannot say enough about how great
Cons is, even if I hate going into the source, it performs very fast, beyond
my expectations and very accurately. &nbsp;One big draw is the SCons multiple
process building, and pcons attempted that, I do not know how well, but
if I rewrite Cons it will have that for sure. &nbsp;Oh, and I should mention
that we are using Cons with Visual Studio on a Windows environment, using
ClearCase for version control. &nbsp;Our source is several million lines
of code using multiple brands of compilers. &nbsp;Definitely a better need
for plug-in modules for different types of tools, as the scanning requirements
are all different.</font>
<br>
<br>
<br><font size=2 face="sans-serif"><br>
---<br>
Rick Croote<br>
Software Engineer<br>
Environment and Tools Team<br>
Philips Medical Systems<br>
Bothell, WA<br>
[email protected]<br>
Phone: 425-487-7834<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=33%>
<br>
<br>
<br>
<br>
<br><font size=1 face="sans-serif"><b>Pierre THIERRY &lt;[email protected]&gt;</b>
</font>
<p><font size=1 face="sans-serif">Sent by:</font>
<br><font size=1 face="sans-serif">[email protected]</font>
<p><font size=1 face="sans-serif">2006-11-28 06:07 PM</font>
<td width=66%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">[email protected]</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: CONS specs update?</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Classification</font></div>
<td></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<div align=right>
<br></div></table>
<br>
<br>
<br><font size=2><tt>Scribit Pierre THIERRY dies 27/10/2004 hora 03:05:<br>
&gt; &gt; I'd hate to see yet another effort to revive Cons drop flat.
<br>
&gt; So do I. Sorry for the very long silence, I didn't find time to sit
on<br>
&gt; a table with a notepad, and think about how everything the discussed<br>
&gt; about could fit together. I think I was lacking inspiration to do
the<br>
&gt; synthesis of that...<br>
<br>
Well, sorry for the next long silence. I must tell that I finally won't<br>
try to make cons evolve. Mainly because I see pretty clearly in my head<br>
how to do much of the work in an object-oriented way, and because I<br>
never really understood Perl's object oriented mechanisms.<br>
<br>
I still plan to develop a build management tool with the design I<br>
sketched previously, but probably in Common Lisp. When it works, I'll<br>
probably write the Construct module anyway, so it should be possible to<br>
use existing Construct files with that tool, and use Perl around it's<br>
Lisp core.<br>
<br>
If I have any success in my attempt, I'll post some note here.<br>
<br>
Alternatively,<br>
Pierre<br>
-- <br>
[email protected]<br>
OpenPGP 0xD9D50D8A<br>
[attachment &quot;signature.asc&quot; deleted by Rick Croote/ATL-BTL/MS/PHILIPS]
_______________________________________________<br>
[email protected]<br>
http://lists.gnu.org/mailman/listinfo/cons-discuss<br>
Cons URL: http://www.dsmit.com/cons/</tt></font>
<br>
--=_alternative 006E58D488257235_=--



--===============0599417621==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
[email protected]
http://lists.gnu.org/mailman/listinfo/cons-discuss
Cons URL: http://www.dsmit.com/cons/
--===============0599417621==--