quote:

A roundabout way to say, toungue-in-cheek, that in 99% of the procedures, a PERFORM is not really necessary. Wouldn't you agree?

You're right Danny

I'm going to raise a NFR for 'perform' to be removed from MODIFY and MAINTAIN.

I will lobby the ANSI standard committee to remove this universally unnecessary feature from most modern programming languages.

In fact your logic has inspired me to realise that we dont need a car 99% of the time because we can always walk...

Danny,

I agree with the fact that, given what DM already has, you can circumvent using a perform most of the time, but then I would also agree with John for it's development and inclusion into DM. For my own part, I would probably live without it, but if it was available then I would use it - who wouldn't? If the product is not developed then it will grow stagnant and become less used because other tools offer more - but then we know that

As for Summit, yes, I'll be there, but unlike the tourists I won't be wearing lime green stretch pants, weigh 400 lbs and be married to my cousin (private joke!)

John,

?????, keep taking the happy pills

T

quote:

As for Summit, yes, I'll be there, but unlike the tourists I won't be wearing lime green stretch pants, weigh 400 lbs

Hmm, just wondering, if the guy in green pants with a bit of overweight isn't you, then how will we recognize you? Any obvious marks to recognize you by?

GamP,

I'll be the one in the "T" shirt. lol

Also, once I have registered, you will be able to tell me apart by looking at my name tag

BTW, last year a few of us wrote our pseudonyms on our name tags so that other "pointers" could tell who we were.

T

quote:

Originally posted by jgelona:
You guys are making this too hard. Want to do a PERFORM? Just do a -INCLUDE.

Take the code you want to PERFORM, put it in its own fex and do a -INCLUDE.

You can even make the command conditional. Here's some pseudo code.

-SET &PERFORM=IF TEST IS TRUE THEN'-INCLUDE FEXNAME' ELSE '-*';
&PERFORM.EVAL

You can even take it one step further and have FEXNAME be conditional.

Only problem with that is that it's not executed in MRE--it looks for fex in app path. Anyone have a suggestion on conditional include that looks in MRE?

you can include the "path" for MRE as well:

-INCLUDE domainname/app/fexname

domainname must be the actual PHYSICAL name of the domain (rightclick on domain and click properties - it is in the href) not the "nice" name that appears in MRE.

An INCLUDE in MRE is handled differently to an INCLUDE in the server, I think.

MRE builds the request up adding the includes to the fex and passing the fex to WebFOCUS for execution.

quote:

Originally posted by Waz:

Just keep in mind that this is FOCUS not "Python, Perl, Ruby, server-side JavaScript, Lua".

If you want to use those, call them from DM.

could you expand on that or link me to an article?

are you talking about reading external code files like you would read external data flat/TD files?

DM is fantastic, it elevates the language far above the basic FOCUS code.

in fact only a few weeks ago i was impressing our resident microsoft programmer with a report that called itself and changed as it did so, i think its was the fact you could have it all in one statement that did it...

i am not an old skool coder, have knowledge but no experience with procural languages and have more experience with OOP concepts yet i find the procedural aspect of DM intuitive and a good fit with the 'linear' style of WebFOCUS code

im interested in learning more about DM,

quote:

And a little caveat for Jodye. I know that DM will accept -IF &X=1 THEN GOTO ... but the correct syntax is -IF &X EQ 1 THEN GOTO ...
Also a semi-colon should not appear after a label.

things like this i need to know, i tend to put = at certains stages of DM statements and generally always err on the side of caution by terminating all statements with a ; the other thing i always have to pause on is using functions on DM string values and getting the arguments right

in a nutshell, to me DM means i can agree to pretty much most requests for reports that can be customized by the end user without yet having thought of a solution- its flexibility elevates it far above something like basic SQL which (for me) would require something like Access VB to be able to offer the same output

quote:

Originally posted by Danny-SRL:
For the PERFORM enthusiasts an idea with a bit of code:

  
-* File perform1.fex
-SET &PERFORM='-GOTO ';
-SET &RETURN='-GOTO ';
-*
-* LOTS OF CODE
-*
-SET &BACK='#NEXT1';
&PERFORM.EVAL #ABC
-#NEXT1
-TYPE RETURNED HERE
-SET &BACK='#NEXT2';
&PERFORM.EVAL #XYZ
-#NEXT2
-TYPE RETURNED ELSEWHERE
-*
-* LOTS OF CODE
-*
-SET &BACK='#NEXT3';
&PERFORM.EVAL #ABC
-#NEXT3
-TYPE RETURNED AGAIN
-*
-EXIT
-*
-#ABC
-TYPE ARRIVED THERE
&RETURN.EVAL &BACK
-*
-#XYZ
-TYPE ARRIVED FURTHER
&RETURN.EVAL &BACK

so here you are using the EVAL method to run the '-GOTO' string value in &PERFORM so it is interpreted as DM?

damn this thread is old, didn't realise.