[jamming] Join modifier

[John Waugh]

Well, nothing that hasn't been said before (:
Scons has its benefits, like using hashes rather than timestamps and having
the full power of python, etc.
But it really is quite slow. We don't do that much TDD or anything, but the
psycological annoyance of waiting for scons to "think" for 15 seconds before
actually building anything is significant.
Also, scons' "makefiles" are python, which sounds nice but gets to be overly
verbose.
We actually have a system built on top of scons to make the makefiles
simpler, which works ok.
But then only one or two people actually understand that layer enough to
make changes to it, which becomes a bottleneck. So the complexity of scons
becomes an issue.

Not that we'll ditch scons any time soon (or ever), but for my personal
projects at home, Jam appeals to me most.

-John

On 3/3/06, david turner <dturner at nds.com> wrote:
>
> John Waugh a écrit :
> > I'd be interested
> > We use scons at work and it's so painful (:
> >
> Really, could you care to elaborate what you find painful with it ?
> That's not do diss Scons, I'm just really curious about *anything*
> related to software construction :-)
> > Is the join bug mentioned here:
> > http://maillist.perforce.com/pipermail/jamming/2004-October/002456.html
> > <http://maillist.perforce.com/pipermail/jamming/2004-October/002456.html
> >
> > fixed in that version, by any chance ?
> > Easy to work around, in any case.
> >
> I think so. Let me a few days to prepare the release.
>
> Regards,
>
> - David
> > much thanks if you do a release
> > -John
> >
> > On 3/3/06, *david turner * <dturner at nds.com <mailto:dturner at nds.com>>
> > wrote:
> >
> >     John Waugh a écrit :
> >     > Well I figured it out. Classic jam 2.5 has the :J modifier, but
> >     FTJam
> >     > does not :( I guess I'll use classic jam - it seems more recently
> >     > updated anyway.
> >     >
> >     If someone's interested, I can make a release of FTJam 2.5.3; as the
> >     name suggests, it has all the features
> >     of Classic Jam 2.5 plus a few extras (e.g. a SharedLibrary rule to
> >     build
> >     DLLs and Unix shared objects)
> >
> >     Regards,
> >
> >     - David Turner
> >     - FTJam maintainer
> >
> >     > -John
> >     >
> >     > On 3/2/06, * John Waugh* <john.waugh at gmail.com
> >     <mailto:john.waugh at gmail.com>
> >     > <mailto:john.waugh at gmail.com <mailto:john.waugh at gmail.com>>>
> wrote:
> >     >
> >     >     Just as a follow-up, I'm using FTJam, on WinXP.
> >     >     Still no luck using :J=
> >     >
> >     >
> >     >     On 3/1/06, *John Waugh* <john.waugh at gmail.com
> >     <mailto:john.waugh at gmail.com>
> >     >     <mailto:john.waugh at gmail.com <mailto:john.waugh at gmail.com>>>
> >     wrote:
> >     >
> >     >         I can't seem to get the join (:J) modifier to work
> >     >         I haven't been able to find much info in the mailing
> >     archives
> >     >         or elsewhere ):
> >     >
> >     >         Here is example code:
> >     >
> >     >         --- start code ---
> >     >
> >     >         local test = aaa ;
> >     >         test += bbb ;
> >     >         test += ccc ;
> >     >         ECHO $(test) ;      # prints: aaa bbb ccc
> >     >         ECHO $(test:J=x) ;  # prints the same as above !
> >     >
> >     >         --- end code ---
> >     >
> >     >         Am I missing something?
> >     >         I thought the last line above would print "aaaxbbbxccc"
> >     >
> >     >         What's the magic incantation?
> >     >
> >     >         Thanks
> >     >         -John
> >     >
> >     >
> >     >
> >     >
> >
> ------------------------------------------------------------------------
> >     >
> >     > _______________________________________________
> >     > jamming mailing list  -  jamming at perforce.com
> >     <mailto:jamming at perforce.com>
> >     > http://maillist.perforce.com/mailman/listinfo/jamming
> >     >
> >
> >
> ***********************************************************************************
> >     Information contained in this email message is confidential and
> >     may be privileged, and is intended only for use of the individual
> >     or entity named above. If the reader of this message is not the
> >     intended recipient, or the employee or agent responsible to
> >     deliver it to the intended recipient, you are hereby notified that
> >     any dissemination, distribution or copying of this communication
> >     is strictly prohibited. If you have received this communication in
> >     error, please immediately notify the postmaster at nds.com
> >     <mailto:postmaster at nds.com> and destroy the original message.
> >
> ***********************************************************************************
> >
> >
>
>
> ***********************************************************************************
> Information contained in this email message is confidential and may be
> privileged, and is intended only for use of the individual or entity named
> above. If the reader of this message is not the intended recipient, or the
> employee or agent responsible to deliver it to the intended recipient, you
> are hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, please immediately notify the postmaster at nds.comand destroy the original message.
>
> ***********************************************************************************
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://maillist.perforce.com/pipermail/jamming/attachments/20060303/aba38dd4/attachment.html