Home > Archive > Tcl > November 2006 > proc needs to always calculate the following Saturday but fails Nov - Apr
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
proc needs to always calculate the following Saturday but fails Nov - Apr
|
|
| comp.lang.tcl 2006-11-24, 7:02 pm |
| [TCL]
proc CALCULATE_XML_EXPDATE {triviaAttrs triviaAttrCount
hasPassedTrivia} {
set midnightNow [clock scan [clock format [clock scan now] -format
"%m/%d/%Y"]]
set expDate [lindex $triviaAttrs [expr {[lsearch $triviaAttrs
{expDate}] + 1 + ($triviaAttrCount * (([llength $triviaAttrs] /
$triviaAttrCount) - 1))}]]
set expDate [clock scan [clock format $expDate -format "%m/%d/%Y"]];
# ROUND FOUND EXPDATE IN XML GROUP TO MIDNIGHT
if {$hasPassedTrivia} {
incr expDate [expr {7 * 86400}]
while {$expDate <= $midnightNow} {incr expDate [expr {7 * 86400}]; #
INCREASE BY ONE WEEK}
}
return $expDate
}
[/TCL]
This proc is supposed to calculate the immediate following Saturday of
the w , however, between November and April it gives me Friday; if I
up the date by 86400, it then gives me Sunday from April until
November.
I've tried for years to get this to be accurate and fail every time;
can someone please help me with this? I need to always get the next
immediate following Saturday.
Thanx
Phil
| |
| comp.lang.tcl 2006-11-24, 7:02 pm |
|
Kevin Kenny wrote:
> comp.lang.tcl wrote:
>
> Uhm, does [clock scan Saturday] do what you want? Or if you need
> the next Saturday after a given date,
>
> [clock scan Saturday -base [clock scan $date]]
>
> I'm not quite following the Tcl code that you posted, but suspect
> that you're trying to reinvent one of the idioms above.
>
> --
> 73 de ke9tv/2, Kevin
Problem is that it has to also be the next Saturday from the last
previous value of $expDate, so that if the very last value in the XML
row points to the date being 11/25/2006, the next one must be
12/2/2006, however, if the last one is 12/2/2006, the next one after
that must be 12/9/2006 and so on and so on
Phil
| |
| Glenn Jackman 2006-11-24, 7:02 pm |
| At 2006-11-24 12:29PM, "comp.lang.tcl" wrote:
> [TCL]
> proc CALCULATE_XML_EXPDATE {triviaAttrs triviaAttrCount
> hasPassedTrivia} {
> set midnightNow [clock scan [clock format [clock scan now] -format
> "%m/%d/%Y"]]
Whoa! Too much work.
set midnightNow [clock scan "00:00"]
> set expDate [lindex $triviaAttrs [expr {[lsearch $triviaAttrs
> {expDate}] + 1 + ($triviaAttrCount * (([llength $triviaAttrs] /
> $triviaAttrCount) - 1))}]]
> set expDate [clock scan [clock format $expDate -format "%m/%d/%Y"]];
And then:
set saturday [clock scan Saturday -base $expDate]
I know of no other language that makes date arithmetic this easy.
> # ROUND FOUND EXPDATE IN XML GROUP TO MIDNIGHT
> if {$hasPassedTrivia} {
> incr expDate [expr {7 * 86400}]
> while {$expDate <= $midnightNow} {incr expDate [expr {7 * 86400}]; #
> INCREASE BY ONE WEEK}
Never assume a day equals 86400 seconds. Always use the clock command
to manipulate time. If you want a time 7 days from another time:
set expDate [clock scan "7 days" -base $expDate]
> }
> return $expDate
> }
>
> [/TCL]
>
> This proc is supposed to calculate the immediate following Saturday of
> the w, however, between November and April it gives me Friday; if I
> up the date by 86400, it then gives me Sunday from April until
> November.
Doesn't that sound suspiciously like you're getting bit by
standard time vs. daylight savings time? Some days have more/less than
86400 seconds.
--
Glenn Jackman
Ulterior Designer
| |
| comp.lang.tcl 2006-11-24, 7:02 pm |
|
Glenn Jackman wrote:
> At 2006-11-24 12:29PM, "comp.lang.tcl" wrote:
>
> Whoa! Too much work.
> set midnightNow [clock scan "00:00"]
You've got to be kidding, it can't be that easy! :(
>
>
> And then:
> set saturday [clock scan Saturday -base $expDate]
>
> I know of no other language that makes date arithmetic this easy.
Except that this will give me a fixed Saturday date. I want the
immediate following Saturday from the very last date found in the last
XML row in the XML file, which could be 11/25/2006 or 12/2/2006 or
12/9/2006 or...
>
>
>
> Never assume a day equals 86400 seconds. Always use the clock command
> to manipulate time. If you want a time 7 days from another time:
> set expDate [clock scan "7 days" -base $expDate]
I can't see how this will work when I need to find the very next
following Saturday after the very last date in the last XML row with
the expDate attribute. Sorry, your code is easy to understand but I
have no idea how to implement it.
Phil
>
>
> Doesn't that sound suspiciously like you're getting bit by
> standard time vs. daylight savings time? Some days have more/less than
> 86400 seconds.
>
>
> --
> Glenn Jackman
> Ulterior Designer
| |
| comp.lang.tcl 2006-11-24, 7:02 pm |
|
Bryan Oakley wrote:
> comp.lang.tcl wrote:
>
> Using a -base of your date + 1 day seems to do the trick, or am I
> missing something?
>
> % clock format [clock scan Saturday -base [clock scan "11/23/2006 + 1 day"]]
> Sat Nov 25 00:00:00 CST 2006
> % clock format [clock scan Saturday -base [clock scan "11/24/2006 + 1 day"]]
> Sat Nov 25 00:00:00 CST 2006
> % clock format [clock scan Saturday -base [clock scan "11/25/2006 + 1 day"]]
> Sat Dec 02 00:00:00 CST 2006
Um, ok sorry to sound stupid but I will anyway..
My timestamp in expDate attribute will be something like "1164949026",
how do I use that?
Phil
> %
| |
| comp.lang.tcl 2006-11-26, 7:04 pm |
|
Gerald W. Lester wrote:
> comp.lang.tcl wrote:
>
> clock format $expDate
>
> you may want to use the -format option to clock format to specify the way
> you want the date/time to look.
>
>
Ok I'm really sorry, but I cannot follow what you guys are telling me
to do, I'm completely lost. Here is my original proc:
proc CALCULATE_XML_EXPDATE {triviaAttrs triviaAttrCount
hasPassedTrivia} {
set midnightNow [clock scan [clock format [clock scan now] -format
"%m/%d/%Y"]]
set expDate [lindex $triviaAttrs [expr {[lsearch $triviaAttrs
{expDate}] + 1 + ($triviaAttrCount * (([llength $triviaAttrs] /
$triviaAttrCount) - 1))}]]
set expDate [clock scan [clock format $expDate -format "%m/%d/%Y"]];
# ROUND FOUND EXPDATE IN XML GROUP TO MIDNIGHT
if {$hasPassedTrivia} {
incr expDate [expr {7 * 86400}]
while {$expDate <= $midnightNow} {incr expDate [expr {7 * 86400}]; #
INCREASE BY ONE WEEK}
}
return $expDate
}
I need to change the proc so that I ensure that I always get the next
Saturday following the value in the very last expDate="[0-9]" in the
XML row in trivia.xml. What you guys are telling me to do is great,
but for me with ADD you're going all over the map and trying to get me
to drink from a firehose.
Sorry, guys, but I still need help
Phil
> --
> +--------------------------------+---------------------------------------+
> | Gerald W. Lester |
> |"The man who fights for his ideals is the man who is alive." - Cervantes|
> +------------------------------------------------------------------------+
| |
| comp.lang.tcl 2006-11-26, 7:04 pm |
|
Bryan Oakley wrote:
> comp.lang.tcl wrote:
>
> Using a -base of your date + 1 day seems to do the trick, or am I
> missing something?
>
> % clock format [clock scan Saturday -base [clock scan "11/23/2006 + 1 day"]]
> Sat Nov 25 00:00:00 CST 2006
> % clock format [clock scan Saturday -base [clock scan "11/24/2006 + 1 day"]]
> Sat Nov 25 00:00:00 CST 2006
> % clock format [clock scan Saturday -base [clock scan "11/25/2006 + 1 day"]]
> Sat Dec 02 00:00:00 CST 2006
> %
I'm sorry I am not getting it at all
puts [clock format [clock scan Saturday -base [clock scan "1165035600 +
1 day"]]]
unable to convert date-time string "1165035600 + 1 day"
% puts [clock format [clock scan Saturday -base [clock scan "[clock
scan "1165035600" -format "%m/%d/%Y"] + 1day"]]]
bad switch "-format": must be -base or -gmt
I at this point don't know when or if I'll get it because I can't seem
to process how to do it.
Phil
| |
| Glenn Jackman 2006-11-26, 7:04 pm |
| At 2006-11-26 03:44PM, "comp.lang.tcl" wrote:
>
> Bryan Oakley wrote:
>
>
> I'm sorry I am not getting it at all
>
> puts [clock format [clock scan Saturday -base [clock scan "1165035600 +
> 1 day"]]]
> unable to convert date-time string "1165035600 + 1 day"
> % puts [clock format [clock scan Saturday -base [clock scan "[clock
> scan "1165035600" -format "%m/%d/%Y"] + 1day"]]]
> bad switch "-format": must be -base or -gmt
>
> I at this point don't know when or if I'll get it because I can't seem
> to process how to do it.
When you are working with dates in Tcl, there are two kinds of time
values:
1. an epoch time (the number of seconds since jan 1, 1970, which looks
like a 10-digit number), or
2. a datetime string (such as "11/25/2006" or "tomorrow", etc)
When you have an epoch time, that's the value you use in [clock
format ...] or the "-base" value in [clock scan ...]
When you have a datetime string, that's what you use in [clock scan ...]
You can't treat an epoch time as a datetime string, which is what you're
trying to do above. Also, you don't need to chain [clock format]s and
[clock scan]s together.
So:
set expdate 1165035600
set tomorrow_epoch [clock scan tomorrow -base $expdate]
# the above command means: when the time was $expdate, what will
# the time be tomorrow?
set next_saturday_epoch [clock scan saturday -base $tomorrow_epoch]
puts "starting time: [clock format $expdate]"
puts "the next day: [clock format $tomorrow_epoch]"
puts "the following saturday : [clock format $next_saturday_epoch]"
--
Glenn Jackman
Ulterior Designer
| |
| slebetman@yahoo.com 2006-11-26, 10:01 pm |
| comp.lang.tcl wrote:
> Glenn Jackman wrote:
>
> Except that this will give me a fixed Saturday date. I want the
> immediate following Saturday from the very last date found in the last
> XML row in the XML file, which could be 11/25/2006 or 12/2/2006 or
> 12/9/2006 or...
What do you mena "fixed Saturday"? The code works as advertised for me.
Assuming your expDate is already in epoch time:
set saturday [clock scan Saturday -base $expDate]
should be ok. Oh, except that it doesn't handle if the date is already
a Saturday. Then Kevin Kenny's version should work:
set expTimeTomorrow [clock scan tomorrow -base $expDate]
set saturday [clock scan Saturday -base $expTimeTomorrow]
Test it out on a few dates you gave as example:
foreach day {11/25/2006 12/2/2006 12/9/2006} {
# convert date to epoch time in expDate:
set expDate [clock scan $day]
# increment by 1 day:
set expTimeTomorrow [clock scan tomorrow -base $expDate]
# ask Tcl for saturday's time:
set saturday [clock scan Saturday -base $expTimeTomorrow]
puts [clock format $saturday -format "%m/%d/%Y"]
}
| |
| slebetman@yahoo.com 2006-11-27, 4:10 am |
| slebetman@yahoo.com wrote:
> foreach day {11/25/2006 12/2/2006 12/9/2006} {
>
> # convert date to epoch time in expDate:
> set expDate [clock scan $day]
>
> # increment by 1 day:
> set expTimeTomorrow [clock scan tomorrow -base $expDate]
>
> # ask Tcl for saturday's time:
> set saturday [clock scan Saturday -base $expTimeTomorrow]
>
> puts [clock format $saturday -format "%m/%d/%Y"]
> }
On second thought, Uwe's answer is much more elegant, straight-forward
and human readable. I forgot that Tcl's clock command understands
"next":
set saturday [clock scan {next Saturday} -base $expDate]
| |
| comp.lang.tcl 2006-11-27, 4:10 am |
|
Glenn Jackman wrote:
> At 2006-11-26 03:44PM, "comp.lang.tcl" wrote:
>
> When you are working with dates in Tcl, there are two kinds of time
> values:
> 1. an epoch time (the number of seconds since jan 1, 1970, which looks
> like a 10-digit number), or
> 2. a datetime string (such as "11/25/2006" or "tomorrow", etc)
>
> When you have an epoch time, that's the value you use in [clock
> format ...] or the "-base" value in [clock scan ...]
>
> When you have a datetime string, that's what you use in [clock scan ...]
>
> You can't treat an epoch time as a datetime string, which is what you're
> trying to do above. Also, you don't need to chain [clock format]s and
> [clock scan]s together.
>
> So:
> set expdate 1165035600
> set tomorrow_epoch [clock scan tomorrow -base $expdate]
> # the above command means: when the time was $expdate, what will
> # the time be tomorrow?
>
> set next_saturday_epoch [clock scan saturday -base $tomorrow_epoch]
>
> puts "starting time: [clock format $expdate]"
> puts "the next day: [clock format $tomorrow_epoch]"
> puts "the following saturday : [clock format $next_saturday_epoch]"
>
ok, now, this is where it gets a bit bad, but I just don't know how to
do this
How do I calculate 12:00AM Saturday immediately after the avlue
116035600
I'm sorry I just don't know this stuff
Phil
> --
> Glenn Jackman
> Ulterior Designer
| |
| comp.lang.tcl 2006-11-27, 4:10 am |
|
comp.lang.tcl wrote:
> Glenn Jackman wrote:
>
> ok, now, this is where it gets a bit bad, but I just don't know how to
> do this
>
> How do I calculate 12:00AM Saturday immediately after the avlue
> 116035600
>
> I'm sorry I just don't know this stuff
** UPDATE**
I took a wild, wild guess and came up with this:
[TCL]
proc CALCULATE_XML_EXPDATE {{triviaAttrs {}} {triviaAttrCount 0}
{hasPassedTrivia 1}} {
if {[string length [info procs {IS_LIST}]] == 0} then source
../tcl_string_tools.tcl
if {![info exists triviaAttrs] || ![IS_LIST $triviaAttrs] || [llength
$triviaAttrs] == 0} then \
return [clock scan {next Saturday} -base [clock scan now]]; # RETURN
THE NEXT SATURDAY SINCE NO expDate COULD BE FOUND
# SINCE $triviaAttrs HAS TO BE AN EXISTING LIST WITH llength > 0 TO
GET HERE, JUST MAKE SURE $triviaAttrCount REFLECTS THAT
if {[expr {$triviaAttrCount == 0}]} then $triviaAttrCount = [expr
{[XML_GET_ELEMENT_ATTR_COUNT $triviaAttrs]}]
# GET THE LAST expDate ATTRIBUTE VALUE IN $triviaAttrs
set expDate [lindex $triviaAttrs [expr {[lsearch $triviaAttrs
{expDate}] + 1 + ($triviaAttrCount * (([llength $triviaAttrs] /
$triviaAttrCount) - 1))}]]
# WILL RETURN THE FOLLOWING SATURDAY AFTER $expDate ROUNDED
AUTOMATICALLY TO 00:00
return [clock scan {next Saturday} -base $expDate]
}
[/TCL]
Sorry I can't test it. I have no idea how to get this to work in
Windows but it seems to work in UNIX. Help and review appreciated
Phil
[color=darkred]
>
> Phil
>
| |
| comp.lang.tcl 2006-11-27, 7:05 pm |
|
Ralf Fassel wrote:
> * "comp.lang.tcl" <phillip.s.powell@gmail.com>
> | I took a wild, wild guess and came up with this:
> |
> | [TCL]
>
> If you post code, make sure it is suitably formatted for posting on
> the Web:
> - lines no longer than 70 chars, otherwise they will get wrapped and
> thus are no longer valid TCL code
> - continuation lines properly wrapped
> - proper syntax for the mentioned language in the first place
>
> The code you posted shows up here like this:
>
> | proc CALCULATE_XML_EXPDATE {{triviaAttrs {}} {triviaAttrCount 0}
> | {hasPassedTrivia 1}} {
> | if {[string length [info procs {IS_LIST}]] == 0} then source
> | ./tcl_string_tools.tcl
> | if {![info exists triviaAttrs] || ![IS_LIST $triviaAttrs] || [llength
> | $triviaAttrs] == 0} then \
> | return [clock scan {next Saturday} -base [clock scan now]]; # RETURN
> | THE NEXT SATURDAY SINCE NO expDate COULD BE FOUND
> |
> | # SINCE $triviaAttrs HAS TO BE AN EXISTING LIST WITH llength > 0 TO
> | GET HERE, JUST MAKE SURE $triviaAttrCount REFLECTS THAT
> | if {[expr {$triviaAttrCount == 0}]} then $triviaAttrCount = [expr
> | {[XML_GET_ELEMENT_ATTR_COUNT $triviaAttrs]}]
> |
> | # GET THE LAST expDate ATTRIBUTE VALUE IN $triviaAttrs
> | set expDate [lindex $triviaAttrs [expr {[lsearch $triviaAttrs
> | {expDate}] + 1 + ($triviaAttrCount * (([llength $triviaAttrs] /
> | $triviaAttrCount) - 1))}]]
> | # WILL RETURN THE FOLLOWING SATURDAY AFTER $expDate ROUNDED
> | AUTOMATICALLY TO 00:00
> | return [clock scan {next Saturday} -base $expDate]
> | }
> | [/TCL]
>
> No way this will run in *any* TCL interpreter, neither Windows nor
> Linux.
>
> Things to keep in mind:
>
> - if/then/else:
> You usually require parens around the 'then' part.
>
> This will not work as expected:
>
> if {[string length [info procs {IS_LIST}]] == 0} \
> then source ./tcl_string_tools.tcl
>
> Instead of sourcing the file it will trigger an syntax error.
> You almost always need parens for the 'then' clause (and the
> elseif/else as well):
>
> if {[string length [info procs {IS_LIST}]] == 0} \
> then { source ./tcl_string_tools.tcl }
I'm sorry but why? I was told by other TCL developers that you do *NOT*
need "parens" (you mean braces, right?) around the "then" clause as it
is valid TCL syntax, in fact, I've always used braces around "if-then"
clauses in TCL, but other people here do not, so I was trying to compat
with their standards so I don't seem too dumb on here
>
> Only exception is when the 'then' clause is *one* *word* only.
> if {$something} then continue
> if {$something} then break
> But even that I would prefer to write as:
> if {$something} then { continue }
> if {$something} then { break }
Is this TCL coding standard or something else? Now I'm just plain
>
> - TCL is not Perl: your code
> if {[expr {$triviaAttrCount == 0}]} \
> then $triviaAttrCount = \
> [expr {[XML_GET_ELEMENT_ATTR_COUNT $triviaAttrs]}]
>
> is not TCL syntax. You want:
>
> if {$triviaAttrCount == 0} then {
> set triviaAttrCount \
> [XML_GET_ELEMENT_ATTR_COUNT $triviaAttrs]
> }
>
Actually I was thinking not in Perl but in PHP; I barely know Perl.
> (no 'expr' necessary inside 'if' clauses, parens around the 'then'
> clause, proper variable assignment syntax).
[XML_GET_ELEMENT_ATTR_COUNT] returns an integer, but I had to be sure
it was an integer in this case else it would throw an "expected integer
but got.." TCL error. Don't know how to cast in TCL, sorry, in PHP
it's a breeze.
>
> - called functions may fail:
> | set expDate [lindex $triviaAttrs [expr {[lsearch $triviaAttrs
> | {expDate}] + 1 + ($triviaAttrCount * (([llength $triviaAttrs] /
> | $triviaAttrCount) - 1))}]]
>
> The lsearch above may fail to find a match. If it does not find a
> match, it returns -1. Is the calculation still valid then?
> Shouldn't you handle a failure?
>
I thought I logically did that by ensuring that $triviaAttrs has listed
content, otherwise, it wouldn't even get to that step.
> HTH
> R'
I updated the proc:
[TCL]
proc CALCULATE_XML_EXPDATE {{triviaAttrs {}} {triviaAttrCount {0}}
{hasPassedTrivia {1}}} {
if {[string length [info procs {IS_LIST}]] == 0} {
source [file join [file dirname [info script]]
tcl_string_tools.tcl]; # FAILS ON MY WINDOWS BOX
}
# RETURN THE NEXT SATURDAY SINCE NO expDate COULD BE FOUND
if {![info exists triviaAttrs] || ![IS_LIST $triviaAttrs] || [llength
$triviaAttrs] == 0} {
return [clock scan {next Saturday} -base [clock scan now]]
}
# SINCE $triviaAttrs HAS TO BE AN EXISTING LIST WITH llength > 0 TO
GET HERE,
# JUST MAKE SURE $triviaAttrCount REFLECTS THAT
if {$triviaAttrCount == 0} { set triviaAttrCount
[XML_GET_ELEMENT_ATTR_COUNT $triviaAttrs] }
# GET THE LAST expDate ATTRIBUTE VALUE IN $triviaAttrs
set expDate \
[lindex $triviaAttrs \
[expr {[lsearch $triviaAttrs {expDate}] + 1 + \
($triviaAttrCount * (([llength $triviaAttrs] /
$triviaAttrCount) - 1)) \
}\
]\
]
# WILL RETURN THE FOLLOWING SATURDAY AFTER $expDate ROUNDED
#AUTOMATICALLY TO 00:00
return [clock scan {next Saturday} -base $expDate]
}
[/TCL]
| |
| comp.lang.tcl 2006-11-27, 7:05 pm |
|
Bryan Oakley wrote:
> comp.lang.tcl wrote:
>
> Because that is how the if statement is documented to work (like you,
> I'm assuming that Ralf meant "braces" rather than "parens").
>
> Look at the man page for "if" and you'll see this:
>
> if expr1 ?then? body1 elseif expr2 ?then? body2 elseif ... ?else? ?bodyN?
>
> the thing after "then" is "body1" and must be a Tcl word. That means
> either a single (human) word, or a collection of words that are joined
> together with a quoting mechanism, typically curly braces.
>
>
>
> Remember that Tcl quoting is a tool, not a rule. [1] You never *have* to
> use curly braces. They exist as a way to group several words (in the
> human sense) together into a single "word" (in the Tcl sense).
>
> I think as a general rule, people don't use curly braces for a
> single-word body of an if statement simply because it reads better. From
> the perspective of the interpreter though, the following are all
> functionally identical:
>
> if {$something} continue
> if {$something} {continue}
> if {$something} "continue"
> if {$something} [some command that returns "continue"]
> if {$something} then continue
> if {$something} then {continue}
> ... and so on ...
>
>
> The choice of when or if to use quotes, and what type of quotes, is
> entirely up to the programmer, generally dictated by context. I'm
> convinced that once someone fully understands that single fact, all
> their Tcl quoting problems will vanish forever.
>
> [1] http://www.tclscripting.com/article...6/article3.html
The man page was Gr, but your link totally spoke my language, much
more simplistically. Thanx I will remember the rule about braces vs
not-braces vs. then vs quotes vs whtever else
| |
| R. T. Wurth 2006-11-27, 7:05 pm |
| Bryan Oakley <oakley@bardo.clearlight.com> wrote in news:GgEah.702$Py2.699
@newssvr27.news.prodigy.net:
> The choice of when or if to use quotes, and what type of quotes, is
> entirely up to the programmer, generally dictated by context. I'm
> convinced that once someone fully understands that single fact, all
> their Tcl quoting problems will vanish forever.
It's not snappy or funny, thus not QOTW material, but what he said
needs to be highlighted, restated, and taken to heart by anyon who hopes to
have any chance of calling themselves competent in Tcl. If quotes are
voodoo magic that get thrown at a problem, one is not doing software
engineering, nor computer science. If one truly understands the reason for
each and every use of quotes (even if its "to make the code clearer to
human readers" or "because a maintenance programmer might need to change my
bareword to a string containing a space"), that's a scientific and
engineering approach to the problem at hand.
| |
| Glenn Jackman 2006-11-27, 7:05 pm |
| At 2006-11-27 12:05PM, "Uwe Klein" wrote:
> Bryan Oakley wrote:
>
> You need braces when crutches don't keep you upright anymore ;-)
North American version:
You need braces when your code lacks bite.
British version:
You need braces when your code is caught with its trousers down.
And they say comedy is hard. Pshaw!
--
Glenn Jackman
Ulterior Designer
| |
|
|
| slebetman@yahoo.com 2006-11-29, 10:03 pm |
| comp.lang.tcl wrote:
> Darren New wrote:
>
> Sorry never learned C. I went from the HTML camp to Javascript to some
> Java to Perl to ASP to Tcl to PHP.
In which case you'll appreciate that it's the same in Java and Perl
(both languages inherit behaviors from C since well.. back then
everybody knows C!)
Example perl code:
my $x = 1;
if ($x = 0) {
print "Never going to execute this!";
}
print "And now \$x is $x\n";
|
|
|
|
|