While Loop bug?

in my little lua circle we have the following all the fime

while true do
blhablahblahblahblahblahblahblahblhablahblahblahblahblahblahblah
blhablahblahblahblahblahblahblah
blhablahblahblahblahblahblahblah
blhablahblahblahblahblahblahblah
blhablahblahblahblahblahblahblah
if blhablahblahblahblahblahblahblahvblhablahblahblahblahblahblahblah
blhablahblahblahblahblahblahblahblhablahblahblahblahblahblahblahblhablahblahblahblahblahblahblah
blhablahblahblahblahblahblahblahblhablahblahblahblahblahblahblahblhablahblahblahblahblahblahblahblhablahblahblahblahblahblahblahblhablahblahblahblahblahblahblah
blhablahblahblahblahblahblahblah
blhablahblahblahblahblahblahblah
blhablahblahblahblahblahblahblahblhablahblahblahblahblahblahblahblhablahblahblahblahblahblahblah
blhablahblahblahblahblahblahblahblhablahblahblahblahblahblahblah end

"wheres my error?"

finding your style and sticking with it helps out a freakin ton

me i dont like the
if(stuff){
}

makes it hard for me to see where blocks actually start and end

i do the

if(stuff)
{
}

routine

but it doesnt matter, as long as its consistent 100%

and eventho im often cussed for my particular brand of screwed up coding, ive never had someone (who knows the system) say they didnt understand what was going on, or they couldnt follow it

it just might take them a couple of min to comprehend whats going on heh

You don't like K&R? Well hell! I want my cookie back now!

This is why I have mine set up to take any junk including the noobie stuff here, paste it into Scite, hit F8, which runs it through the C compiler/indent/white space stripper and see it how God (who I should point out is female) intended code to be written within about 2 seconds

But then again, I have been wrong before(not about God being female though)!

its just me

