By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!Code:C:\Programs\TCC>SET _DATELONG=%%@MAKEDATE[%%@DATE[%%[_DATE]],4] C:\Programs\TCC>echo %_DATELONG TCC: (Sys) Invalid function. "%@MAKEDATE[11193,4]" C:\Programs\TCC>
So does @DATECONVERT, @AGEDATE... just curious, why @DATE, @DAY etc. wasn't removed as well?
TCC/LE was split from the TCC source tree at version 7. So it doesn't have any of the newer variable functions or a few of the more obscure ones.
TCC/LE is intended as a replacement for CMD.EXE, not for the full TCC.
> Erm, sorry? I have this variable definition for 4NT 4.0 which is
> replacing my shell for... what, ten years?
> And calling obvious supplement to the present functionality an "obscure
> one"... sorry, but i don't get it.
> I was thinking about using more recent, unicode shell that are also
> affordable for me (I don't want to make credit card for just one
> transaction), but the place at which you sliced it is just...
> unhealthy. At this rate, i could just rewrite all my scripts in bash or
> MS PoweShell, since they would be all need major rewrite with such
> abundance of castrated functionality in TCC/LE.
But you cannot realistically expect a free product to have the same feature set as the commercial version.
TCC/LE was split from the TCC source tree at version 7.
Many *NIX distributions.
So, that is still true? I was just guessing that your new version 12 was split from the TCC 12 source.
Still waiting for the first "thanks", but not holding my breath. :-)
>---Quote (Originally by rconn)---
>Still waiting for the first "thanks", but not holding my breath. :-)
>---End Quote---
>Okay, thanks for TCC/LE.
Still waiting for the first "thanks", but not holding my breath. :-)
If you like TCC/LE, you'll REALLY like the full TCC.
> Still waiting for the first "thanks", but not holding my breath. :-)
It's still true.
My inclination is to discontinue TCC/LE altogether, as it generates a continuous stream of complaints (frequently quite nasty) that (1) I didn't include the full TCC feature set, and (2) I don't provide unlimited free support. I certainly don't have any desire to continue it beyond v12.
Still waiting for the first "thanks", but not holding my breath. :-)
One reason you've got so few thanks for TCC LE might be that people suspect that it wasn't pure-hearted selflessness that made you offer it for free, but sound business calculation. Like giving a free fix to a student who later is in a position to decide to buy 100 licenses...
<WWW.4DOS.INFO>
In terms of effort vs. results for JP Software, it's pretty much been a complete waste of my time, and I have *no* incentive to take it any further. The only reason I didn't kill it in 12.0 was because of the TCMD/LE users.
However, the end result was that far more users wanted to *downgrade* to the free version (and complain bitterly that I hadn't made the full version free), than have ever wanted to upgrade from TCC/LE to the full version. (There may have been a few of the latter, but I'm unaware of them.)
> (Side Note: I would love to have an option to toggle on/off *all*
> the gui surrounding that fabulous command line interpreter.)
>
>
> However, the end result was that far more users wanted to *downgrade* to the free version (and complain bitterly that I hadn't made the full version free), than have ever wanted to upgrade from TCC/LE to the full version. (There may have been a few of the latter, but I'm unaware of them.)
> ---End Quote---
> From my viewpoint, a big thanks to Rich Conn is in order for making
> it available.
>
>
It's still true.
Still waiting for the first "thanks", but not holding my breath. :-)
Not actually true. The primary reason for TCC/LE was for existing TCC / TCMD users who wanted to install it on other machines to run simple scripts, without putting so much into it that it would cripple the full version sales.
> ---- Original Message ----
> From: mfarah
> | ...
> | There will come a time, though, that I'll complain for not having a
> | "portable" version of TCC that I can install on a pendrive (along
> | with other utilities, like Process Explorer, a decent text editor,
> | et.). ;-)
>
> Well, that's built into the full version already, and has been available for the last several versions.
> ---- Original Message ----
> From: mfarah
> | ...
> | There will come a time, though, that I'll complain for not having a
> | "portable" version of TCC that I can install on a pendrive (along
> | with other utilities, like Process Explorer, a decent text editor,
> | et.). ;-)
>
> Well, that's built into the full version already, and has been available for the last several versions.
Well, that's built into the full version already, and has been available for the last several versions.
My inclination is to discontinue TCC/LE altogether, as it generates a continuous stream of complaints (frequently quite nasty) that (1) I didn't include the full TCC feature set, and (2) I don't provide unlimited free support. I certainly don't have any desire to continue it beyond v12.
Still waiting for the first "thanks", but not holding my breath. :-)
> ---Quote (Originally by rconn)---
> My inclination is to discontinue TCC/LE altogether, as it generates a continuous stream of complaints (frequently quite nasty) that (1) I didn't include the full TCC feature set, and (2) I don't provide unlimited free support. I certainly don't have any desire to continue it beyond v12.
>
> Still waiting for the first "thanks", but not holding my breath. :-)
> ---End Quote---
> Rex, I for one want to give you a hearty _*THANK YOU*_ for making TCC/LE available to general users at no cost, and for your persistence in allowing this version to continue.
>
> I genuinely appreciate this contribution to dedicated command-line users like me. Thanks so much!!
>
> Eric Pement
>
>
>
>