Posted by Jerry Stuckle on 11/13/05 18:39

Steve wrote:
> In article <436c4362$0$7057$dbd4f001@news.wanadoo.nl>,
> jrf_no_spam@jokeaday.net (Juliette) wrote:
>
>
>
>>You are missing a closing bracket in the add2tbl.php file.
>>Based on the layout, my guess would be that it should come after:
>> > if ($user == FALSE) {
>> > die("There has been an error in adding you to the
>
> Database.
>
>>Please EMail the admin.");
>>
>>Even so, could just as easily go elsewhere as your indenting is
>>pretty inconsistent (I didn't study the code).
>>
>>Grz, J.
>>
>
>
> I'm quite sure this has been debated many times before, but I have a
> thing in my head about the way neophyte web programmers lay out their
> code.
>
> In the olden days ;-) we used to do it like this,
>
> if (statement);
> {
> if (statement);
> {
> do something;
> }
> else
> {
> do something else;
> }
> }
> else
>
> etc etc etc
>
> Most sensible PFE's will support this, but you can see straight away if
> you have unbalanced parenthesis.
>
> Now, because I'm an old git, and I've always done it that way, I'll
> continue, but what is the reasoning behind hiding a curly bracket at the
> end of a statement ?
>
> </2d>
>
>
>
>
> - Steve

That was one of the ways I've seen. Personally I liked

if (statement)
{
do something;
{
else
{
do something else;
}

Makes it very easy to check your indentation and match braces. But the
one I really don't like seems to be quite popular in PHP and Java:

if (statement) {
do something;
{
else {
do something else;
}


Sure, it takes fewer lines, but it's easy to mismatch braces.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

• Next in forum: Re: Parse error: parse error, unexpected $end
• Prev in forum: Re: Parse error: parse error, unexpected $end
• Thread view: Re: Parse error: parse error, unexpected $end

[Reply to this message]