Swordfish

When I originally designed Swordfish, the aim was to be as "familiar" to some other basics - where you didn't need an explicit procedure "main" entry point - like PROTON or PICBASIC. In hindsight, I agree with you. Having an explicit entry point would have made things a lot easier. Particularly with...

I've tried the site today using geopeeker and geotargetly. The site appears to render correctly in USA and other countries (except Singapore, who are blocked because of SPAM).

Maybe a temporary issue?

This is really strange. The forum is hosted on the same server as the wiki. I'm proxied through cloudflare. Maybe that's an issue? It seems ok in UK but not in USA.

Can anyone else confirm working / not working against their location? Thanks.

I'll look into it more tomorrow...

Variable declarations as well as constants etc still need to be declared *before* the main statement block. This has not changed.

That's unbelievable!!

You have to perform a hard reset (recycle power). Yeah, right.

Pass me the bin...

There is a new update available which should fix this problem for you. Just run "check for update" in the IDE "About" box. For more information, see:

https://www.sfcompiler.co.uk/wiki/pmwi ... ionHistory

There is a new update available which should fix this problem for you. Just run "check for update" in the IDE "About" box. For more information, see:

https://www.sfcompiler.co.uk/wiki/pmwi ... ionHistory

The problem has been fixed. We will post an update very soon. Note that your second case (boolean = 1) will not work. A boolean can only be true or false. Apologies again for this faux pas...

Damn. I will get that fixed...

I would second that approach, if possible...

Jerry is correct. It looks like delayMs() and delayUs() when clock < 1 causes the problem. Note that even if your main code block does not use either of these calls, the LCD module certainly does (for timing). I can confirm that removing all calls to delayXx() negates the issue (please do not do thi...

Yes, the error seems a little anomalous. We will look into it. However, as W4GNS has pointed out it would help to post some additional code that generates the error in your use case. Thanks...

What's happened to the site? Have you tried contacting Graham? It's a real shame if it has all gone. Perhaps try "wayback machine" internet archive?

It's a fair question. In the example you have given x could be anything. It most likely state would be "0" *but* then again it might not. It's easy to miss an initialisation in the code. But the warning should catch them... > ... and just to be REALLY clear, my use of "RHS" was NOT how the Urban Dic...

Just to be clear dim x as byte will generate a hint "x is never used". As Jerry points out, it's not an issue unless you use "x" on the right hand side of an expression. dim x as byte dim y as byte y = x will generate a warning that "x has not been initialised" and dim x as byte dim y as byte = x wi...