Joe,
I don't doubt more debug information would be helpful but the fact such
errors which including non existing tiddlers, macros with no output
(because there are no results today) etc... well it is nice that the
default is to show nothing in the wiki text. This allows non non-existence
or Null results to simply not appear in a rendered tiddler.
In many other environments it is incumbent on the programmer to code for
and catch every error or null case without exception. I am glad TiddlyWiki
does not force this, however when designing and building a few more tools
would be helpful.
However When designing I do insert content around where I expect a result
so null output is obvious to me.
Best Wishes
Tony.
On Tuesday, March 13, 2018 at 12:39:49 AM UTC+11, Joe Armstrong wrote:
>
> Another (possible) silent error
>
> This case is not so clear
>
> If I write [[xyz]] or {{xyz}} when I'm authoring a tiddler
>
> In most cases (not all) this is an error because I've misspelt xyz
>
> I'd like a mode where I got BIG error messages when refereeing to
> non-existent tiddlers
>
> /Joe
>
>
>
>
> On Monday, 12 March 2018 06:23:01 UTC-7, Joe Armstrong wrote:
>>
>> I have just discovered a bug in a tiddler.
>>
>>
>> I misspelled a macro name and didn't notice it – this is actually a
>> common error of mine.
>>
>> In all programming languages I tend to see what I hoped to see rather
>> than what is there. I'm pretty bad at spelling.
>>
>>
>> Mispellling a macro name is a serious error so I want the system to shout
>> out loudly when this happens.
>>
>>
>> What happens in TW is the expansion of (say) <> causes a
>>
>> silent error if baname does not exit. ie there is no replacement text.
>>
>>
>> I'd like the replacement text to be Missing macro badname -- fatal error
>> in tiddler
>>
>>
>> Is this something I can easily fix
>>
>>
>> I HATE silent errors in programming languages - all programming and
>> run-time errors should cause a
>>
>> huge error message and execution should stop immediately. The error
>> message is so the
>>
>> programmer can fix the error. Stopping immediately is to avoid further
>> damage.
>>
>>
>> I given talks about the evils of silent errors. NaN
>> in JS for example is causes errors
>>
>> which are terribly difficult to find.
>>
>>
>> I think any error that can be detected should result in a noisy error.
>>
>>
>> Cheers
>>
>>
>> /Joe
>>
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/9026db30-3a1e-42ec-bd85-d0425b068daa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