the if(stuff){

to me is like a run on sentence

or playing wheres waldo

i want a block title

if (stuff)

and the contents of it below

not

if(){ljhrljhfjlhfdjashksdhskdalskjdlskadjskdjsalkdjlsdjlasdjlasdjsladjlsakdj
sdlfkdlfjhdjfhdkfshdfklfheuwyquidkjdsahdkjasdhuadhkaudkejdahkjdhuaed
asldkhaljdhuaedhaedhaudkaeduhkealjdhaekldhuahddnqwpeuwqeidsljdhalsjh
aldkhelrirelriyeryfkdfnrjeryry
}

for pages on end, and then play "wheres the missing bracket"

this mainly stems from the oldschool lsl script writers, where they proclaim their uberbness by writing that crap, right after declaring variables like "sixteen = 16" then using 8 math functions in a row that always report the same result every time they are called (take a look at xy chess)

besides
its just easier for ME,
god has to be female, that would explain alot (/me makes sure the wife isnt looking)
and i ate your cookie, it was yummy

so MEH

lol thanks for the giggle you two, and I'd like to add my agreement about God... although I'm not sure I can.... on one hand we have pure spite, on the other we have what looks like someone that can't be bothered to check on distant relatives... ok maybe that's mean I suppose I could look at it positively and call it lessons by smacking or non-interference...

speaking of God and programming, both of you would probably appreciate a song called "the eternal flame (AKA God Wrote in LISP code)"... because god likes a language with it's own four letter name
http://www.gnu.org/fun/jokes/eternal-flame.html

You have a Lisp <-> LSL compiler?

How do you know this?

BTW there really is only one true way... and this is the lambda calculus (functional rather than imperative programming).

/esc

True True

Im learning how to script LSL mostly from playing with the examples in the wiki and just about all of it follows the same style. I not have any real-world experience with C-like languages before so it makes it lots easier for me to work stuff out.

lsl only really shares formatting with c style languages

playing is the only way to learn a language

and thats a funny song ... i hate lisp

The second place I worked had very specific coding standards, and since most of their programmers were green they took to them without complaint. Having the whole place agree was really cool, and their standard was very close to my own, so I adopted it easily and still use it twenty years later.

BTW, How do the K&R people handle long lines of code; say, a while statement with three complex conditions on three lines? Where do the second and third lines line up, and where does the while block line up?

while ( this &&
    this_too &&
    also_this)
{
    // do stuff
}

I indent the 2nd and 3rd condition and the block code to the same level. How do you separate the block from the while conditions if the brace is in the wrong place?

You'll have to describe it since I don't have greasemonkey.

I was digging around for a site that was very long indeed but showed the different indent schemes and all of thier permutations for C type code. Creator must have changed services though
On this one I get lazy sometimes. You can preset it in Indent but setting all of the variables such as break at ,/||/&& is a pain. But in general I TRY to remember to treat the parenthesis the same as brackets in a case like that:

void foo(
	int arg1, 
	char arg2, 
	int *arg3, 
	long arg4, 
	char arg5
	) {

PS just hit the QUOTE key on my post and you will see it formatted correctly for when you don't use GreaseMonkey.

And for people who are interested in trying/comparing different types of indent or just want to clean up code that was posted here, there is a freeware gui for Indent/Beautify:

http://www.milannemec.com/winindent.html

All mammals, both male and female have nipples

And platypus hatch from eggs. And dinosaurs ruled the earth for millions of years. Bacteria and insects both out number humans. The question of the sex of god is pretty moot when you cannot even determine God's species. Frankly if God were a giant chicken or maybe a spaghetti monster that would be more important to people initially then it's gender. People might reconsider eating meatballs or chicken sandwiches.

Yesp

Ahhh - I see you've played this game before

I use modified lisp style, same as I do with functions:

while (
____this &&
____that &&
____something(else)
) {
____function (
________with,
________a,
________lotOf,
________parameters
____);
}

(underscores are spaces)

In fact I use this style even if I don't need to wrap the lines, where it makes the control flow easier to understand.

Monotremes do not have nipples. The young lick the milk from pores on the inside of the pouch.

OK I concede cause I don't know what they are and can't even spell monotremes.

Always kind of took fancy to the notion of the stars as having intelligence and the Gods as portrayed by one scif fi writer. Course then you get back to the loop of who created the stars but it still sounds cool.

did you know platypii (sp?) also have a pair of poisonous spines? or divinty comes with a sense of humor, or somebody said "hey what do we do with these spare parts..."

as for handling long lines, I tend to break then to the same level on the conditionals/concatenators if I need to like so, including for functions

if (very_long_variable_name
    & other_other_long_name_etc){
  some_Function( variable_a,
                 variable_b,
                 function( something_ to_get_a_result),
                 worthless_constant );
}

works for me because I read function properties like a list, and operators tell me it's a continuation of the previous line... oddly I don't usually split equivalencies.

but something has to get pretty long before I do that.... oddly I picked that up from writing html where properties could indeed make a line VERY long (before CSS solidified enough to make it much more readable)... that and line continuation characters in VB and a few other languages


want to write one? it'd be seriously crippled, but what the heck

monotremes include platypii and echidnas, and while they don't have nipples, they do have mammary glands....

PS they lay eggs, no pouch, marsupials have pouches.. and nipples, and bifuricated genital tracts :: shakes head ::

You're right, I was mixing up the platypus and the yapok (an aquatic marsupial... and incidentally one in which the males have a pouch, too).

You guys arguing this should try to grab a consensus within LL. Go and read the client code, where they often have 6 arguments for functions and other large code blocks, and until very recently never even tried to rectify it.

The last giant merge into their latest 1.21 code base contained a LARGE number of whitespace changes, which have the general feel of at least containing more consistency rather than less, which is good.

OK I'm confused --- is God a mammal or what?

::looks up 'yapok' ::
huh never knew there were any aquatics in the marsupials, learn something new every day =) looks like a cross between a ferret and and a beaver to me.

and I'm with strife... spaghetti monster gets my vote... although you have to give credit to cthulhu... his worshipers have a few fun quaint sayings, like "my god can eat your god" and "worship now and be eaten last".... then again discordians have the benefit of not having to make any linear sense (frequently not any non-linear sense either)... I suppose that would explain the sticker on my old computer... "hail Eris, all hail discordia" plus that whole "my god is a four letter word" thing =)

Note: I'm not advocating any of those. but to be safe...
http://flickr.com/photos/53577841@N00/174928520/

No No NO. The second method makes reading code MUCH easier, and makes no difference in detecting a semi colon where it doesn't belong. As far as semi colons go, just remember that the go at the end of FUNCTIONS not FLOW CONTROL or EVENTS. The best thing to aid in programming is knowing what the difference is between an event, a function, and flow control statements. Now and then, everyone plops down a semi colon where it doesn't belong, or forgets comparison equals (==) over a regular equal sign.

LSL could do better error reporting (i.e. ...expected '{' before ';') in the case above. That's where the main problem lies. LSL code that shouldn't compile sometimes does, and that's more the fault of the creators of LSL. In the end, when a script behaves other than expected, it's a fair bet to realize that you probably did something similar to the above error. The first things that should pop to mind are comparison equals and a semi colon where it doesn't belong.