ok, you convinced me ;-)
Pascal
Marcin Kasperski a écrit :
>>> No, no, no, it should be continue!
>>>
>>> This is just semantics of handling possible empty lines. In case of
>>> continue, we just ignore empty lines and keep reading stdin. In case
>>> of break, first empty line abort the proces
>> No, no, no, it should be continue!
>>
>> This is just semantics of handling possible empty lines. In case of
>> continue, we just ignore empty lines and keep reading stdin. In case
>> of break, first empty line abort the process.
>> The process is over when stdin is finished, fgets returns fa
Hi,
As you have a Pocket 2002 PDA, and as I tried (only tried ...) to use
system calls present in all winCE versions including 2002, the error may
be due to eTcl (they clearly don't officialy support PPC 2002).
Or, I may have used a system call that is only present since Pocket 2003
: as I mad
Hi Pascal,
I have problem to run scid under my pocket pc with message errour :
could't load library"/programfiles/scidpocket/tkscid.dll:bad adress in system callangumentwhile executing"load [file join $installdir"tkscid.dll"]"invoked from within"if { $windowsCE } {load [file join $installdir"tk
> I integrated your patch, and added your example and more
> details in the usage() function.
>
> But correct me if I am wrong, "continue" should be "break"
> here :
No, no, no, it should be continue!
This is just semantics of handling possible empty lines. In case
of continue, we just ignore em
