I still think that adding an assert command (of all things) is a
completely wrong way to do that tho.
and Dilbert to the rescue:
http://dilbert.com/dyn/str_strip/0//000/20/1//900/210948/210948.strip.zoom.gif
Have a nice sunday :)
Thierry
On 23/02/14 13:43, Thierry Douez wrote:
I still think that adding an assert command (of all things) is a
completely wrong way to do that tho.
Well, everybody is entitled to their own opinion.
One of the things I really, really like about Livecode, is the way that
there are many ways to do
On 21.02.2014, at 16:36, Björnke von Gierke b...@mac.com wrote:
So my suggestion would be to update errorDialog, maybe make a synonym for
people used to other languages. And then add an assert control structure (or
even just modify try to be able to use it in that way).
--
Use an
Alright I think I've said what I wanted on assert, so my next problem is with
the SQLite syntax changes. The new binary mode is in fact just the default
SQLite way to use binary.
Because of that, I strongly would prefer to make that the default, and
deprecate the LC way of storing binary in
So my suggestion would be to update errorDialog, maybe make a synonym for
people used to other languages. And then add an assert control structure (or
even just modify try to be able to use it in that way).
I would not like having this.; they are 2 different beasts and concepts.
( And I'm
But whatever you do, do NOT attempt to take the cat on a long walk after
getting him intoxicated while listening to a long symphony. First, the cat is
likely not going to go very far if you try to walk him, and secondly alcohol is
poison to cats. If you don’t believe me and attempt this, your
My problem is trying to get the cat to STOP dressing up in drag when I’m not
around.
Bob
On Feb 23, 2014, at 10:10 , Richmond richmondmathew...@gmail.com wrote:
On 23/02/14 20:08, Bob Sneidar wrote:
But whatever you do, do NOT attempt to take the cat on a long walk after
getting him
On 23/02/14 20:48, Bob Sneidar wrote:
My problem is trying to get the cat to STOP dressing up in drag when I’m not
around.
Obviously it is trying to ASSERT itself, and OFFSET some of the negative
aspects of living with you:
Next thing you know it will be Skipping Characters :)
Bob
On
Björnke von Gierke wrote:
I still think that adding an assert command (of all things) is a
completely wrong way to do that tho. What i'd want is this to use
existing capabilities, instead of sidestepping how things work right
now. Maybe a control structure would be a lot more in touch with
Alright, thanks everyone for explaining this. I see now that assert does
something that existing capabilities didn't do: Make your own errors up.
I still think that adding an assert command (of all things) is a completely
wrong way to do that tho. What i'd want is this to use existing
I'm not really warming up to the syntax. I'm warming up to the idea, but
I like Björnke's thinking on this. One of the things that's been bugging
me is that this reminds me of try/catch, but it's not thought-out enough,
yet.
On Fri, Feb 21, 2014 at 10:36 AM, Björnke von Gierke b...@mac.com
Hi Bjornke,
I just tried a simple assert/assertError. If the assert fails, the
commands in the assertError message handler are executed then the original
handler still continues to execute, so assert exits the handler to the
assertError message handler , then goes back to the original handler.
On 16.02.2014, at 22:13, Peter Haworth p...@lcsql.com wrote:
Seems like it's really meant to detect the
infamous this should never happen situation rather than expected errors.,
Alright, if that is the case, why isn't it done in the engine WITHOUT adding
another command? why do WE need to
On 20.02.2014, at 16:37, Richard Gaskin ambassa...@fourthworld.com wrote:
The key point there is that both only catch things the engine considers
errors.
Assert compliments those by providing for things which may be syntactically
correct and completely executable, yet are errors within
Subject: Re: RELEASE LiveCode 6.6 DP1
On 20.02.2014, at 16:37, Richard Gaskin ambassa...@fourthworld.com wrote:
The key point there is that both only catch things the engine considers
errors.
Assert compliments those by providing for things which may be
syntactically correct and completely
I think a nice example stack (perhaps even closer to a final release) put
onto revOnline would help everyone. I'd love to know more about this
upcoming feature.
On Thu, Feb 20, 2014 at 10:51 AM, Björnke von Gierke b...@mac.com wrote:
On 20.02.2014, at 16:37, Richard Gaskin
Björnke von Gierke wrote:
On 20.02.2014, at 16:37, Richard Gaskin wrote:
The key point there is that both only catch things the engine
considers errors.
Assert compliments those by providing for things which may be
syntactically correct and completely executable, yet are errors
within
Hi Bjornke,
Like you, I'm still skeptical about how useful this really is. I'm sensing
that LC coders who also work with other more traditional programming
languages will be more comfortable with assert.
To answer your question though, one example might be a parameter to a
function which is
For example, you may want asserts to be evaluated during testing, but
not in the final product.
To bring this new feature to completion I just added a request for a
global property to turn it off:
AllowAssert global property
http://quality.runrev.com/show_bug.cgi?id=11833
Comment
Mark Wieder wrote:
To bring this new feature to completion I just added a request for a
global property to turn it off:
AllowAssert global property
http://quality.runrev.com/show_bug.cgi?id=11833
Comment added to bug report.
Richard: if you don't explicitly put in an assertError handler
On Sunday, February 16, 2014, Peter Haworth p...@lcsql.com wrote:
The assert command seems to have appeared out of nowhere. Is it on any
plan that anyone has seen?
I believe it was added in order to aid with adding test coverage to
LiveCode. At least I seem to recall reading something about
All valid points. I'm just not seeing any big advantages over using if/then
constructs, but I can see that being a personal preference.
Pete
lcSQL Software
On Feb 16, 2014 4:49 AM, Trevor DeVore li...@mangomultimedia.com wrote:
On Sunday, February 16, 2014, Peter Haworth p...@lcsql.com wrote:
Pete-
Sunday, February 16, 2014, 9:11:23 AM, you wrote:
All valid points. I'm just not seeing any big advantages over using if/then
constructs, but I can see that being a personal preference.
Well, one advantage of assert is that the parameters pinpoint exactly
where the error occurred,
Okay so that means there is corruption in DNS. No surprisingly, since I have a
Sprint WiFi cell data dongle which won’t work or work well when I use the
default DNS, but when I switch to Google DNS it starts working famously.
Another possible cause would be DNS cacheing. Changing the DNS
Thanks for the explanation Mark.
Been prowling around the web for information on assert and I think I'm
getting clearer on its use. Seems like it's really meant to detect the
infamous this should never happen situation rather than expected errors.,
kinda like a switch default statement to show
On 14/02/14 20:05, Benjamin Beaumont wrote:
Dear List Members.
We are pleased to announce the release of LiveCode 6.6 DP1.
Warning, this is a pre-release with new features which have the potential
to cause issues. Please ensure you backup your stacks before testing this
release.
*Important
Hi,
the url seems to be alright to me.
Any news on the sample stacks?
Best regards,
Marc
Op 15-feb.-2014, om 12:48 heeft Richmond richmondmathew...@gmail.com het
volgende geschreven:
On 14/02/14 20:05, Benjamin Beaumont wrote:
Dear List Members.
We are pleased to announce the release of
Bug 11814
This bug is caused by setting acceleratedRendering to true
On 2/14/14, 5:06 PM, Michael Gruenthal mgruent...@mac.com wrote:
Just ran a stable in 6.5 iPad (1024 X 768) stack in the iOS 7 retina
simulator. As is, it is scaled down to occupy the bottom left quarter of
the simulator
On 15/02/14 17:07, Marc Van Cauwenberghe wrote:
Hi,
the url seems to be alright to me.
Any news on the sample stacks?
Best regards,
Marc
I phoned the engineers at BLIZOO,
http://en.wikipedia.org/wiki/Blizoo
here in Bulgaria, and they told me that they cannot connect to
If it helps, I can access all of those links here in NY city.
Paul
On Feb 15, 2014, at 11:08 AM, Richmond richmondmathew...@gmail.com wrote:
On 15/02/14 17:07, Marc Van Cauwenberghe wrote:
Hi,
the url seems to be alright to me.
Any news on the sample stacks?
Best regards,
Marc
Me too! And I’m in Brooklyn! So, quite a range of coverage here in the States.
On Feb 15, 2014, at 12:50 PM, PystCat pyst...@gmail.com wrote:
If it helps, I can access all of those links here in NY city.
___
use-livecode mailing list
All links okay in Atlanta, GA.
On Sat, Feb 15, 2014 at 11:08 AM, Richmond richmondmathew...@gmail.com wrote:
here in Bulgaria, and they told me that they cannot connect to
downloads.livecode.com/livecode/
or lists.runrev.com: so something going on there.
At the moment I cannot, also,
Am 15.02.2014 um 19:45 schrieb Jim Kanter j...@d-film.com:
All links okay in Atlanta, GA.
Same over here in germany! :-)
On Sat, Feb 15, 2014 at 11:08 AM, Richmond richmondmathew...@gmail.com
wrote:
here in Bulgaria, and they told me that they cannot connect to
All links OK here in Mexico City, too
On 15 Feb 2014, at 12:48 PM, Klaus major-k kl...@major-k.de wrote:
Am 15.02.2014 um 19:45 schrieb Jim Kanter j...@d-film.com:
All links okay in Atlanta, GA.
Same over here in germany! :-)
On Sat, Feb 15, 2014 at 11:08 AM, Richmond
On 15/02/14 20:48, Klaus major-k wrote:
Am 15.02.2014 um 19:45 schrieb Jim Kanter j...@d-film.com:
All links okay in Atlanta, GA.
Same over here in germany! :-)
I have just had a majorly stupid conversation with an 'engineer' from my
ISP provider who told me this:
1. Maybe the Livecode
Richmond-
Hmmm... possible dns resolution issues?
Can you ping www.livecode.com ?
If not, can you ping 37.59.205.89 ?
You might also try reconfiguring your dns settings to point to
Google's dns servers at 8.8.8.8 to see if that helps.
--
-Mark Wieder
ahsoftw...@gmail.com
On 15/02/14 21:30, Mark Wieder wrote:
Richmond-
Hmmm... possible dns resolution issues?
Can you ping www.livecode.com ?
If not, can you ping 37.59.205.89 ?
You might also try reconfiguring your dns settings to point to
Google's dns servers at 8.8.8.8 to see if that helps.
pinging
On Sat, Feb 15, 2014 at 11:04 AM, Richmond richmondmathew...@gmail.comwrote:
Anyway; obviously nothing wrong with RunRev, and quite a lot with my ISP
over here: both in terms of their service, and
in terms of the fact that their people talk unmitigated rubbish.
Sadly, not an unusual
Richmond-
Saturday, February 15, 2014, 11:43:37 AM, you wrote:
and bingo, everything is lovely.
Yay!
--
-Mark Wieder
ahsoftw...@gmail.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe
Can someone elaborate why assert is better then using is true/false, and what
additional things it adds?
I don't feel i can do the following otherwise: Please do not be afraid to try
it out as we need feedback to develop it further. (page 7,
Bjornke,
That was my question exactly.
On Sat, Feb 15, 2014 at 5:24 PM, Björnke von Gierke b...@mac.com wrote:
Can someone elaborate why assert is better then using is true/false, and
what additional things it adds?
I don't feel i can do the following otherwise: Please do not be afraid to
On Sat, Feb 15, 2014 at 5:24 PM, Björnke von Gierke b...@mac.com wrote:
Can someone elaborate why assert is better then using is true/false, and
what additional things it adds?
'assert' is designed for writing tests for your code. That being the case,
if 'assert' fails then the assertError
The assert command seems to have appeared out of nowhere. Is it on any
plan that anyone has seen?
Anyway, with assert:
-
--Test Harness using assert
-
command test1
do test commands
assert .
end test1
command test2
do test
Im sure there are some people very excited about the sqlite update. Very
cool.
On Fri, Feb 14, 2014 at 12:05 PM, Benjamin Beaumont b...@runrev.com wrote:
Dear List Members.
We are pleased to announce the release of LiveCode 6.6 DP1.
Warning, this is a pre-release with new features which
On Fri, Feb 14, 2014 at 10:05 AM, Benjamin Beaumont b...@runrev.com wrote:
- SQLite support updated and improved
YES
Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and
SQLiteAdmin http://www.lcsql.com/sqliteadmin.html
I see in the release notes that the hope is to include the 3.8.3 version of
the SQLite library in the final release of 6.6. One of the very cool new
features in sqlite 3.8.3 is recursive SELECT statements. Think expanding a
bill of materials or a manager/employee chart with one SELECT statement.
On Feb 14, 2014, at 11:05 AM, Benjamin Beaumont b...@runrev.com wrote:
*Sample Stacks*
We have included 3 sample stack demonstrating some of the new
features/improvements in this release:
- Stack showing effect of changes in image quality
- Stack showing effect of fullscreenmode on desktop
LiveCode use-livecode@lists.runrev.com
Subject: Re: RELEASE LiveCode 6.6 DP1
On Feb 14, 2014, at 11:05 AM, Benjamin Beaumont b...@runrev.com wrote:
*Sample Stacks*
We have included 3 sample stack demonstrating some of the new
features/improvements in this release:
- Stack showing effect
Great. A 25 year step BACKWARDS when it comes to readability.
There is nothing readable about recursive code. It might be clever and
brief, but it is most definitely NOT readable.
On Fri, Feb 14, 2014 at 2:22 PM, Peter Haworth p...@lcsql.com wrote:
I see in the release notes that the hope
Just ran a stable in 6.5 iPad (1024 X 768) stack in the iOS 7 retina
simulator. As is, it is scaled down to occupy the bottom left quarter of
the simulator screen, but all objects are actually where they belong e.g.
touching a button where it¹s rendered in the bottom left quarter doesn't
work, but
So don't use it then :-) I'm happy to see SQLite catching up with other
SQL implementations.
Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and
SQLiteAdmin http://www.lcsql.com/sqliteadmin.html
On Fri, Feb 14, 2014 at 1:06 PM, Mike
Don't worry, Peter, I won't. I will speak up when something comes in that
makes me go UGH, though. this me and the new assert syntax also come
to mind.
On Fri, Feb 14, 2014 at 5:11 PM, Peter Haworth p...@lcsql.com wrote:
So don't use it then :-) I'm happy to see SQLite catching up with
52 matches
Mail list logo
