Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
Bug in disarm( )
Nov 12, 2017, 6:54 pm
By GatewaySysop
Bug in will_fall( )
Oct 23, 2017, 1:35 am
By GatewaySysop
Bug in do_zap( ), do_brandish( )
Oct 18, 2017, 1:52 pm
By GatewaySysop
Bug in get_exp_worth( )
Oct 10, 2017, 1:26 am
By GatewaySysop
Bug in do_drag( )
Oct 8, 2017, 12:40 am
By GatewaySysop
LOP Heroes Edition
Author: Vladaar
Submitted by: Vladaar
Heroes sound extras
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.3
Author: Vladaar
Submitted by: Vladaar
Memwatch
Author: Johan Lindh
Submitted by: Vladaar
Beastmaster 6D sound files
Author: Vladaar
Submitted by: Vladaar
Users Online
CommonCrawl, Yahoo!

Members: 0
Guests: 8
Stats
Files
Topics
Posts
Members
Newest Member
476
3,704
19,231
608
LAntorcha
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Bugfix Lists » SWR FUSS Bugfix List » [Bug] Line editor input not c...
Forum Rules | Mark all | Recent Posts

[Bug] Line editor input not consistent with file I/O behaviour
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Jan 30, 2006, 3:17 pm
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,639
JoinedJan 1, 2002

Bug: Line editor input not consistent with file I/O behaviour
Danger: Medium - Will break any mudprog entered via OLC before the mud reboots.
Found by: Stan
Fixed by: Samson

---

build.c, copy_buffer

Locate:
	strcat( tmp, "\r\n" );


And change it to:
	strcat( tmp, "\n" );


If you have not yet done the telnet protocol fix where \n\r is replaced with \r\n, you won't be affected by the bug but should probably still fix it anyway.

This is one of those stupid things that even after looking at it and banging heads against walls still fails to make alot of sense, but nonetheless, having the line editor only use \n (LF) to signify a newline seems to be the proper solution to this. Since mudprogs are saved to disk with \r (CR) stripped the behaviour of the line editor now properly follows the same standard used by the file I/O systems. And it can never hurt anything to use consistent behaviour, right? We've just seen what happens when you don't!
       
Pages:<< prev 1 next >>