New Start Databases

Thenomain

SGP was meant to be a boxed solution. I know you know that, but a lot of people reading don't.

I don't think that "every coder wants it their way" as much as the game designer wants a lot of features that need fine-tuned. It used to involve language code and obfuscation objects and places-spying based on stats.

As much as I bitch about code, including mine, I have really only one thing I want my way: Put spaces after commas.

ixokai

@Thenomain said in New Start Databases:

As much as I bitch about code, including mine, I have really only one thing I want my way: Put spaces after commas.

No, you monster.

Thenomain

@ixokai said in New Start Databases:

@Thenomain said in New Start Databases:

As much as I bitch about code, including mine, I have really only one thing I want my way: Put spaces after commas.

No, you monster.

Surethatsfine,Iknowhowlegiblethingsarewithoutthem.Isuspectthatintimeeveryonewillstarttounderstandtheusefulnessofspacesfortheoutstandingsimplicityofbeingabletoparsethekindofcodethatiswrittenoutthere.Inthemeantimethecalmjustificationofbeingrightwillwashovermelikeawarmbreezeonacoolday.

faraday

@Thenomain Unfortunately there are times when adding spaces causes the parser to actually add spaces, which is often not what you wanted. Example: set(me, foo: bar) sets foo to "_bar" instead of "bar" as expected.

I have it in my head that the problem used to be more widespread than it is with the current version of Penn. Or maybe I was just always paranoid. Either way, that's why my MU* code is always squished.

Thenomain

@faraday said in New Start Databases:

@Thenomain Unfortunately there are times when adding spaces causes the parser to actually add spaces, which is often not what you wanted. Example: set(me, foo: bar) sets foo to "_bar" instead of "bar" as expected.

This also isn't after a comma. Any Mush-like parser that would add a space between strcat( foo, bar ) would surprise me. (Note: I don't know what would happen in this case if you had the system not compress spaces, but I suspect code still compresses spaces in almost every other code-like situation.)

Also code that Mush parsers don't pass padded spaces to the buffer: Semi-colons, parenthesis.

I well know this is more of a "spaces or tabs for indent" level of discussion, but I can pretty easily defend it as "so much easier to read as to make up for the pain of remembering the exceptions".

Really, doesn't matter what you use to indent as long as you code with legibility in mind.

Ashen-Shugar

@Thenomain said in New Start Databases:

@ixokai said in New Start Databases:

@Thenomain said in New Start Databases:

As much as I bitch about code, including mine, I have really only one thing I want my way: Put spaces after commas.

No, you monster.

Surethatsfine,Iknowhowlegiblethingsarewithoutthem.Isuspectthatintimeeveryonewillstarttounderstandtheusefulnessofspacesfortheoutstandingsimplicityofbeingabletoparsethekindofcodethatiswrittenoutthere.Inthemeantimethecalmjustificationofbeingrightwillwashovermelikeawarmbreezeonacoolday.

Function: parenmatch([<object>/]<attribute> [,<type>, [<key>], [<flags>]])
...
[snip]
...
  The following flags exist:
    s - put spaces after every , and ; character and before and after =
    p - put spaces before ) and after (
    b - put spaces before ] and after [
    B - put spaces before } and after {
...
[snip]
...

Some people listen to you Theno

Lithium

I don't have that much of a problem with SGP, I rip some of it out, but much of it works fine even today and I don't see the need to do so. Admittedly I don't have the time, or the skill, to be a psychocoder like Theno, Ashen, or Faraday and the rest but for a hobby coder like myself, I like SGP even if it isn't the sweetest thing ever.

I do code my own stuff for what's missing from SGP as I find it necessary but a lot of it just works and that's fine.

I wouldn't mind seeing something like it for Rhost though, and would welcome it too since it might give me enough code to look at that I might be able to teach myself the differences. I basically am self taught learning through osmosis and help files on what the functions do.

I am sure my code is crap by some accounts but as long as it works, isn't easily broken, and doesn't crash the game then that's all that really matters right?

Ashen-Shugar

@Lithium said in New Start Databases:

[snip]
I wouldn't mind seeing something like it for Rhost though, and would welcome it too since it might give me enough code to look at that I might be able to teach myself the differences. I basically am self taught learning through osmosis and help files on what the functions do.
[snip]

Rhost has a minimal db that already has SGP. But as was stated elsewhere in this thread, it is a dated package. I wouldn't mind getting Theno's code, or MuxCore, or Faraday's ported to Rhost, and honestly most things should work ported to Rhost, the only difference being when you use a codebase's unique feature sets or oddities (like previously mentioned with Faraday's code on missmatches that work on Penn but not on non-penn), or align() via penn, or maybe the structure/setx stuff in TM3, and so forth.

And those can be ported, but the more unique code or features used the more effort in conversion.

My ultimate goal in all this is to see into making a general code that can be mostly working across codebases that helps people build ontop of it. So something that people are used to that they can then customize. Obviously it has to be generic, but a core set I think would get more attraction to mushing.

It's kinda daunting when you start up your mush and only see room #0, the Wizard #1, and a master room and that's.... it.

Then you think 'omg, I have so much to do!' and about 50% of the games flounder on that alone. I'm hoping if everyone comes together with a core package set, we can reduce that 50% by a significant amount.

Thenomain

@Ashen-Shugar

One of the million things I have on the back burner is "SGP replacement".

My back burner is about the size of a house.