Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Bug report /sbnc tcl
Author Message
TsT Offline
Junior Member
**

Posts: 5
Joined: Jun 2010
Reputation: 0
Post: #1
Bug report /sbnc tcl
I'm using sbnc 1.2 (linux debian/lenny).

When i'm using the /sbnc tcl command I got a strange thing.

I discover this bug when I try :
Code:
tcl info commands {bnc*}
and put a additionnal space between the last argument

Code:
tcl info commands  {bnc*}
<-sBNC> invalid command name "inf"

Code:
tcl abcde fgh  {ghi*}
<-sBNC> invalid command name "abcd"

I don't have this case when I'm using tclsh
I suppose that a sbnc bug ...
(This post was last modified: 14.06.2010 03:45 by TsT.)
14.06.2010 03:44
Find all posts by this user Quote this message in a reply
Bighead Offline
Junior Member
**

Posts: 5
Joined: May 2010
Reputation: 0
Post: #2
RE: Bug report /sbnc tcl
(14.06.2010 03:44)TsT Wrote:  I suppose that a sbnc bug ...

I'm quite using an alpha Version of sBNC 1.3 - my output is the following:
Quote:(NOTICE) von (-sBNC) bncnumversion bnccommand bncgetsendq bncshareddir bncversion bncgetgvhost bncuserlist bncsetgvhost bncreply bncgetmotd bncdisconnect bncdeletecommand bnckill bncvaliduser bncsettag bncjoinchans bncsetreslimit bncgettag bncisipblocked bncuptime bncsetmotd bncgetreslimit bncexedir bncaddcommand bncgetglobaltags bnccheckpassword bncgetglobaltag bncconfigdir bncsetsendq bncrnotc bncvalidusername bncmodules bncsetglobaltag bnclogbadlogin bncmoduledir bncnotc

This bug is already fixed and will be released within the next release, i think Smile

Greetz, Bighead
15.06.2010 14:27
Find all posts by this user Quote this message in a reply
TsT Offline
Junior Member
**

Posts: 5
Joined: Jun 2010
Reputation: 0
Post: #3
RE: Bug report /sbnc tcl
Ok thanks.

I got another maybe similar problem.

Can you check on the new 1.3 version if the bug also disapears ?

Code:
<admin> tcl namespace eval ::xxx { proc yyy {} {return ok}}
<-sBNC> <no error>

<admin> tcl ::xxx::yyy
<-sBNC> An error occured in the tcl script:
<-sBNC> invalid command name ":xxx::yyy"

<admin> tcl eval [list ::xxx::yyy]
<-sBNC> ok

Best Regards,
19.06.2010 12:09
Find all posts by this user Quote this message in a reply
Bighead Offline
Junior Member
**

Posts: 5
Joined: May 2010
Reputation: 0
Post: #4
RE: Bug report /sbnc tcl
I've got the same output Smile

Code:
(13:11:45) (head[away]) tcl namespace eval ::xxx { proc yyy {} {return ok}}
(13:11:45) (-sBNC) <no error>
(13:11:51) (Bighead) tcl ::xxx::yyy
(13:11:51) (-sBNC) An error occured in the tcl script:
(13:11:51) (-sBNC) invalid command name ":xxx::yyy"
(13:11:56) (Bighead) tcl eval [list ::xxx::yyy]
(13:11:56) (-sBNC) ok

Greetz, Bighead
19.06.2010 12:13
Find all posts by this user Quote this message in a reply
TsT Offline
Junior Member
**

Posts: 5
Joined: Jun 2010
Reputation: 0
Post: #5
RE: Bug report /sbnc tcl
Then this bug is still present.

My complete bug report :
Code:
<admin> tcl namespace eval [list ::xxx] { proc yyy {} {return ok}}
<-sBNC> <no error>

<admin> tcl info commands ::xxx::yyy
<-sBNC> ::xxx::yyy
Code:
<admin> tcl ::xxx::yyy
<-sBNC> An error occured in the tcl script:
<-sBNC> invalid command name ":xxx::yyy"
Code:
<admin> tcl :::xxx::yyy
<-sBNC> ok
I don't know why the first ":" is eat.
20.06.2010 15:27
Find all posts by this user Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  Certain away messages break the sbnc install Wader 0 2,459 16.05.2011 21:07
Last Post: Wader
  [sBNC 1.3] Modes/Ranks arn't being put through sBNC Wader 0 583 21.04.2011 15:01
Last Post: Wader
  The sBNC Cache Jimmy 6 2,286 14.08.2010 12:17
Last Post: Jimmy
  Bug Report /omsg /onotice sanctus 4 1,638 27.06.2010 07:34
Last Post: sanctus

Forum Jump:


Contact Us | shroudBNC Home | Return to Top | Return to Content | Lite (Archive) Mode | RSS Syndication